Searched full:practice (Results 1 – 25 of 69) sorted by relevance
123
| /Zephyr-latest/boards/native/nrf_bsim/ |
| D | board.yml | 18 # definitions. In practice these board uses the same native SOC (SOC_POSIX) as the nrf52_bsim
|
| /Zephyr-latest/dts/bindings/display/ |
| D | ilitek,ili9xxx-common.yaml | 18 only 6 color bits are actually used being in practice equivalent to
|
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | mbox.c | 29 * In practice: The first device (mbox0) is for IPC commands in both
38 * otherwise ignored. In practice they don't do anything that simple
|
| /Zephyr-latest/subsys/bindesc/ |
| D | Kconfig | 29 limit to this value is the maximum value of a uint16_t (65535), in practice
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 41 * - best practice cryptography
215 device shall use best practice cryptography, appropriate to
313 - The device shall use best practice cryptography to facilitate secure update mechanisms.
427 - The consumer IoT device shall use best practice cryptography to communicate securely.
576 especially associated services, should be protected, with best practice cryptography.
666 user and should follow security best practice on usability.
|
| /Zephyr-latest/boards/arduino/nano_33_ble/support/ |
| D | startup.cmm | 41 IF PRACTICE.CoMmanD.AVAILable(SYStem.CPU.NANO33BLE)
|
| /Zephyr-latest/doc/project/ |
| D | modifying_contributions.rst | 52 Developers should try to limit the above practice to pull requests identified
|
| /Zephyr-latest/cmake/modules/ |
| D | user_cache.cmake | 81 # is good practice to have clean git repositories.
|
| /Zephyr-latest/tests/subsys/llext/ |
| D | testcase.yaml | 23 # While there is in practice no value in compiling subsys/llext/*.c
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 135 document more rules about how to use phandle-array properties in practice.
206 references to further reading for how this all works in practice using DTS
290 Therefore, almost all GPIO controller nodes you will see in practice will look
|
| D | intro-syntax-structure.rst | 79 In practice, devicetree nodes usually correspond to some hardware, and the node
112 Properties in practice
115 In practice, properties usually describe or configure the hardware the node
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_config.rst | 51 before continuing. This means in practice that the application wants to wait
|
| /Zephyr-latest/tests/benchmarks/sched_userspace/src/ |
| D | main.c | 33 * precision. In practice it's VERY jittery in recent qemu in stamp()
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | dlist.rst | 56 in practice the two structs are internally identical, and the list
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 81 doesn't overlap with the target Zephyr memory. In practice on the
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico2/ |
| D | rpi_pico2.dtsi | 71 * smaller than 256 bytes, but in practice the linker places the vector
|
| /Zephyr-latest/drivers/led_strip/ |
| D | tlc59731.c | 21 * A pulse must be high for at least 14ns. In practice, turning a GPIO on
|
| /Zephyr-latest/scripts/west_commands/runners/ |
| D | trace32.py | 22 The runner is a wrapper around Lauterbach TRACE32 PowerView. It executes a Lauterbach Practice
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 17 In practice, most users will be interested in Statuses
|
| /Zephyr-latest/lib/heap/ |
| D | heap_stress.c | 56 * practice, the operations aren't quite symmetric (you can in rand_alloc_choice()
|
| /Zephyr-latest/tests/benchmarks/sched/src/ |
| D | main.c | 68 * precision. In practice it's VERY jittery in recent qemu in _stamp()
|
| /Zephyr-latest/drivers/timer/ |
| D | mtk_adsp_timer.c | 16 * In practice only "ostimer0" is used as an interrupt source by the
|
| /Zephyr-latest/scripts/build/ |
| D | llext_inject_slids.py | 17 the case after one invocation. For this reason, in practice, the script
|
| /Zephyr-latest/drivers/ipm/ |
| D | ipm_cavs_host.c | 12 /* Matches SOF_IPC_MSG_MAX_SIZE, though in practice nothing anywhere
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | mutexes.rst | 39 for as long as needed; however, it is considered good practice to hold the lock
|
123
