Searched full:behave (Results 1 – 25 of 46) sorted by relevance
12
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | Kconfig | 30 Forces a message copy on the listeners and subscribers to behave equivalent to
|
| /Zephyr-latest/include/zephyr/drivers/pcie/ |
| D | vc.h | 59 * and any code using it should behave accordingly (displaying some info,
81 * and any code using it should behave accordingly (displaying some info,
|
| /Zephyr-latest/dts/bindings/rng/ |
| D | st,stm32-rng.yaml | 21 sampling clock detection mechanism to behave properly.
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/advertiser/ |
| D | disable.sh | 7 # The test checks that both advertisers, the legacy and the extended, behave identically.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 135 The emulated RTC device fully implements the RTC API, and will behave like a real
144 set using :c:func:`rtc_set_time`. The RTC will then behave as a real RTC, until the
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | memmap.h | 39 * that partially-initialized arrays behave as expected.
|
| /Zephyr-latest/soc/silabs/silabs_s2/ |
| D | soc.c | 82 * This makes the secure-only app behave more like a non-secure app, allowing the use of in soc_prep_hook()
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_l2.rst | 36 how the L2 layer is supposed to behave.
83 In the next section, we will describe how a device driver should behave when
|
| D | net_pkt.rst | 201 Let's see now, step by step, the functions and how they behave
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | external_content.py | 14 copied. Therefore, incremental builds detect changes correctly and behave as
|
| /Zephyr-latest/drivers/serial/ |
| D | uart_native_ptty.c | 30 * terminal driver will be configured in "raw" mode, and will therefore behave
|
| /Zephyr-latest/soc/intel/intel_adsp/common/include/ |
| D | cavs-idc.h | 17 * registers seem to behave symmetrically regardless of which CPU does
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | Kconfig | 213 to use the LFXO. Otherwise, XL1 and XL2 pins will behave as regular
|
| /Zephyr-latest/tests/benchmarks/thread_metric/src/ |
| D | tm_interrupt_processing_test.c | 141 * To be fair, it must behave just like a processor interrupt, i.e. it must save
|
| D | tm_interrupt_preemption_processing_test.c | 150 * To be fair, it must behave just like a processor interrupt, i.e. it must save
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 194 …logy behaves, your implementation must make it appear to the end user to behave exactly as specifi…
203 Each :c:struct:`implementation API function <conn_mgr_conn_api>` you implement should behave as-des…
|
| D | main.rst | 290 These features describe how ifaces should behave during connect and disconnect events.
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | heap.rst | 121 :c:func:`sys_multi_heap_aligned_alloc`. These behave identically to
|
| /Zephyr-latest/drivers/flash/ |
| D | flash_stm32wb0x.c | 239 * behave like the other counters in this function. in write_word_range()
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 186 For example, running ``west update --group-filter=+foo,-bar`` would behave
|
| /Zephyr-latest/boards/arduino/due/doc/ |
| D | index.rst | 68 (SYSTICK) that behave more as interrupts than exceptions. In addition, there can
|
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 36 that behave like standard libc functions but use the selected cbprintf
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | xtensa_asm2_util.S | 145 * registers used to hold PC/PS, but Qemu has been observed to behave
|
| /Zephyr-latest/tests/kernel/usage/thread_runtime_stats/src/ |
| D | test_thread_runtime_stats.c | 121 * The analysis fields should behave as follows prior to the system in ZTEST()
|
| /Zephyr-latest/doc/_extensions/zephyr/kconfig/ |
| D | __init__.py | 16 using the ``:kconfig:option:`` role. Kconfig options behave as regular domain
|
12
