Home
last modified time | relevance | path

Searched refs:devicetree_api (Results 1 – 5 of 5) sorted by relevance

/Zephyr-latest/tests/lib/devicetree/api/src/
Dmain.c114 ZTEST(devicetree_api, test_path_props) in ZTEST() argument
141 ZTEST(devicetree_api, test_alias_props) in ZTEST() argument
157 ZTEST(devicetree_api, test_nodelabel_props) in ZTEST() argument
173 ZTEST(devicetree_api, test_inst_props) in ZTEST() argument
202 ZTEST(devicetree_api, test_any_inst_prop) in ZTEST() argument
230 ZTEST(devicetree_api, test_any_compat_inst_prop) in ZTEST() argument
241 ZTEST(devicetree_api, test_any_inst_bool) in ZTEST() argument
268 ZTEST(devicetree_api, test_default_prop_access) in ZTEST() argument
324 ZTEST(devicetree_api, test_has_path) in ZTEST() argument
333 ZTEST(devicetree_api, test_has_alias) in ZTEST() argument
[all …]
/Zephyr-latest/doc/services/storage/flash_map/
Dflash_map.rst51 The flash_map.h API uses data generated from the :ref:`devicetree_api`, in
/Zephyr-latest/doc/build/dts/
Dapi-usage.rst388 These macros have tricky naming conventions which the :ref:`devicetree_api` API
/Zephyr-latest/doc/releases/
Drelease-notes-2.3.rst134 :ref:`devicetree_api` for an API reference.
672 * A new :ref:`devicetree_api` was added. This API is not generated, but is
Drelease-notes-3.2.rst972 * :ref:`devicetree_api`