| /Zephyr-latest/subsys/fs/ext2/ |
| D | ext2.h | 47 #define EXT2_S_IRUSR 0x100 /* owner may read */
48 #define EXT2_S_IWUSR 0x080 /* owner may write */
49 #define EXT2_S_IXUSR 0x040 /* owner may execute */
50 #define EXT2_S_IRGRP 0x020 /* group members may read */
51 #define EXT2_S_IWGRP 0x010 /* group members may write */
52 #define EXT2_S_IXGRP 0x008 /* group members may execute */
53 #define EXT2_S_IROTH 0x004 /* others may read */
54 #define EXT2_S_IWOTH 0x002 /* others may write */
55 #define EXT2_S_IXOTH 0x001 /* others may execute */
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 6 The following terms may be used as shorthand API tags to indicate the
25 if the function may return before the operation it initializes is
54 interrupts, any thread may be suspended in any function.
56 Functions that are not **reschedule** may be invoked from either thread
59 Functions that are **reschedule** may be invoked from thread context.
61 Functions that are **reschedule** but not **sleep** may be invoked from
82 but that the operation may require an invoking thread that would have to
84 its operation. This behavior may be mediated by **no-wait**.
88 Functions that are **sleep** may be invoked from thread context.
90 Functions that are **sleep** may be invoked from interrupt and
[all …]
|
| /Zephyr-latest/boards/nxp/mimxrt1064_evk/ |
| D | CMakeLists.txt | 9 CONFIG_DISPLAY: Running this firmware on a board without a display may damage the board
17 "the MIMXRT1064-EVK, but targeting a custom board. You may need to "
24 # This configuration block may need modification if another flash chip is
33 # This configuration block may need modification if another SDRAM chip
40 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/boards/nxp/mimxrt1040_evk/ |
| D | CMakeLists.txt | 9 CONFIG_DISPLAY: Running this firmware on a board without a display may damage the board
17 "the MIMXRT1040-EVK, but targeting a custom board. You may need to "
24 # This configuration block may need modification if another flash chip is
33 # This configuration block may need modification if another SDRAM chip
40 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 18 with addresses to kernel objects when making API calls, but may never
23 Since user threads may not directly manipulate kernel objects, all use of
33 If an object loses all references, two events may happen:
36 may be called to release any runtime-allocated buffers the object was using.
56 in a special table of kernel object metadata. Kernel objects may be members
63 object. Kernel objects may not be members of a union data type.
69 The debug output of the :ref:`gen_kobject_list.py` script may be useful when
77 Kernel objects may also be allocated at runtime if
79 :c:func:`k_object_alloc` API may be used to instantiate an object from
80 the calling thread's resource pool. Such allocations may be freed in two
[all …]
|
| D | mpu_stack_objects.rst | 42 MPU design may require specific constraints on the region definition. These
57 MPUs may have a region priority mechanisms that use the highest priority region
58 that covers the memory access to determine the enforcement policy. Others may
61 Size and alignment constraints may result in stack allocations being larger
62 than the requested size. Region priority mechanisms may result in
|
| /Zephyr-latest/scripts/native_simulator/common/src/include/ |
| D | nsi_main.h | 22 * Note that other components may have requested a different
23 * exit code which may have precedence if it was !=0
33 * Note that other components may have requested a different
34 * exit code which may have precedence if it was !=0
|
| /Zephyr-latest/boards/nxp/mimxrt1050_evk/ |
| D | CMakeLists.txt | 9 CONFIG_DISPLAY: Running this firmware on a board without a display may damage the board
21 "the MIMXRT1050-EVK, but targeting a custom board. You may need to "
30 # This configuration block may need modification if another flash chip is
39 # This configuration block may need modification if another SDRAM chip
46 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/boards/native/nrf_bsim/ |
| D | cpu_wait.c | 20 * Note that interrupts may be received in the meanwhile and that therefore this
21 * thread may lose context.
22 * Therefore the wait time may be considerably longer.
32 * There may be wakes due to other interrupts or nested calls to in arch_busy_wait()
57 * There may be wakes due to other interrupts or nested calls to in posix_cpu_hold()
|
| /Zephyr-latest/doc/services/resource_management/ |
| D | index.rst | 10 multithreaded system, especially when transitions may be asynchronous,
33 in the off state. The service may also be in a transition to a given
49 :ref:`async_notification`. Both operations may be cancelled, but
51 * Requests to turn on may be queued while a transition to off is in
79 A generic API may be implemented by multiple drivers where the common
80 case is asynchronous. The on-off client structure may be an
82 guarantee synchronous context-independent transitions a driver may
|
| /Zephyr-latest/boards/nxp/mimxrt1024_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1024-EVK, but targeting a custom board. You may need to "
19 # This configuration block may need modification if another flash chip is
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/boards/nxp/mimxrt1020_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1020-EVK, but targeting a custom board. You may need to "
19 # This configuration block may need modification if another flash chip is
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/dts/bindings/video/ |
| D | nxp,video-smartdma.yaml | 19 GPIO0 pin index to use for VSYNC input. Only pins 0-15 may be used.
24 GPIO0 pin index to use for HSYNC input. Only pins 0-15 may be used.
29 GPIO0 pin index to use for PCLK input. Only pins 0-15 may be used.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | health_srv.rst | 15 The Health Server model may report a list of faults that have occurred in the
16 device's lifetime. Typically, the faults are events or conditions that may
21 outside of the node's design limits, and may have caused invalid behavior or
37 The attention state may be used during provisioning to let the user know which
47 The remaining time for the attention period may be queried through
|
| /Zephyr-latest/boards/nxp/mimxrt1060_evk/ |
| D | CMakeLists.txt | 9 CONFIG_DISPLAY: Running this firmware on a board without a display may damage the board
29 "the MIMXRT1060-EVK, but targeting a custom board. You may need to "
39 # This configuration block may need modification if another flash chip is
48 # This configuration block may need modification if another SDRAM chip
55 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 7 many different IC families, some functionality may be unavailable without the
29 license as part of the blob submission process. Blob vendors may impose a
55 Each blob which may be fetched must be individually identified in the
119 be unconditionally accepted by the project; any blob may be rejected for other
131 meets these requirements. The project may remove a blob from the upstream
151 APIs may change and such blobs cannot be modified by all project maintainers
163 for maintainability and usability. Use of such libraries may require special
164 compiler and/or linker flags, however. For example, a porting layer may require
165 special flags, or a static archive may require use of specific linker flags.
184 The scope of this test suite may grow over time. The goal is to specify
[all …]
|
| /Zephyr-latest/boards/nxp/mimxrt1160_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1160-EVK, but targeting a custom board. You may need to "
19 # This configuration block may need modification if another flash chip is
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-latest/boards/native/native_posix/ |
| D | cpu_wait.c | 17 * Note that interrupts may be received in the meanwhile and that therefore this
18 * thread may lose context.
19 * Therefore the wait time may be considerably longer.
40 * There may be wakes due to other interrupts including in arch_busy_wait()
65 * There may be wakes due to other interrupts or nested calls to in posix_cpu_hold()
|
| /Zephyr-latest/boards/native/native_sim/ |
| D | cpu_wait.c | 20 * Note that interrupts may be received in the meanwhile and that therefore this
21 * thread may lose context.
22 * Therefore the wait time may be considerably longer.
43 * There may be wakes due to other interrupts including in arch_busy_wait()
68 * There may be wakes due to other interrupts or nested calls to in posix_cpu_hold()
|
| /Zephyr-latest/dts/bindings/mspi/ |
| D | mspi-controller.yaml | 29 The controller driver may use this during initialization.
38 The controller driver may check this setting against its
45 The controller driver may check this setting against its
88 choice for a typical "CEn" pin. GPIO_ACTIVE_HIGH may be used if
92 Regardless of whether the CE pin may need software control or MSPI
|
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
| D | CMakeLists.txt | 12 "the MIMXRT1170-EVK, but targeting a custom board. You may need to "
24 # This configuration block may need modification if another flash chip is
33 # This configuration block may need modification if another SDRAM chip
40 "configuration data (XMCD) is included. This configuration may not boot")
|
| /Zephyr-latest/include/zephyr/kernel/mm/ |
| D | demand_paging.h | 98 * If CONFIG_DEMAND_PAGING_ALLOW_IRQ is enabled, this function may not be
99 * called by ISRs as the backing store may be in-use.
105 * The region may be partially paged out.
116 * If CONFIG_DEMAND_PAGING_ALLOW_IRQ is enabled, this function may not be
117 * called by ISRs as the backing store may be in-use.
131 * If CONFIG_DEMAND_PAGING_ALLOW_IRQ is enabled, this function may not be
132 * called by ISRs as the backing store may be in-use.
226 * page frame may be considered as a potential eviction candidate.
241 * page frame may no longer be considered as a potential eviction candidate.
329 * This function may be called multiple times on the same data page. If its
[all …]
|
| /Zephyr-latest/include/zephyr/ |
| D | fatal.h | 43 * weak symbol so that applications may introduce their own policy.
46 * unconditionally. Depending on architecture support, this may be
60 * the kernel itself may be in an inconsistent state, with API calls to
66 * state when the error occurred. May in some cases be NULL.
82 * state when the error occurred. May in some cases be NULL.
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | power_management.rst | 4 Power management of sensors is often a non-trivial task as sensors may have multiple power states
5 for various channels. Some sensors may allow for low noise, low power, or suspending channels
7 low power states sensors may lose their state, turning off even the digital logic portion of the de…
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | semaphores.rst | 30 A semaphore may be **given** by a thread or an ISR. Giving the semaphore
33 A semaphore may be **taken** by a thread. Taking the semaphore
35 When a semaphore is unavailable a thread may choose to wait for it to be given.
36 Any number of threads may wait on an unavailable semaphore simultaneously.
41 You may initialize a "full" semaphore (count equal to limit) to limit the number
42 of threads able to execute the critical section at the same time. You may also
44 to create a gate through which no waiting thread may pass until the semaphore
|
