Searched full:devicetree (Results 1 – 25 of 438) sorted by relevance
12345678910>>...18
| /Zephyr-Core-2.7.6/doc/guides/dts/ |
| D | dt-vs-kconfig.rst | 3 Devicetree versus Kconfig
6 Along with devicetree, Zephyr also uses the Kconfig language to configure the
7 source code. Whether to use devicetree or Kconfig for a particular purpose can
12 * Use devicetree to describe **hardware** and its **boot-time configuration**.
19 In other words, devicetree mainly deals with hardware, and Kconfig with
26 nodes in the devicetree. These provide the UART type (via the ``compatible``
30 devicetree. This could include configuration such as the RX IRQ line's
32 their boot-time configuration is described in devicetree.
36 board's devicetree still includes UART nodes.
41 * Devicetree should be used to describe the presence of the radio **hardware**,
[all …]
|
| D | intro.rst | 3 Introduction to devicetree
8 This is a conceptual overview of devicetree and how Zephyr uses it. For
11 A *devicetree* is a hierarchical data structure that describes hardware. The
12 `Devicetree specification`_ defines its source and binary representations.
13 Zephyr uses devicetree to describe the hardware available on its :ref:`boards`,
16 There are two types of devicetree input files: *devicetree sources* and
17 *devicetree bindings*. The sources contain the devicetree itself. The bindings
19 <build_overview>` uses devicetree sources and bindings to produce a generated C
20 header. The generated header's contents are abstracted by the ``devicetree.h``
21 API, which you can use to get information from your devicetree.
[all …]
|
| D | howtos.rst | 3 Devicetree HOWTOs
6 This page has step-by-step advice for getting things done with devicetree.
10 .. _get-devicetree-outputs:
12 Get your devicetree and generated header
15 A board's devicetree (:ref:`BOARD.dts <devicetree-in-out-files>`) pulls in
17 includes the SoC's ``.dtsi``. One way to figure out the devicetree's contents
21 If you just want to see the "final" devicetree for your board, build an
26 You can build :ref:`hello_world` to see the "base" devicetree for your board
47 The :file:`zephyr.dts` file is the final devicetree in DTS format.
51 See :ref:`devicetree-in-out-files` for details about these files.
[all …]
|
| D | design.rst | 6 Zephyr's use of devicetree has evolved significantly over time, and further
14 Zephyr shall obtain its hardware descriptions exclusively from devicetree.
19 - New device drivers shall use devicetree APIs to determine which :ref:`devices
27 - Boot-time pin muxing and pin control can be accomplished via devicetree.
34 devicetree instead.
37 particular compatible are enabled. This can and should be done with devicetree
42 board level devicetree instead.
45 information obtained from devicetree, e.g. for device power management.
50 Zephyr's devicetree tooling is based on a generic layer which is interoperable
51 with other devicetree users, such as the Linux kernel.
[all …]
|
| D | troubleshooting.rst | 3 Troubleshooting devicetree
6 Here are some tips for fixing misbehaving devicetree related code.
18 This is general advice which is especially applicable to debugging devicetree
22 Make sure <devicetree.h> is included
25 Unlike Kconfig symbols, the :file:`devicetree.h` header must be included
28 Many Zephyr header files rely on information from devicetree, so including some
29 other API may transitively include :file:`devicetree.h`, but that's not
39 - In C/C++, devicetree names must be lowercased and special characters must be
40 converted to underscores. Zephyr's generated devicetree header has DTS names
42 ``<devicetree.h>`` API.
[all …]
|
| D | api-usage.rst | 3 Devicetree access from C/C++
6 This guide describes Zephyr's ``<devicetree.h>`` API for reading the devicetree
8 :ref:`devicetree-intro` and :ref:`dt-bindings`. See :ref:`devicetree` for
14 Linux developers familiar with devicetree should be warned that the API
15 described here differs significantly from how devicetree is used on Linux.
17 Instead of generating a C header with all the devicetree data which is then
19 devicetree data structure in its binary form. The binary representation is
22 Zephyr does not work this way because the size of the devicetree binary and
31 To get information about a particular devicetree node, you need a *node
37 Use :c:func:`DT_PATH()` along with the node's full path in the devicetree,
[all …]
|
| D | index.rst | 3 Devicetree Guide
6 This is a high-level guide to devicetree as it is used for Zephyr development.
7 See :ref:`devicetree` for reference material.
|
| /Zephyr-Core-2.7.6/doc/reference/devicetree/ |
| D | api.rst | 3 Devicetree API
6 This is a reference page for the ``<devicetree.h>`` API. The API is macro
26 A *node identifier* is a way to refer to a devicetree node at C preprocessor
28 devicetree data in C rvalue form using, for example, the
29 :ref:`devicetree-property-access` API.
32 identifiers for other devicetree nodes using :c:func:`DT_PATH`,
41 .. doxygengroup:: devicetree-generic-id
49 There are special-purpose APIs for accessing the :ref:`devicetree-reg-property`
50 and :ref:`devicetree-interrupts-property`.
55 .. doxygengroup:: devicetree-generic-prop
[all …]
|
| D | index.rst | 3 Devicetree chapter
6 This is reference documentation for devicetree as it is used for Zephyr
8 platform-independent specification, see the `Devicetree specification`_.
10 .. _Devicetree specification: https://www.devicetree.org/
|
| /Zephyr-Core-2.7.6/scripts/dts/ |
| D | README.txt | 5 The libraries and tests have now been moved to the 'python-devicetree'
14 https://pypi.org/project/devicetree/
15 https://python-devicetree.readthedocs.io/en/latest/
16 https://github.com/zephyrproject-rtos/python-devicetree
18 The 'python-devicetree' subdirectory you find here next to this
19 README.txt matches the standalone python-devicetree repository linked
27 devicetree.edtlib from now on, but the code will continue to be found
30 Eventually, as APIs stabilize, the python-devicetree code in this
|
| D | gen_dts_cmake.py | 7 This script uses edtlib and the devicetree data in the build directory
8 to generate a CMake file which contains devicetree data.
20 devicetree as CMake target properties.
26 CMake target properties, along with other devicetree data.
29 devicetree values can be used at CMake processing time.
39 DT_PROP(node_id, foo) from devicetree.h.
47 sys.path.append(os.path.join(os.path.dirname(__file__), 'python-devicetree',
|
| /Zephyr-Core-2.7.6/samples/basic/button/ |
| D | README.rst | 18 The button must be configured using the ``sw0`` :ref:`devicetree <dt-guide>`
19 alias, usually in the :ref:`BOARD.dts file <devicetree-in-out-files>`. You will
24 Unsupported board: sw0 devicetree alias is not defined
29 The sample additionally supports an optional ``led0`` devicetree alias. This is
34 Devicetree details
37 This section provides more details on devicetree configuration.
39 Here is a minimal devicetree fragment which supports this sample. This only
43 .. code-block:: devicetree
69 As shown, the ``sw0`` devicetree alias must point to a child node of a node
80 node, and that the GPIO controller's devicetree binding names those two cells
|
| /Zephyr-Core-2.7.6/samples/basic/blinky/ |
| D | README.rst | 25 Unsupported board: led0 devicetree alias is not defined
29 ``led0`` :ref:`devicetree <dt-guide>` alias. This is usually done in the
30 :ref:`BOARD.dts file <devicetree-in-out-files>` or a :ref:`devicetree overlay
31 <set-devicetree-overlays>`.
|
| /Zephyr-Core-2.7.6/samples/basic/rgb_led/ |
| D | README.rst | 23 The LED PWM channels must be configured using the following :ref:`devicetree
25 <devicetree-in-out-files>`:
36 Unsupported board: red-pwm-led devicetree alias is not defined
37 Unsupported board: green-pwm-led devicetree alias is not defined
38 Unsupported board: blue-pwm-led devicetree alias is not defined
46 No additional wiring is necessary if the required devicetree aliases refer to
|
| /Zephyr-Core-2.7.6/doc/reference/peripherals/ |
| D | regulators.rst | 14 the regulator subsystem. Nodes with a devicetree compatible of
22 completes. Zephyr recognizes devicetree nodes with a compatible of
25 The ``vin-supply`` devicetree property is used to identify the
26 regulator(s) that a devicetree node directly depends on. Within the
34 ``supply-gpios`` devicetree property should be used. There is no device
|
| /Zephyr-Core-2.7.6/doc/reference/usb/ |
| D | uds_cdc_acm.rst | 18 The devicetree compatible property for CDC ACM UART is
21 and a compatible node in the devicetree sources is present. If necessary,
30 node label. Often, CDC ACM UART is described in a devicetree overlay file
33 .. code-block:: devicetree
44 devicetree to describe CDC ACM UART. The motivation behind using devicetree
58 .. code-block:: devicetree
96 backend for other subsystems by setting :ref:`devicetree-chosen-nodes`
|
| /Zephyr-Core-2.7.6/scripts/dts/python-devicetree/ |
| D | setup.py | 11 This is just a placeholder for moving Zephyr's devicetree libraries
22 name='devicetree',
24 description='Python libraries for devicetree',
28 url='https://github.com/zephyrproject-rtos/python-devicetree',
|
| /Zephyr-Core-2.7.6/samples/basic/servo_motor/ |
| D | README.rst | 27 Unsupported board: pwm-servo devicetree alias is not defined
31 :ref:`devicetree <dt-guide>` alias. Usually you will need to set this up via a
32 :ref:`devicetree overlay <set-devicetree-overlays>` like so:
59 The sample has a devicetree overlay for the :ref:`bbc_microbit`.
|
| /Zephyr-Core-2.7.6/include/devicetree/ |
| D | fixed-partitions.h | 3 * @brief Flash Devicetree macro public API header file.
20 * @defgroup devicetree-fixed-partition Devicetree Fixed Partition API
21 * @ingroup devicetree
29 * Example devicetree fragment:
|
| /Zephyr-Core-2.7.6/samples/boards/nrf/battery/ |
| D | README.rst | 13 * If the board devicetree has a ``/vbatt`` node with compatible
15 example of a devicetree node describing a voltage divider for battery
18 .. code-block:: devicetree
34 ``Vdd`` is selected. An example of a Devicetree configuration for this case is
37 .. code-block :: devicetree
67 devicetree configuration as noted above.
|
| /Zephyr-Core-2.7.6/soc/arm/nordic_nrf/ |
| D | soc_nrf_common.h | 15 #include <devicetree.h>
19 * @brief Get a PSEL value out of a foo-gpios or foo-pin devicetree property
29 * helper macro can be used to get a PSEL value out of the devicetree
55 * Error out the build if the devicetree node with identifier
72 "Devicetree node " DT_NODE_PATH(node_id) \
88 "Devicetree node " DT_NODE_PATH(node_id) \
95 * @brief Convert a devicetree GPIO phandle+specifier to PSEL value
113 * This macro converts a devicetree GPIO phandle array value
161 "Devicetree node " \
|
| /Zephyr-Core-2.7.6/doc/guides/porting/ |
| D | shields.rst | 26 * **<shield>.overlay**: This file provides a shield description in devicetree
27 format that is merged with the board's :ref:`devicetree <dt-guide>`
52 * Devicetree: A board :ref:`devicetree <dt-guide>` file,
56 .. code-block:: devicetree
67 .. code-block:: devicetree
150 node`_ that looks like the following into the board devicetree file:
153 …https://github.com/devicetree-org/devicetree-specification/blob/4b1dac80eaca45b4babf5299452a951008…
192 devicetree. In some cases it's necessary to use a non-zero flag value
|
| /Zephyr-Core-2.7.6/samples/basic/threads/ |
| D | README.rst | 31 ``led0`` and ``led1`` :ref:`devicetree <dt-guide>` aliases, usually in the
32 :ref:`BOARD.dts file <devicetree-in-out-files>`.
39 Unsupported board: led0 devicetree alias is not defined
40 Unsupported board: led1 devicetree alias is not defined
|
| /Zephyr-Core-2.7.6/doc/reference/storage/flash_map/ |
| D | flash_map.rst | 32 devicetree as described below.
34 Relationship with Devicetree
38 particular its :ref:`devicetree-flash-api`. Zephyr additionally has some
43 Here is an example devicetree fragment which uses fixed flash partitions for
78 :ref:`devicetree-reg-property`, and in this case is 0x20000.
81 with a devicetree label like ``"image-0"``, use something like this:
|
| /Zephyr-Core-2.7.6/include/linker/ |
| D | devicetree_regions.h | 7 * Generate memory regions from devicetree nodes.
16 * @brief Generate a linker memory region from a devicetree node
25 * @param node_id devicetree node identifier with a \<reg\> property
|
12345678910>>...18
