Home
last modified time | relevance | path

Searched +full:child +full:- +full:ref (Results 1 – 25 of 51) sorted by relevance

123

/Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings/
Dchild-binding.yaml1 # SPDX-License-Identifier: BSD-3-Clause
3 description: child-binding test
5 compatible: "top-binding"
7 child-binding:
8 description: child node
10 child-prop:
13 child-ref:
16 child-binding:
19 grandchild-prop:
22 grandchild-ref:
/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 {
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
47 #. A node named ``a-sub-node``, which is a child of ``a-node``
[all …]
Dbindings-intro.rst1 .. _dt-binding-compat:
8 For a detailed syntax reference, see :ref:`dt-bindings-file-syntax`.
10 Devicetree nodes are matched to bindings using their :ref:`compatible
11 properties <dt-important-props>`.
13 During the :ref:`build_configuration_phase`, the build system tries to match
18 .. _dt-bindings-simple-example:
25 .. code-block:: devicetree
28 bar-device {
29 compatible = "foo-company,bar-device";
30 num-foos = <3>;
[all …]
Dapi-usage.rst1 .. _dt-from-c:
8 :ref:`devicetree-intro` and :ref:`dt-bindings`. See :ref:`dt-reference` for
26 .. _dt-node-identifiers:
42 Use :c:macro:`DT_NODELABEL()` to get a node identifier from a :ref:`node
43 label <dt-node-labels>`. Node labels are often provided by SoC :file:`.dtsi`
50 :zephyr:code-sample:`blinky`, which uses the ``led0`` alias) that need to
65 By parent/child
67 for a parent or child node, starting from a node identifier you already have.
72 .. _dt-node-main-ex:
77 .. literalinclude:: main-example.dts
[all …]
/Zephyr-latest/include/zephyr/devicetree/
Dfixed-partitions.h9 * SPDX-License-Identifier: Apache-2.0
20 * @defgroup devicetree-fixed-partition Devicetree Fixed Partition API
33 * compatible = "fixed-partitions";
38 * label = "image-0";
49 * @param label lowercase-and-underscores label property value
57 * @param label lowercase-and-underscores label property value
58 * @return 1 if any "fixed-partitions" child node has the given label,
65 * @brief Test if fixed-partition compatible node exists
68 * @return 1 if node exists and is fixed-partition compatible, 0 otherwise.
75 * @param node_id node identifier for a fixed-partitions child node
[all …]
/Zephyr-latest/scripts/dts/python-devicetree/tests/
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 …f"compatible '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 …]
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 …]
/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
33 "floating" on top of the gray plane. Parent commits point to child commits
36 rectangle. Parent/child commit relationships in each repository are also shown
[all …]
/Zephyr-latest/doc/_scripts/
Dgen_devicetree_rest.py2 # SPDX-License-Identifier: Apache-2.0
26 GENERIC_OR_VENDOR_INDEPENDENT = 'Generic or vendor-independent'
31 # Base properties that have documentation in 'dt-important-props'.
59 # Load the vendor-prefixes.txt file. Return a dict mapping 'vnd'
65 # vnd A stand-in for a real vendor
67 # Gets split into a key 'vnd' and a value 'A stand-in for a real
77 logger.info('found %d vendor prefixes in %s', len(vnd2vendor) - 1,
92 # - The 'None' key maps to bindings with no vendor prefix
93 # in their compatibles, like 'gpio-keys'. This is the first key.
94 # - The (UNKNOWN_VENDOR,) key maps to bindings whose compatible
[all …]
/Zephyr-latest/dts/bindings/regulator/
Drenesas,da1469x-regulator.yaml2 # SPDX-License-Identifier: Apache-2.0
7 compatible: "renesas,smartbond-regulator"
9 child-binding:
11 - name: regulator.yaml
12 property-allowlist:
13 - regulator-always-on
14 - regulator-boot-on
15 - regulator-init-microvolt
16 - regulator-initial-mode
17 - regulator-max-microamp
[all …]
/Zephyr-latest/samples/basic/button/
DREADME.rst1 .. zephyr:code-sample:: button
3 :relevant-api: gpio_interface
14 debouncing, check out :ref:`input` and :zephyr:code-sample:`input-dump`
21 called "User buttons" on many of Zephyr's :ref:`boards`.
23 The button must be configured using the ``sw0`` :ref:`devicetree <dt-guide>`
24 alias, usually in the :ref:`BOARD.dts file <devicetree-in-out-files>`. You will
27 .. code-block:: none
35 the same alias used by the :zephyr:code-sample:`blinky` sample. If this is provided, the LED
48 .. code-block:: devicetree
58 gpio-controller;
[all …]
/Zephyr-latest/samples/drivers/adc/adc_sequence/
DREADME.rst1 .. zephyr:code-sample:: adc_sequence
2 :name: Analog-to-Digital Converter (ADC) sequence sample
3 :relevant-api: adc_interface
10 This sample demonstrates how to use the :ref:`ADC driver API <adc_api>` using sequences.
24 child node, with your desired settings like gain, reference, or acquisition time and
34 :ref:`nrf52840dk_nrf52840` as follows:
36 .. zephyr-app-commands::
37 :zephyr-app: samples/drivers/adc/adc_sequence
50 .. code-block:: console
53 - ADC_0, channel 0, 5 sequence samples:
[all …]
/Zephyr-latest/dts/bindings/pinctrl/
Dene,kb1200-pinctrl.yaml1 # SPDX-License-Identifier: Apache-2.0
9 - bias-disable: Disable pull-up/down resistor.
10 - bias-pull-up: Enable pull-up resistor.
11 - bias-pull-down: Enable pull-down resistor.
12 - drive-push-pull: Output driver is push-pull.
13 - drive-open-drain: Output driver is open-drain.
14 - output-disable: Disable GPIO output driver data
15 - output-enable: Ensable GPIO output driver data
16 - output-high: GPIO output data high
17 - output-low: GPIO output data low
[all …]
Dinfineon,cat1-pinctrl.yaml4 # SPDX-License-Identifier: Apache-2.0
11 UART0 RX to a particular port/pin and enable the pull-up resistor on that
22 'bias-pull-up' property. Here is a list of the supported standard pin
24 * bias-high-impedance
25 * bias-pull-up
26 * bias-pull-down
27 * drive-open-drain
28 * drive-open-source
29 * drive-push-pull (strong)
30 * input-enable (input-buffer)
[all …]
/Zephyr-latest/doc/build/dts/api/
Dapi.rst10 Some of these -- the ones beginning with ``DT_INST_`` -- require a special
13 :ref:`device drivers <device_model_api>`, though they can be used outside of
19 .. _devicetree-generic-apis:
33 :ref:`devicetree-property-access` API.
41 child node, respectively.
45 .. doxygengroup:: devicetree-generic-id
47 .. _devicetree-property-access:
52 The following general-purpose macros can be used to access node properties.
53 There are special-purpose APIs for accessing the :ref:`devicetree-ranges-property`,
54 :ref:`devicetree-reg-property` and :ref:`devicetree-interrupts-property`.
[all …]
/Zephyr-latest/samples/drivers/adc/adc_dt/
DREADME.rst1 .. zephyr:code-sample:: adc_dt
2 :name: Analog-to-Digital Converter (ADC) with devicetree
3 :relevant-api: adc_interface
10 This sample demonstrates how to use the :ref:`ADC driver API <adc_api>`.
16 The pins of the ADC channels are board-specific. Please refer to the board
26 ``io-channels`` property of the ``zephyr,user`` node. This is usually done with
31 also needs to be specified in devicetree, in ADC controller child nodes. Also
43 .. zephyr-app-commands::
44 :zephyr-app: samples/drivers/adc/adc_dt
57 .. code-block:: console
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart_async/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart_async
3 :relevant-api: hci_raw bluetooth uart_interface
43 instructions in the :ref:`bluetooth_bluez` section.
48 found in :ref:`nordic_segger`.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart_async
57 .. _bluetooth-hci-uart-async-qemu-posix:
62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
66 .. code-block:: console
68 sudo btattach -B /dev/ttyACM0 -S 1000000 -R
[all …]
/Zephyr-latest/doc/build/flashing/
Dconfiguration.rst1 .. _flashing-soc-board-config:
7 :ref:`west flash<west-flashing>`) which allows for customising how commands are used when
8 programming boards. This configuration is used for :ref:`sysbuild` projects and allows for
9 configuring when commands are ran for groups of board targets. As an example: a multi-core SoC
10 might want to only allow the ``--erase`` argument to be used once for all of the cores in the SoC
27 child, this then contains a map of commands as they would be provided to the flash runner e.g.
28 ``--reset`` followed by a list which specifies the settings for each of these commands (these
31 runners, otherwise must contain each runner that it applies to using the runner-specific name.
41 An example flashing configuration for a ``soc.yml`` is shown below in which the ``--recover``
46 .. code-block:: yaml
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart_3wire/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart_3wire
2 :name: HCI 3-wire (H:5)
3 :relevant-api: hci_raw bluetooth uart_interface
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
43 instructions in the :ref:`bluetooth_bluez` section.
48 found in :ref:`nordic_segger`.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart_3wire
57 .. _bluetooth-hci-uart-3wire-qemu-posix:
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart
3 :relevant-api: hci_raw bluetooth uart_interface
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
43 instructions in the :ref:`bluetooth_bluez` section.
48 found in :ref:`nordic_segger`.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart
57 .. _bluetooth-hci-uart-qemu-posix:
62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
[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 { ... };').
62 stored in big-endian format.
113 def name(self) -> str:
117 # Converted to a property to discourage renaming -- that has to be done
122 def unit_addr(self) -> str:
129 def path(self) -> str:
144 def node_iter(self) -> Iterable['Node']:
[all …]
/Zephyr-latest/doc/kernel/services/threads/
Dindex.rst7 There is also limited support for using :ref:`nothread`.
37 allocate CPU time to the thread. (See :ref:`scheduling_v2`.)
41 (See :ref:`thread_options_v2`.)
50 This depends on the :kconfig:option:`CONFIG_USERSPACE` option. See :ref:`usermode_api`.
69 value -- for example, to allow device hardware used by the thread
75 re-spawned before it can be used.
91 thread self-exits, or the target thread aborts (either due to a
96 re-used for any purpose, including spawning a new thread. Note that
176 - There may need to be additional memory reserved for memory management
178 - If guard-based stack overflow detection is enabled, a small write-protected
[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