Searched full:reused (Results 1 – 25 of 54) sorted by relevance
123
/Zephyr-latest/boards/native/nrf_bsim/common/ |
D | README.txt | 2 common & reused between several babblesim boards.
|
/Zephyr-latest/include/zephyr/dt-bindings/display/ |
D | panel.h | 22 * They are required because the enum cannot be reused within devicetree,
|
/Zephyr-latest/dts/bindings/spi/ |
D | atmel,sam-spi.yaml | 33 reused. The number of channels available is device dependent.
|
/Zephyr-latest/doc/_doxygen/ |
D | mainpage.md | 25 There are some imported or reused components of the Zephyr project that
|
/Zephyr-latest/ |
D | CONTRIBUTING.rst | 17 * There are some imported or reused components of the Zephyr project that
|
/Zephyr-latest/.github/ISSUE_TEMPLATE/ |
D | 003_rfc-proposal.md | 39 For example, do we have existing components which can be reused or altered.
|
/Zephyr-latest/boards/native/nrf_bsim/ |
D | Kconfig | 99 # Let's reuse the RTC sync options so applications which use it can be reused as is
|
/Zephyr-latest/doc/develop/manifest/external/ |
D | cannectivity.rst | 41 Once CANnectivity is added as a Zephyr module, the "gs_usb" implementation can be reused outside of
|
/Zephyr-latest/include/zephyr/modem/ |
D | cmux.h | 272 * before being reused. 284 * before being reused.
|
/Zephyr-latest/include/zephyr/crypto/ |
D | crypto.h | 268 * 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/ |
D | has_client.c | 426 /* 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/ |
D | dmic_nhlt.h | 92 * following nhlt_pdm_ctrl_cfg #0 and be reused by nhlt_pdm_ctrl_cfg #1 by setting
|
/Zephyr-latest/dts/bindings/gpio/ |
D | gpio-controller.yaml | 23 be used, but the IP block is reused in a lot of designs, some using
|
/Zephyr-latest/dts/bindings/pinctrl/ |
D | st,stm32-pinctrl.yaml | 55 Reused from
|
/Zephyr-latest/include/zephyr/console/ |
D | console.h | 109 * after console_getline() call, or the buffer can be reused.
|
/Zephyr-latest/tests/subsys/mem_mgmt/mem_attr_heap/src/ |
D | main.c | 121 * Check if the memory is correctly released and can be reused in ZTEST()
|
/Zephyr-latest/subsys/bluetooth/mesh/ |
D | rpl.c | 140 * reused. If such entry is reused, "store" bit will be set and in bt_mesh_rpl_check()
|
/Zephyr-latest/doc/kernel/services/data_passing/ |
D | stacks.rst | 117 its address back on the stack to allow the data structure to be reused.
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | slabs.rst | 43 it must release the block back to the memory slab so the block can be reused.
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | ec_host_cmd.rst | 115 e.g. eSPI. These ones should be reused as much as possible.
|
/Zephyr-latest/tests/kernel/threads/dynamic_thread/src/ |
D | main.c | 110 * @brief Test object permission on dynamic user thread when index is reused
|
/Zephyr-latest/doc/introduction/ |
D | index.rst | 40 imported or reused components of the Zephyr project that use other licensing,
|
/Zephyr-latest/tests/subsys/testsuite/fff_fake_contexts/src/ |
D | main.c | 70 /* Last FFF sequence entry is reused for excess calls. in ZTEST()
|
/Zephyr-latest/doc/hardware/cache/ |
D | guide.rst | 157 In some cases, the same buffer may be reused for e.g. DMA reads and DMA writes.
|
/Zephyr-latest/doc/hardware/porting/ |
D | shields.rst | 62 one described above. Generic functionalities that could be reused among
|
123