Searched refs:often (Results 26 – 50 of 78) sorted by relevance
1234
/Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
D | Kconfig | 84 DMA is often use for communication, however it usually requires
|
/Zephyr-latest/subsys/testsuite/ztest/ |
D | Kconfig | 90 do actions in your test case, this option often enabled when doing 98 do actions in your test case, this option often enabled when doing
|
/Zephyr-latest/doc/contribute/ |
D | proposals_and_rfcs.rst | 27 from contributors before it becomes a part of Zephyr. Quite often, even
|
/Zephyr-latest/subsys/logging/ |
D | Kconfig.misc | 118 Determines how often failures are reported. Report contains number
|
/Zephyr-latest/drivers/dma/ |
D | Kconfig.xilinx_axi_dma | 80 This configuration controls how often this happens.
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_l2.rst | 128 often not fit this frame size limitation, e.g. a buffer containing an IPv6 129 packet will often have to be split into several fragments and IP6 packet headers
|
/Zephyr-latest/doc/kernel/ |
D | timeutil.rst | 16 Applications often need to correlate the Zephyr internal time with external 128 governments, often to align local midnight to solar time.
|
/Zephyr-latest/doc/develop/test/twister/ |
D | twister_blackbox.rst | 65 TESTDATAs are most often declared as class fields.
|
/Zephyr-latest/doc/develop/languages/cpp/ |
D | index.rst | 132 "C+11") add another level of complexity as new features are often 134 with subtle differences. Making things more complex, compilers often
|
/Zephyr-latest/doc/kernel/services/smp/ |
D | smp.rst | 36 At the lowest level, however, Zephyr code has often used the 91 :c:func:`irq_lock` are not simply invoking a very short (often ~1 99 It is often desirable for real time applications to deliberately
|
/Zephyr-latest/doc/build/kconfig/ |
D | tips.rst | 161 In practice, this often amplifies the problem, because any dependencies added 167 well. This is very often overlooked in practice, even for the simplest case 312 Common sense applies, but be aware that ``select`` often causes issues in 643 If one symbol depends on another, then it's often a good idea to place it
|
D | menuconfig.rst | 15 interfaces is often handier, as they correctly handle dependencies between
|
D | setting.rst | 341 interfaces <menuconfig>` afterwards. It is often necessary to repeat
|
/Zephyr-latest/subsys/shell/backends/ |
D | Kconfig.backends | 135 Determines how often UART is polled for RX byte. 235 Determines how often RTT is polled for RX byte.
|
/Zephyr-latest/doc/services/crypto/ |
D | psa_crypto.rst | 73 The API provides support for key agreement protocols that are often
|
/Zephyr-latest/cmake/ide/ |
D | eclipse_cdt4_generator_amendment.cmake | 25 # In mixed C/C++ projects, the header files often contain the following
|
/Zephyr-latest/doc/hardware/emulator/ |
D | bus_emulators.rst | 17 Emulators often implement special features for testing. For example a
|
/Zephyr-latest/doc/services/llext/ |
D | build.rst | 6 often useful to have access to the headers and compiler flags used by the main
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-tools.rst | 19 It is often useful to make use of existing mobile applications to interact with
|
D | bluetooth-le-host.rst | 28 * Peripheral (e.g. a smart sensor, often with a limited user interface)
|
/Zephyr-latest/arch/x86/ |
D | Kconfig | 309 Non-emulated X86 devices often require special hardware to attach
|
/Zephyr-latest/doc/kernel/usermode/ |
D | syscalls.rst | 292 uninitialized. This is not used very often, currently only for 583 #. Any error resulting from a failed memory heap allocation, often from
|
/Zephyr-latest/boards/intel/adsp/doc/ |
D | intel_adsp_generic.rst | 130 situation and use case. They're often not mutually exclusive but to avoid
|
/Zephyr-latest/doc/build/cmake/ |
D | index.rst | 86 preprocessor (often abbreviated *cpp*, which should not be confused with
|
/Zephyr-latest/doc/build/dts/ |
D | api-usage.rst | 43 label <dt-node-labels>`. Node labels are often provided by SoC :file:`.dtsi`
|
1234