Home
last modified time | relevance | path

Searched full:reused (Results 1 – 25 of 54) sorted by relevance

123

/Zephyr-latest/boards/native/nrf_bsim/common/
DREADME.txt2 common & reused between several babblesim boards.
/Zephyr-latest/include/zephyr/dt-bindings/display/
Dpanel.h22 * They are required because the enum cannot be reused within devicetree,
/Zephyr-latest/dts/bindings/spi/
Datmel,sam-spi.yaml33 reused. The number of channels available is device dependent.
/Zephyr-latest/doc/_doxygen/
Dmainpage.md25 There are some imported or reused components of the Zephyr project that
/Zephyr-latest/
DCONTRIBUTING.rst17 * There are some imported or reused components of the Zephyr project that
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D003_rfc-proposal.md39 For example, do we have existing components which can be reused or altered.
/Zephyr-latest/boards/native/nrf_bsim/
DKconfig99 # Let's reuse the RTC sync options so applications which use it can be reused as is
/Zephyr-latest/doc/develop/manifest/external/
Dcannectivity.rst41 Once CANnectivity is added as a Zephyr module, the "gs_usb" implementation can be reused outside of
/Zephyr-latest/include/zephyr/modem/
Dcmux.h272 * before being reused.
284 * before being reused.
/Zephyr-latest/include/zephyr/crypto/
Dcrypto.h268 * IV value should not be reused across multiple
293 * should not be reused across multiple operations
317 * be reused across multiple operations (within a
339 * be reused across multiple operations (within a
/Zephyr-latest/subsys/bluetooth/audio/
Dhas_client.c426 /* Cleanup instance so that it can be reused */ in active_index_subscribe_cb()
483 /* Cleanup instance so that it can be reused */ in active_index_read_cb()
530 /* Cleanup instance so that it can be reused */ in control_point_subscribe_cb()
586 /* Cleanup instance so that it can be reused */ in control_point_discover_cb()
653 /* Cleanup instance so that it can be reused */ in features_read_cb()
697 /* Cleanup instance so that it can be reused */ in features_subscribe_cb()
790 /* Cleanup instance so that it can be reused */ in features_discover_cb()
/Zephyr-latest/drivers/dai/intel/dmic/
Ddmic_nhlt.h92 * following nhlt_pdm_ctrl_cfg #0 and be reused by nhlt_pdm_ctrl_cfg #1 by setting
/Zephyr-latest/dts/bindings/gpio/
Dgpio-controller.yaml23 be used, but the IP block is reused in a lot of designs, some using
/Zephyr-latest/dts/bindings/pinctrl/
Dst,stm32-pinctrl.yaml55 Reused from
/Zephyr-latest/include/zephyr/console/
Dconsole.h109 * after console_getline() call, or the buffer can be reused.
/Zephyr-latest/tests/subsys/mem_mgmt/mem_attr_heap/src/
Dmain.c121 * Check if the memory is correctly released and can be reused in ZTEST()
/Zephyr-latest/subsys/bluetooth/mesh/
Drpl.c140 * reused. If such entry is reused, "store" bit will be set and in bt_mesh_rpl_check()
/Zephyr-latest/doc/kernel/services/data_passing/
Dstacks.rst117 its address back on the stack to allow the data structure to be reused.
/Zephyr-latest/doc/kernel/memory_management/
Dslabs.rst43 it must release the block back to the memory slab so the block can be reused.
/Zephyr-latest/doc/services/device_mgmt/
Dec_host_cmd.rst115 e.g. eSPI. These ones should be reused as much as possible.
/Zephyr-latest/tests/kernel/threads/dynamic_thread/src/
Dmain.c110 * @brief Test object permission on dynamic user thread when index is reused
/Zephyr-latest/doc/introduction/
Dindex.rst40 imported or reused components of the Zephyr project that use other licensing,
/Zephyr-latest/tests/subsys/testsuite/fff_fake_contexts/src/
Dmain.c70 /* Last FFF sequence entry is reused for excess calls. in ZTEST()
/Zephyr-latest/doc/hardware/cache/
Dguide.rst157 In some cases, the same buffer may be reused for e.g. DMA reads and DMA writes.
/Zephyr-latest/doc/hardware/porting/
Dshields.rst62 one described above. Generic functionalities that could be reused among

123