Home
last modified time | relevance | path

Searched +full:foo +full:- +full:names (Results 1 – 25 of 60) sorted by relevance

123

/Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings/
Dprops.yaml1 # SPDX-License-Identifier: BSD-3-Clause
8 nonexistent-boolean:
11 existent-boolean:
21 uint8-array:
22 type: uint8-array
26 const: "foo"
28 string-array:
29 type: string-array
30 const: ['foo', 'bar', 'baz']
32 phandle-ref:
[all …]
/Zephyr-latest/doc/build/snippets/
Dwriting.rst15 .. code-block:: yaml
17 name: snippet-name
24 you can combine a snippet-specific devicetree overlay and a ``.conf`` file like
27 .. code-block:: yaml
29 name: foo
31 EXTRA_DTC_OVERLAY_FILE: foo.overlay
32 EXTRA_CONF_FILE: foo.conf
36 .. code-block:: yaml
38 name: foo
47 ``snippet-<name>`` as a namespace prefix when choosing names for node labels,
[all …]
Dusing.rst1 .. _using-snippets:
8 See :ref:`built-in-snippets` for a list of snippets that are provided by
11 Snippets have names. You use snippets by giving their names to the build
17 To use a snippet named ``foo`` when building an application ``app``:
19 .. code-block:: console
21 west build -S foo app
25 .. code-block:: console
27 west build -S snippet1 -S snippet2 [...] app
33 ``SNIPPET`` variable. This is a whitespace- or semicolon-separated list of
34 snippet names you want to use. For example:
[all …]
/Zephyr-latest/dts/bindings/test/
Dvnd,phandle-holder.yaml2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "vnd,phandle-holder"
13 phs-or: {type: "phandles"}
14 pha-gpios: {type: "phandle-array"}
15 gpios: {type: "phandle-array"}
16 foos: {type: "phandle-array"}
17 foo-names: {type: "string-array"}
18 pwms: {type: "phandle-array"}
19 pwm-names: {type: "string-array"}
21 type: "phandle-array"
[all …]
/Zephyr-latest/scripts/dts/python-devicetree/tests/
Dtest_dtlib.py2 # SPDX-License-Identifier: BSD-3-Clause
23 # - to stop on the first failure with shorter traceback output,
24 # use '-x --tb=native'
25 # - to drop into a debugger on failure, use '--pdb'
26 # - to run a particular test function or functions, use
27 # '-k test_function_pattern_goes_here'
34 fd, path = tempfile.mkstemp(prefix='pytest-', suffix='.dts')
36 os.write(fd, dts.encode('utf-8'))
44 representation is expected[1:-1].
52 expected = expected[1:-1]
[all …]
Dtest.dts4 * SPDX-License-Identifier: BSD-3-Clause
9 /dts-v1/;
16 interrupt-parent-test {
18 compatible = "interrupt-three-cell";
19 #interrupt-cells = <3>;
20 interrupt-controller;
24 interrupt-names = "foo", "bar";
25 interrupt-parent = <&{/interrupt-parent-test/controller}>;
28 interrupts-extended-test {
29 controller-0 {
[all …]
Dtest_edtlib.py2 # SPDX-License-Identifier: BSD-3-Clause
23 # test.dts is the main test file. test-bindings/ and test-bindings-2/ has
46 with from_here(): edtlib.EDT("test.dts", ["test-bindings"])
48 enums_hpath = hpath('test-bindings/enums.yaml')
50 … marked as deprecated in 'properties:' in {hpath('test-bindings/deprecated.yaml')} for node /test-…
51 "unit address and first address in 'reg' (0x1) don't match for /reg-zero-size-cells/node",
52 "unit address and first address in 'reg' (0x5) don't match for /reg-ranges/parent/node",
53 …"unit address and first address in 'reg' (0x30000000200000001) don't match for /reg-nested-ranges/…
54 …mpatible 'enums' in binding '{enums_hpath}' has non-tokenizable enum for property 'string-enum': '…
55 …f"compatible 'enums' in binding '{enums_hpath}' has enum for property 'tokenizable-lower-enum' tha…
[all …]
/Zephyr-latest/doc/build/dts/
Dbindings-syntax.rst1 .. _dt-bindings-file-syntax:
7 files are YAML files. A :ref:`simple example <dt-bindings-simple-example>` was
17 The top level of a bindings file maps keys to values. The top-level keys look
20 .. code-block:: yaml
24 This is the Vendomatic company's foo-device.
29 See https://yaml-multiline.info/ for formatting help.
35 compatible: "manufacturer,foo-device"
41 child-binding:
50 # SPI memory chip, use 'on-bus:' to say what type of bus, like this.
53 on-bus: spi
[all …]
Dintro-syntax-structure.rst1 .. _dt-syntax:
6 As the name indicates, a devicetree is a tree. The human-readable text format
24 .. code-block:: devicetree
26 /dts-v1/;
29 a-node {
30 subnode_nodelabel: a-sub-node {
31 foo = <3>;
36 The ``/dts-v1/;`` line means the file's contents are in version 1 of the DTS
37 syntax, which has replaced a now-obsolete "version 0".
46 #. A node named ``a-node``, which is a child of the root node
[all …]
Dapi-usage.rst1 .. _dt-from-c:
8 :ref:`devicetree-intro` and :ref:`dt-bindings`. See :ref:`dt-reference` for
26 .. _dt-node-identifiers:
43 label <dt-node-labels>`. Node labels are often provided by SoC :file:`.dtsi`
44 files to give nodes names that match the SoC datasheet, like ``i2c1``,
50 :zephyr:code-sample:`blinky`, which uses the ``led0`` alias) that need to
72 .. _dt-node-main-ex:
77 .. literalinclude:: main-example.dts
79 :start-after: start-after-here
83 - ``DT_PATH(soc, i2c_40002000)``
[all …]
Dtroubleshooting.rst1 .. _dt-trouble:
8 See :ref:`dt-howtos` for other "HOWTO" style information.
10 .. _dt-trouble-try-pristine:
17 See :ref:`west-building-pristine` for examples, or just delete the build
39 .. code-block:: c
43 where ``NODE_ID`` is a valid :ref:`node identifier <dt-node-identifiers>`, but
53 = "okay";``; see :ref:`dt-important-props` for more information about
73 .. code-block:: none
92 devicetree for your application build. (See :ref:`get-devicetree-outputs` for
97 :ref:`overlay <set-devicetree-overlays>`. For example, if :file:`zephyr.dts`
[all …]
Dbindings-intro.rst1 .. _dt-binding-compat:
8 For a detailed syntax reference, see :ref:`dt-bindings-file-syntax`.
11 properties <dt-important-props>`.
18 .. _dt-bindings-simple-example:
25 .. code-block:: devicetree
28 bar-device {
29 compatible = "foo-company,bar-device";
30 num-foos = <3>;
35 .. code-block:: yaml
39 compatible: "foo-company,bar-device"
[all …]
Dphandles.rst1 .. _dt-phandles:
19 .. code-block:: DTS
22 lbl_a: node-1 {};
23 lbl_b: lbl_c: node-2 {};
28 - ``/node-1`` as ``&lbl_a``
29 - ``/node-2`` as either ``&lbl_b`` or ``&lbl_c``
39 "Type" in this section refers to one of the type names documented in
40 :ref:`dt-bindings-properties` in the devicetree bindings documentation.
47 You can use phandles to refer to ``node-b`` from ``node-a``, where ``node-b``
48 is related to ``node-a`` in some way.
[all …]
Dbindings-upstream.rst1 .. _dt-writing-bindings:
21 Zephyr aims for devicetree :ref:`dt-source-compatibility`. Therefore, if there
24 justify any Zephyr-specific divergences.
28 - There is an existing binding in the mainline Linux kernel. See
32 - Your hardware vendor provides an official binding outside of the Linux
48 https://docs.kernel.org/devicetree/bindings/writing-bindings.html
50 File names
53 Bindings which match a compatible must have file names based on the compatible.
55 - For example, a binding for compatible ``vnd,foo`` must be named ``vnd,foo.yaml``.
56 - If the binding is bus-specific, you can append the bus to the file name;
[all …]
/Zephyr-latest/tests/lib/devicetree/api/
Dapp.overlay4 * SPDX-License-Identifier: Apache-2.0
8 * Names in this file should be chosen in a way that won't conflict
9 * with real-world devicetree nodes, to allow these tests to run on
15 test-alias = &test_nodelabel;
24 string = "foo";
28 #address-cells = < 0x1 >;
29 #size-cells = < 0x1 >;
30 interrupt-parent = <&test_intc>;
32 test_cpu_intc: interrupt-controller {
33 compatible = "vnd,cpu-intc";
[all …]
/Zephyr-latest/soc/nordic/common/
Dsoc_nrf_common.h3 * SPDX-License-Identifier: Apache-2.0
19 * @brief Get a PSEL value out of a foo-gpios or foo-pin devicetree property
21 * Many Nordic bindings have 'foo-pin' properties to specify a pin
22 * configuration as a PSEL value directly instead of using a 'foo-gpios'
25 * It would be better to use 'foo-gpios' properties instead. This type
28 * To allow for a smooth migration from 'foo-pin' to 'foo-gpios', this
30 * using whichever one of 'foo-gpios' or 'foo-pin' is in the DTS.
34 * - NRF_DT_PSEL_CHECK_*() to check the property configuration at build time
35 * - NRF_DT_GPIOS_TO_PSEL() if you only have a 'foo-gpios'
38 * @param psel_prop lowercase-and-underscores old-style 'foo-pin' property
[all …]
/Zephyr-latest/doc/develop/west/
Dmanifest.rst1 .. _west-manifests:
8 ``west.manifest`` module, see :ref:`west-apis-manifest`. For a more general
9 introduction and command overview, see :ref:`west-basics`.
16 .. _west-mr-model:
25 .. figure:: west-mr-model.png
27 :alt: West multi-repo history
28 :figclass: align-center
30 West multi-repo history
48 - Projects can be added (like ``P1`` between manifest repository
52 - Project and manifest repository histories don't have to move
[all …]
Dconfig.rst1 .. _west-config:
7 command, and configuration options used by built-in commands. For API
9 :ref:`west-apis-configuration`.
12 ------------------------
14 West's configuration file syntax is INI-like; here is an example file:
16 .. code-block:: ini
32 - Linux: :file:`/etc/westconfig`
33 - macOS: :file:`/usr/local/etc/westconfig`
34 - Windows: :file:`%PROGRAMDATA%\\west\\config`
39 - All platforms: the default is :file:`.westconfig` in the user's home
[all …]
/Zephyr-latest/scripts/dts/python-devicetree/src/devicetree/
Ddtlib.py2 # SPDX-License-Identifier: BSD-3-Clause
10 The top-level entry point of the library is the DT class. DT.__init__() takes a
30 "Exception raised for devicetree-related errors"
34 Represents a node in the devicetree ('node-name { ... };').
59 x = "foo", < 0x12345678 >, [ 9A ];
61 This gives x the value b"foo\0\x12\x34\x56\x78\x9A". Numbers in DTS are
62 stored in big-endian format.
78 The path to the node as a string, e.g. "/foo/bar".
113 def name(self) -> str:
117 # Converted to a property to discourage renaming -- that has to be done
[all …]
/Zephyr-latest/include/zephyr/devicetree/
Dpinctrl.h3 * SPDX-License-Identifier: Apache-2.0
15 * @defgroup devicetree-pinctrl Pin control
26 * pinctrl-0 = <&foo &bar>;
27 * pinctrl-1 = <&baz &blub>;
35 * @param node_id node with a pinctrl-'pc_idx' property
38 * @return node identifier for the phandle at index 'idx' in 'pinctrl-'pc_idx''
44 * @brief Get a node identifier from a pinctrl-0 property
50 * It is provided for convenience since pinctrl-0 is commonly used.
52 * @param node_id node with a pinctrl-0 property
53 * @param idx index into the pinctrl-0 property
[all …]
Dclocks.h9 * SPDX-License-Identifier: Apache-2.0
20 * @defgroup devicetree-clocks Devicetree Clocks API
26 * @brief Test if a node has a clocks phandle-array property at a given index
28 * This expands to 1 if the given index is valid clocks property phandle-array index.
33 * n1: node-1 {
37 * n2: node-2 {
49 * @param idx index of a clocks property phandle-array whose existence to check
56 * @brief Test if a node has a clock-names array property holds a given name
58 * This expands to 1 if the name is available as clocks-name array property cell.
63 * n1: node-1 {
[all …]
/Zephyr-latest/include/zephyr/data/
Djson.h4 * SPDX-License-Identifier: Apache-2.0
83 * power of 2 in order to keep this value in the 0-3 range
120 * @param data User-provided pointer
145 * struct foo {
149 * struct json_obj_descr foo[] = {
150 * JSON_OBJ_DESCR_PRIM(struct foo, some_int, JSON_TOK_NUMBER),
157 .field_name_len = sizeof(#field_name_) - 1, \
172 * int32_t foo;
182 * { ... declare foo descriptor ... },
190 .field_name_len = (sizeof(#field_name_) - 1), \
[all …]
/Zephyr-latest/doc/develop/
Dmodules.rst7 order to avoid reinventing the wheel and to reuse as much well-established,
14 modules, an external project is required to have its own life-cycle outside
29 - Debugger integration
30 - Silicon vendor Hardware Abstraction Layers (HALs)
31 - Cryptography libraries
32 - File Systems
33 - Inter-Process Communication (IPC) libraries
36 references to optional :ref:`binary blobs <bin-blobs>`.
41 .. _modules-vs-projects:
47 <west-workspace>`. In fact, modules :ref:`do not require west
[all …]
/Zephyr-latest/scripts/dts/
Dgen_dts_cmake.py4 # SPDX-License-Identifier: Apache-2.0
39 DT_PROP(node_id, foo) from devicetree.h.
48 sys.path.insert(0, os.path.join(os.path.dirname(__file__), 'python-devicetree',
69 # Returns parsed command-line arguments
72 parser.add_argument("--cmake-out", required=True,
74 parser.add_argument("--edt-pickle", required=True,
89 # whatever we want as target property names.
93 # names. This lets us store the "real" paths and property names
94 # without conversion to lowercase-and-underscores like we have to
97 # If CMake adds restrictions on target property names later, we
[all …]
/Zephyr-latest/include/zephyr/
Ddevicetree.h2 * SPDX-License-Identifier: Apache-2.0
39 * -----------------
42 * part in DT_N_<path-id>_P_<property-id> macros, or the "prop-suf"
71 * @defgroup devicetree-generic-id Node identifiers and helpers
96 * The arguments to this macro are the names of non-root nodes in the
98 * Non-alphanumeric characters in each name must be converted to
108 * current-speed = <115200>;
119 * Example usage with DT_PROP() to get the `current-speed` property:
125 * (The `current-speed` property is also in `lowercase-and-underscores`
130 * - the first argument corresponds to a child node of the root (`soc` above)
[all …]

123