Searched full:own (Results 1 – 25 of 535) sorted by relevance
12345678910>>...22
| /Zephyr-Core-3.6.0/drivers/sensor/bmi08x/ |
| D | Kconfig | 34 bool "Use own thread"
42 int "Accelerometer own thread priority"
49 int "Accelerometer own thread stack size"
70 bool "Use own thread"
78 int "Own thread priority"
85 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/drivers/sensor/mc3419/ |
| D | Kconfig | 21 bool "Use own thread"
23 Enable trigger to run in own thread. By
27 int "Own thread priority"
32 int "Own thread stask size"
|
| /Zephyr-Core-3.6.0/drivers/sensor/tcn75a/ |
| D | Kconfig | 22 bool "Use own thread"
40 int "Own thread priority"
44 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/drivers/sensor/bmp388/ |
| D | Kconfig | 29 bool "Use own thread"
41 int "Own thread priority"
48 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/drivers/sensor/bmg160/ |
| D | Kconfig | 45 bool "Use own thread"
53 int "Own thread priority"
60 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/drivers/sensor/icm42688/ |
| D | Kconfig | 48 bool "Use own thread"
66 int "Own thread priority"
73 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/drivers/sensor/bmm150/ |
| D | Kconfig | 50 bool "Use own thread"
77 int "Own thread priority"
84 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/op_agg/ |
| D | model_coex.sh | 18 # Then it starts sending its own aggregated sequence.
20 # own aggregated sequence from the DUT device, then it verifies that the
23 # related to its own aggregated sequence from the cli device.
|
| /Zephyr-Core-3.6.0/drivers/mm/ |
| D | mm_drv_common.h | 117 * Drivers do not have to implement their own sys_mm_drv_map_region()
120 * Or the drivers can implement their own sys_mm_drv_map_region(), then
143 * Drivers do not have to implement their own sys_mm_drv_map_array()
146 * Or the drivers can implement their own sys_mm_drv_map_array(), then
169 * Drivers do not have to implement their own sys_mm_drv_unmap_region()
172 * Or the drivers can implement their own sys_mm_drv_unmap_region(), then
192 * Drivers do not have to implement their own sys_mm_drv_remap_region()
195 * Or the drivers can implement their own sys_mm_drv_remap_region(), then
219 * Drivers do not have to implement their own sys_mm_drv_move_region()
222 * Or the drivers can implement their own sys_mm_drv_move_region(), then
[all …]
|
| /Zephyr-Core-3.6.0/drivers/sensor/fxas21002/ |
| D | Kconfig | 64 bool "Use own thread"
81 int "Own thread priority"
86 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/lib/posix/options/getopt/ |
| D | Kconfig | 10 Different shell backends are use their own instance of getopt to
23 Different shell backends are using their own instance of getopt to
|
| /Zephyr-Core-3.6.0/drivers/sensor/fxos8700/ |
| D | Kconfig | 55 bool "Use own thread"
73 int "Own thread priority"
78 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/drivers/serial/ |
| D | Kconfig.native_posix | 21 bool "Connect the UART to its own pseudo terminal"
23 Connect this UART to its own pseudoterminal. This is the preferred
68 This is only applicable if the UART_0 is configured to use its own
|
| /Zephyr-Core-3.6.0/samples/tfm_integration/tfm_secure_partition/ |
| D | README.rst | 12 create your own partitions.
28 When adapting this partition for your own purposes, please change all occurrences of
29 "dummy_partition", "DUMMY_PARTITION", "dp", and "DP" to your own partition name. Also, look through
|
| /Zephyr-Core-3.6.0/drivers/sensor/bmi160/ |
| D | Kconfig | 32 bool "Use own thread"
40 int "Own thread priority"
47 int "Own thread stack size"
|
| /Zephyr-Core-3.6.0/tests/bluetooth/host/id/bt_id_set_create_conn_own_addr/src/ |
| D | main.c | 33 * Test setting connection own address while 'CONFIG_BT_PRIVACY' isn't enabled.
62 * Test setting connection own address while 'CONFIG_BT_PRIVACY' isn't enabled.
95 * Test setting connection own address while 'CONFIG_BT_PRIVACY' is enabled and privacy features
127 * Test setting connection own address while 'CONFIG_BT_PRIVACY' is enabled and privacy features
|
| /Zephyr-Core-3.6.0/doc/project/ |
| D | modifying_contributions.rst | 20 own pull requests in order to:
61 * submit the modified patches as their *own* work (i.e. with their
62 *own* sign-off line and author identity). In this case, the developer
|
| /Zephyr-Core-3.6.0/samples/modules/tflite-micro/magic_wand/ |
| D | README.rst | 100 Modifying Sample for Your Own Project
104 samples when creating your own TensorFlow project. To build with
116 own model for use in the sample.
|
| /Zephyr-Core-3.6.0/include/zephyr/dt-bindings/memory-attr/ |
| D | memory-attr.h | 30 * Software can define their own memory attributes if needed using the
41 * Architectures can define their own memory attributes if needed using the
|
| /Zephyr-Core-3.6.0/tests/bluetooth/host/id/bt_id_set_scan_own_addr/src/ |
| D | main.c | 47 * Test setting scan own address while 'CONFIG_BT_PRIVACY' isn't enabled.
78 * Test setting scan own address while 'CONFIG_BT_PRIVACY' isn't enabled.
114 * Test setting scan own address while 'CONFIG_BT_PRIVACY' is enabled and privacy features
146 * Test setting scan own address while 'CONFIG_BT_PRIVACY' is enabled and privacy features
|
| D | test_suite_invalid_inputs.c | 39 * Test setting scan own address while 'CONFIG_BT_PRIVACY' isn't enabled.
68 * Test setting scan own address while 'CONFIG_BT_PRIVACY' isn't enabled.
102 * Test setting scan own address while 'CONFIG_BT_PRIVACY' is enabled.
|
| /Zephyr-Core-3.6.0/arch/x86/core/ |
| D | efi.c | 45 * uses special segment descriptors from its own GDT, maybe it relies
46 * on interrupts in its own IDT, maybe it twiddles custom MSRs or
50 * has already initialized all its own memory and left the rest of the
70 * but as long as this (SysV) function was called per its own ABI they
71 * have already been saved by our own caller. Also note that there is
|
| /Zephyr-Core-3.6.0/lib/libc/arcmwdt/include/sys/ |
| D | cdefs.h | 7 /* MWDT has no it's own cdefs. Add this one for satisfy dependencies */
|
| /Zephyr-Core-3.6.0/doc/develop/west/ |
| D | index.rst | 7 ``west``\ [#west-name]_. West is developed in its own `repository`_.
11 "pluggable": you can write your own west extension commands which add
|
| /Zephyr-Core-3.6.0/tests/arch/riscv/fpu_sharing/src/ |
| D | main.c | 111 * Test 1: Wait for thread2 to let us run and make sure we still own the in thread1_entry()
137 * touch the FPU. Make sure we still own the FPU in dirty state when in thread1_entry()
147 * Test 5: Because we currently own a dirty FPU, we are considered in thread1_entry()
148 * an active user. This means we should still own it after letting in thread1_entry()
160 * make it own the FPU right away. However we won't preemptively own in thread1_entry()
172 * active user, it should still own the FPU as it is not contended. in thread1_entry()
195 * Test 3: Make sure we still own the FPU when scheduled back. in thread2_entry()
219 * user. We should own it right away but clean this time. in thread2_entry()
230 * assigned to it. This means we should still own it despite not in thread2_entry()
|
12345678910>>...22
