Home
last modified time | relevance | path

Searched refs:phandle (Results 1 – 25 of 31) sorted by relevance

12

/Zephyr-latest/doc/build/dts/
Dphandles.rst6 The devicetree concept of a *phandle* is very similar to pointers in
16 The usual way to get a phandle for a devicetree node is from one of its node
26 You can write the phandle for:
44 One node: phandle type
68 These properties have type ``phandle``.
89 Zero or more nodes with metadata: phandle-array type
98 These properties have type ``phandle-array``.
100 .. _dt-phandle-arrays:
102 phandle-array properties
111 Usually, properties with this type are written like ``phandle-array-prop`` in
[all …]
Dapi-usage.rst131 - :ref:`phandle-properties`
295 phandle properties
302 Property values can refer to other nodes using the ``&another-node`` phandle
304 contain phandles have type ``phandle``, ``phandles``, or ``phandle-array`` in
305 their bindings. We'll call these "phandle properties" for short.
307 You can convert a phandle to a node identifier using :c:macro:`DT_PHANDLE`,
311 One common use case for phandle properties is referring to other hardware in
313 phandle to a Zephyr driver-level :ref:`struct device <device_model_api>`.
316 Another common use case is accessing specifier values in a phandle array. The
324 check if a specifier value is present in a phandle property.
Dbindings-syntax.rst163 phandle | phandles | phandle-array | path | compound>
262 about the ``phandle*`` type properties.
296 * - ``phandle``
297 - exactly one phandle
304 * - ``phandle-array``
309 - a path to a node as a phandle path reference or path string
390 property with type ``phandle-array``.
393 property named ``foos`` with type ``phandle-array`` implicitly has specifier
408 type: phandle-array
438 type: phandle-array
[all …]
Dintro-syntax-structure.rst361 * - phandle
363 - ``a-phandle = <&mynode>;``
369 * - phandle-array
371 - ``a-phandle-array = <&mynode0 1 2>, <&mynode1 3 4>;``
375 - The values in the ``phandle``, ``phandles``, and ``phandle-array`` types are
402 You can write a phandle using ``&foo``, where ``foo`` is a :ref:`node label
414 #. The ``device@0`` node's phandle, which is written here as ``&foo`` since
419 In the devicetree, a phandle value is a cell -- which again is just a 32-bit
431 foo = <&label1 1 2>, <&label2 3 4>; // Okay for 'type: phandle-array'
Dmacros.bnf149 ; The node identifier for the phandle in a named pinctrl property.
202 ; The node identifier for the phandle of a logical index in the GPIO hogs array.
303 ; - with array types (uint8-array, phandle-array, etc.)
305 ; - that have zephyr device API specific macros for phandle-arrays
306 ; - related to phandle specifier names ("foo-names")
314 ; cells within a phandle array
/Zephyr-latest/scripts/dts/python-devicetree/tests/
Dtest.dts357 phandle-ref = < &{/ctrl-1} >;
358 phandle-refs = < &{/ctrl-1} &{/ctrl-2} >;
359 phandle-array-foos = < &{/ctrl-1} 1 &{/ctrl-2} 2 3 >;
365 compatible = "phandle-array-controller-1";
366 #phandle-array-foo-cells = <1>;
371 compatible = "phandle-array-controller-2";
372 #phandle-array-foo-cells = <2>;
377 phandle-array-foos = < &{/ctrl-0-1} 0 &{/ctrl-0-2} >;
378 phandle-array-foo-names = "a", "missing", "b";
382 compatible = "phandle-array-controller-0";
[all …]
Dtest_dtlib.py819 phandle = dtlib.to_num(dt.root.props[prop].value[offset:offset + 4])
820 actual_name = dt.phandle2node[phandle].name
/Zephyr-latest/boards/toradex/colibri_imx7d/doc/
Dindex.rst256 #You need to find the following phandle numbers:
260 #Note down the phandle value (0xbd)
270 # phandle = <0xbd>;
273 #Note down the phandle value (0x32)
281 # phandle = <0x32>;
284 #Node down the biggest phandle value
285 grep "phandle = <" imx7d-colibri-emmc-eval-v3.dts | sort -r | head -1
286 # outputs your DTS's largest phandle definition
287 # phandle = <0xca>;
301 phandle = <0xbd>;
[all …]
/Zephyr-latest/samples/subsys/tracing/
Dgpio.overlay17 phandle = < 0x1 >;
/Zephyr-latest/tests/drivers/build_all/gpio/
Daltera.overlay20 phandle = < 0x1 >;
/Zephyr-latest/drivers/i3c/
DKconfig.npcx21 # as the second group in the phandle-array.
/Zephyr-latest/dts/arm/
Dcortex_r8_virt.dtsi60 phandle = < 0x1 >;
/Zephyr-latest/samples/drivers/led/pwm/
DREADME.rst34 defined and the PWM configuration must be provided through a "pwms" phandle's
/Zephyr-latest/samples/drivers/led/pwm/boards/
Dmec15xxevb_assy6853.overlay25 /* struct pwm_dt_spec: phandle channel period(ns) flags */
Dmec172xevb_assy6906.overlay27 /* struct pwm_dt_spec: phandle channel period(ns) flags */
/Zephyr-latest/samples/subsys/fs/fs_sample/boards/
Dnrf52840dk_nrf52840_ram_disk_region.overlay51 * disk using a phandle; note that we reference the
/Zephyr-latest/scripts/kconfig/
Dkconfigfunctions.py685 phandle = node.props[prop].val
687 return phandle.path if phandle else ""
/Zephyr-latest/scripts/dts/python-devicetree/src/devicetree/
Ddtlib.py1763 phandle = node.props.get("phandle")
1764 if phandle:
1765 if len(phandle.value) != 4:
1770 for marker in phandle._markers:
1788 phandle_val = int.from_bytes(phandle.value, "big")
Dedtlib.py2979 phandle = to_num(raw[:4])
2983 map_parent = parent.dt.phandle2node.get(phandle)
3133 phandle = to_num(raw[:4])
3136 node = prop.node.dt.phandle2node.get(phandle)
/Zephyr-latest/tests/lib/devicetree/api/
Dapp.overlay58 test_phandles: phandle-holder-0 {
60 * There should only be one vnd,phandle-holder in the entire DTS.
62 compatible = "vnd,phandle-holder";
/Zephyr-latest/subsys/usb/device_next/class/
Dusbd_uac2_macros.h124 #define CONNECTED_ENTITY_ID(entity, phandle) \ argument
125 COND_CODE_1(DT_NODE_HAS_PROP(entity, phandle), \
126 (ENTITY_ID(DT_PHANDLE_BY_IDX(entity, phandle, 0))), (0))
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst173 ``forwards`` attribute consists of the phandle followed by the address. In
/Zephyr-latest/doc/build/dts/api/
Dapi.rst143 - a node directly depends on any nodes its properties refer to by phandle
/Zephyr-latest/doc/build/kconfig/
Dtips.rst76 type phandle-array in the device binding, and using the
/Zephyr-latest/doc/releases/
Dmigration-guide-3.7.rst265 Added new phandle-array type DT property ``nxp,references``, the user can use this

12