Home
last modified time | relevance | path

Searched refs:often (Results 26 – 50 of 78) sorted by relevance

1234

/Zephyr-latest/subsys/mgmt/ec_host_cmd/
DKconfig84 DMA is often use for communication, however it usually requires
/Zephyr-latest/subsys/testsuite/ztest/
DKconfig90 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/
Dproposals_and_rfcs.rst27 from contributors before it becomes a part of Zephyr. Quite often, even
/Zephyr-latest/subsys/logging/
DKconfig.misc118 Determines how often failures are reported. Report contains number
/Zephyr-latest/drivers/dma/
DKconfig.xilinx_axi_dma80 This configuration controls how often this happens.
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_l2.rst128 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/
Dtimeutil.rst16 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/
Dtwister_blackbox.rst65 TESTDATAs are most often declared as class fields.
/Zephyr-latest/doc/develop/languages/cpp/
Dindex.rst132 "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/
Dsmp.rst36 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/
Dtips.rst161 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
Dmenuconfig.rst15 interfaces is often handier, as they correctly handle dependencies between
Dsetting.rst341 interfaces <menuconfig>` afterwards. It is often necessary to repeat
/Zephyr-latest/subsys/shell/backends/
DKconfig.backends135 Determines how often UART is polled for RX byte.
235 Determines how often RTT is polled for RX byte.
/Zephyr-latest/doc/services/crypto/
Dpsa_crypto.rst73 The API provides support for key agreement protocols that are often
/Zephyr-latest/cmake/ide/
Declipse_cdt4_generator_amendment.cmake25 # In mixed C/C++ projects, the header files often contain the following
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst17 Emulators often implement special features for testing. For example a
/Zephyr-latest/doc/services/llext/
Dbuild.rst6 often useful to have access to the headers and compiler flags used by the main
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-tools.rst19 It is often useful to make use of existing mobile applications to interact with
Dbluetooth-le-host.rst28 * Peripheral (e.g. a smart sensor, often with a limited user interface)
/Zephyr-latest/arch/x86/
DKconfig309 Non-emulated X86 devices often require special hardware to attach
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst292 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/
Dintel_adsp_generic.rst130 situation and use case. They're often not mutually exclusive but to avoid
/Zephyr-latest/doc/build/cmake/
Dindex.rst86 preprocessor (often abbreviated *cpp*, which should not be confused with
/Zephyr-latest/doc/build/dts/
Dapi-usage.rst43 label <dt-node-labels>`. Node labels are often provided by SoC :file:`.dtsi`

1234