| /Zephyr-latest/scripts/release/ |
| D | bug_bash.py | 71 user = p.user.login
72 tally[user] = tally.get(user, 0) + 1
81 for user, score in self.get_tally().items():
83 rev_tally[score] = [user]
85 rev_tally[score].append(user)
99 for user in users:
103 top_ten.append(tuple([score, user]))
163 for score, user in top_ten:
165 print('{}\t{}'.format(score, user))
180 issues[i].number, pulls[i].user.login, pulls[i].title))
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 006_nomination.md | 3 about: Nominate a GitHub user for additional rights on the Zephyr Project
20 Use this template to nominate a GitHub user for the Contributor role with
21 Triage permission level, which allows the user to add reviewers to a pull
28 Provide the following information about the GitHub user:
37 reviewed by the GitHub user that demonstrate the user's dedication to the
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 2 .. _dt-zephyr-user:
4 The ``/zephyr,user`` node
7 Zephyr's devicetree scripts handle the ``/zephyr,user`` node as a special case:
14 This node is meant for sample code and user applications. It should not be
20 You can store numeric or array values in ``/zephyr,user`` if you want them to
28 zephyr,user {
54 You can store :ref:`phandles <dt-phandles>` in ``/zephyr,user`` if you want to
63 zephyr,user {
100 The ``/zephyr,user`` node is a convenient place to store application-specific
110 zephyr,user {
|
| /Zephyr-latest/subsys/bluetooth/controller/ticker/ |
| D | ticker.c | 1954 struct ticker_user *user;
1957 user = &users[count_user];
1958 user_ops = &user->user_op[0];
1964 while (user->middle != user->last) {
1971 user_op = &user_ops[user->middle];
1974 prev = user->middle;
1975 middle = user->middle + 1;
1976 if (middle == user->count_user_op) {
1979 user->middle = middle;
2047 user->middle = prev;
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | mpu_userspace.rst | 16 During the process of dropping a thread to user mode, the privileged stack
21 During system calls, the user mode thread's access to the system call and the
22 passed-in parameters are all validated. The user mode thread is then elevated
25 thread is set back to user mode and the stack is restored to the user stack.
|
| D | overview.rst | 10 isolated from other user mode threads and from the kernel. A flawed or
11 malicious user mode thread cannot leak or modify the private data/resources
13 control another user mode thread or the kernel.
15 Example use-cases of Zephyr's user mode features:
32 'user mode') we aim to protect against the following:
41 - A user thread will by default have read/write access to its own stack
44 - A user thread will never by default have access to user thread stacks
47 - A user thread will never by default have access to thread stacks owned
51 - A user thread may have read/write access to the stacks of other user
56 - On MMU systems, threads may access any user thread stack in the same
[all …]
|
| D | index.rst | 7 which we call user mode. The current implementation is designed for devices
10 For details on creating threads that run in user mode, please see
|
| /Zephyr-latest/soc/raspberrypi/rpi_pico/rp2040/ |
| D | Kconfig | 31 by the board definition, not the user.
37 Should be selected by the board definition, not the user.
43 by the board definition, not the user.
49 by the board definition, not the user.
55 by the board definition, not the user.
|
| /Zephyr-latest/samples/subsys/mgmt/hawkbit/ |
| D | Kconfig | 17 server for updates and installing them without requiring user
23 Manual mode requires the user to call the server probe and then, if
24 there is an available update, also requires the user to decide if
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt118x/ |
| D | Kconfig | 43 and user program images and data. The boot ROM expects container data
46 # Note- This config present the offest between container header and user
50 hex "The offset between container header and user image"
53 The offset between container and user image. IF change the user image
55 value, this will make ROM could get the user image start address.
|
| /Zephyr-latest/include/zephyr/drivers/interrupt_controller/ |
| D | gd32_exti.h | 32 typedef void (*gd32_exti_cb_t)(uint8_t line, void *user);
66 int gd32_exti_configure(uint8_t line, gd32_exti_cb_t cb, void *user);
|
| D | gpio_intc_stm32.h | 80 typedef void (*stm32_gpio_irq_cb_t)(gpio_port_pins_t pin, void *user);
91 stm32_gpio_irq_cb_t cb, void *user);
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | Kconfig | 9 Manual mode requires the user to call the server probe and then, if
10 there is an available update, also requires the user to decide if
19 server for updates and installing them without requiring user
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | index.rst | 15 indicate what user data is "owned" by that node. Instead, the
17 user-defined struct. Macros are provided to retrieve a user struct
21 allocate node objects because the memory is provided by the user).
26 needed will be provided by the user. Some of the provided data
|
| /Zephyr-latest/boards/panasonic/pan1783/doc/ |
| D | index.rst | 35 `pan1783_evb user guide`_ / `pan1783a_evb user guide`_ / `pan1783a_pa_evb user guide`_
61 .. _pan1783_evb user guide: https://pideu.panasonic.de/development-hub/pan1783/evaluation_board/use…
62 .. _pan1783a_evb user guide: https://pideu.panasonic.de/development-hub/pan1783a/evaluation_board/u…
63 .. _pan1783a_pa_evb user guide: https://pideu.panasonic.de/development-hub/pan1783a_pa/evaluation_b…
|
| /Zephyr-latest/tests/benchmarks/sched_userspace/ |
| D | CMakeLists.txt | 8 SOURCE src/user.c
19 target_sources(app PRIVATE src/main.c src/user.c)
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | float.rst | 62 * non-user: A thread that cannot use any floating point registers
64 * FPU user: A thread that can use the standard floating point registers
66 * SSE user: A thread that can use both the standard floating point registers
72 context switches to ensure the computations performed by each FPU user
73 or SSE user are not impacted by the computations performed by the other users.
146 user on a case-by-case basis. A "lazy save" algorithm is used during context
149 FPU user to a non-user thread, and then back to the original FPU user.
153 current FPU user context is saved in the thread object and the ISR is resumed
165 On the ARCv2 architecture, the kernel treats each thread as a non-user
166 or FPU user and the thread must be tagged by one of the
[all …]
|
| /Zephyr-latest/drivers/espi/ |
| D | espi_mchp_xec_v2.c | 1093 static void vw_slp3_handler(int girq_id, int src, void *user) in vw_slp3_handler() argument
1095 const struct device *dev = (const struct device *)user; in vw_slp3_handler()
1100 static void vw_slp4_handler(int girq_id, int src, void *user) in vw_slp4_handler() argument
1102 const struct device *dev = (const struct device *)user; in vw_slp4_handler()
1107 static void vw_slp5_handler(int girq_id, int src, void *user) in vw_slp5_handler() argument
1109 const struct device *dev = (const struct device *)user; in vw_slp5_handler()
1114 static void vw_host_rst_warn_handler(int girq_id, int src, void *user) in vw_host_rst_warn_handler() argument
1116 const struct device *dev = (const struct device *)user; in vw_host_rst_warn_handler()
1121 static void vw_sus_warn_handler(int girq_id, int src, void *user) in vw_sus_warn_handler() argument
1123 const struct device *dev = (const struct device *)user; in vw_sus_warn_handler()
[all …]
|
| /Zephyr-latest/samples/userspace/syscall_perf/ |
| D | README.rst | 10 user thread has to go through a system call compared to a supervisor thread that
17 This application creates a supervisor and a user thread.
19 current thread. The user thread has to go through a system call.
|
| /Zephyr-latest/samples/boards/st/power_mgmt/standby_shutdown/ |
| D | README.rst | 13 Press and hold the user button:
16 release the user button to exit from shutdown mode or from shutdown mode.
40 Press and hold the user button:
43 release the user button to exit from shutdown mode or from shutdown mode.
|
| /Zephyr-latest/tests/arch/arm/arm_thread_swap/ |
| D | README.txt | 19 - the mode variable (when building with support for either user
34 This test verifies that the ARM mechanism for user system calls
36 - the mode variable with respect to the user mode flag always indicates
37 the mode in which a user thread is currently executing.
40 user threads in PRIV mode and supervisor threads
43 targets with support for user space.
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | intc_gd32_exti.c | 38 void *user; member
100 data->cbs[i].cb(i, data->cbs[i].user); in gd32_exti_isr()
142 int gd32_exti_configure(uint8_t line, gd32_exti_cb_t cb, void *user) in gd32_exti_configure() argument
155 data->cbs[line].user = user; in gd32_exti_configure()
|
| /Zephyr-latest/cmake/modules/ |
| D | user_cache.cmake | 5 # Configure user cache directory.
7 # The user cache can be used for caching of data that should be persistent
13 # Zephyr build system uses this user cache to store Zephyr compiler check
84 # user's cache directory.
93 # Populate USER_CACHE_DIR with a directory that user applications may
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 33 In order to use SLIRP with Zephyr, the user has to set the Kconfig option to
50 * Information about network to use. This may be valuable if the user does
52 * Tell QEMU to start DHCP server at user-defined IP address.
57 offloads this to the user, and expects that they will provide arguments
59 populated by the user.
76 If the user does not have any specific networking requirements other than the
77 ability to access a web page from the guest, user networking (slirp) is a
|
| /Zephyr-latest/boards/shields/eval_adxl362_ardz/doc/ |
| D | index.rst | 34 - `EVAL-ADXL362-ARDZ user guide`_
42 .. _EVAL-ADXL362-ARDZ user guide:
43 https://wiki.analog.com/resources/eval/user-guides/eval-adicup360/hardware/adxl362
|
