Searched full:involves (Results 1 – 25 of 30) sorted by relevance
12
| /Zephyr-latest/doc/security/ |
| D | hardening-tool.rst | 7 process, known as "hardening", involves strengthening the security of a system to protect it from
|
| D | security-overview.rst | 591 platform, which involves testing the respective Zephyr OS
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 28 The configuration of a node involves adding an application key, getting
|
| /Zephyr-latest/doc/develop/west/ |
| D | sign.rst | 19 Signing involves a number of "wrapper" scripts stacked on top of each other: ``west
|
| /Zephyr-latest/drivers/clock_control/ |
| D | Kconfig.stm32 | 60 The measurement process involves waiting for a certain amount of LSI periods
|
| /Zephyr-latest/modules/hal_nordic/ |
| D | Kconfig | 223 involves a call to `k_panic`/`k_oops` and allows further tweaking of the behavior.
|
| /Zephyr-latest/arch/x86/core/ |
| D | userspace.c | 53 * CR3 involves an expensive full TLB flush. in z_x86_swap_update_page_tables()
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | Kconfig | 69 The workaround involves execution of 8 NOP instructions when the CPU
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 161 user mode through system calls involves an extra layer of handler functions,
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | guide.rst | 138 Flushing the cache involves writing all modified cache lines in a specified
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 107 situation will not be the same if suspension involves sending packets through a
|
| D | device.rst | 23 Device runtime power management involves coordinated interaction between
|
| /Zephyr-latest/kernel/ |
| D | mem_slab.c | 99 * Currently this just involves creating the list of free blocks for each slab.
|
| D | Kconfig | 129 implemented, this involves an inherent O(N) scaling in the number of
|
| /Zephyr-latest/tests/kernel/events/sys_event/src/ |
| D | main.c | 366 * Testing both the delivery and reception of events involves the use of
|
| /Zephyr-latest/include/zephyr/input/ |
| D | input_kbd_matrix.h | 97 * request to drive all the column and typically involves reenabling
|
| /Zephyr-latest/dts/bindings/ethernet/ |
| D | xlnx,gem.yaml | 107 formed in the context of the ISR, as it only involves a limited number
|
| /Zephyr-latest/tests/kernel/events/event_api/src/ |
| D | test_event_apis.c | 404 * Testing both the delivery and reception of events involves the use of
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 288 Though the API shown previously is rather simple, it involves always
|
| /Zephyr-latest/arch/riscv/core/ |
| D | elf.c | 353 /* this involves moving the symbol */ in arch_elf_relocate()
|
| /Zephyr-latest/doc/services/debugging/ |
| D | coredump.rst | 52 This usually involves the following steps:
|
| /Zephyr-latest/include/zephyr/pm/ |
| D | device.h | 159 * Generic PM involves suspending and resuming operations which can be blocking,
|
| /Zephyr-latest/subsys/testsuite/ztest/include/zephyr/ |
| D | ztest_test.h | 394 * However, if the success case for your test involves a fatal fault,
|
| /Zephyr-latest/drivers/ethernet/ |
| D | phy_xlnx_gem.c | 372 * auto-negotiation. This process involves: in phy_xlnx_gem_marvell_alaska_cfg()
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 737 Interrupt processing that is time consuming, or involves blocking,
|
12
