Home
last modified time | relevance | path

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

123

/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dsrio-rmu.txt5 node is composed of three types of sub-nodes ("fsl-srio-msg-unit",
6 "fsl-srio-dbell-unit" and "fsl-srio-port-write-unit").
10 - compatible
13 Definition: Must include "fsl,srio-rmu-vX.Y", "fsl,srio-rmu".
18 - reg
20 Value type: <prop-encoded-array>
25 - fsl,liodn
26 Usage: optional-but-recommended (for devices with PAMU)
27 Value type: <prop-encoded-array>
33 (msg-unit, doorbell, port-write).
[all …]
H A Dsrio.txt5 - compatible
11 Optionally, a compatible string of "fsl,srio-vX.Y" where X is Major
15 - reg
17 Value type: <prop-encoded-array>
22 - interrupts
24 Value type: <prop_encoded-array>
27 specifier. The format of the specifier is defined by the
28 binding document describing the node's interrupt parent.
31 property. (Typically shared with port-write).
33 - fsl,srio-rmu-handle:
[all …]
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dinterrupts.txt5 -------------------------
8 "interrupts" property, an "interrupts-extended" property, or both. If both are
12 format of the interrupt specifier is determined by the interrupt controller to
16 interrupt-parent = <&intc1>;
19 The "interrupt-parent" property is used to specify the controller to which
22 interrupt client node or in any of its parent nodes. Interrupts listed in the
23 "interrupts" property are always in reference to the node's interrupt parent.
25 The "interrupts-extended" property is a special form; useful when a node needs
26 to reference multiple interrupt parents or a different interrupt parent than
27 the inherited one. Each entry in this property contains both the parent phandle
[all …]
H A Dmsi.txt14 - The doorbell (the MMIO address written to).
19 - The payload (the value written to the doorbell).
24 - Sideband information accompanying the write.
38 --------------------
40 - msi-controller: Identifies the node as an MSI controller.
43 --------------------
45 - #msi-cells: The number of cells in an msi-specifier, required if not zero.
50 The meaning of the msi-specifier is defined by the device tree binding of
62 --------------------
64 - msi-parent: A list of phandle + msi-specifier pairs, one for each MSI
[all …]
H A Dmsi-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/msi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <maz@kernel.org>
18 "#msi-cells":
20 The number of cells in an msi-specifier, required if not zero.
26 The meaning of the msi-specifier is defined by the device tree
30 msi-controller:
35 msi-ranges:
[all …]
/linux/Documentation/devicetree/bindings/iommu/
H A Diommu.txt13 Example: 32-bit DMA to 64-bit physical addresses
15 * Implement scatter-gather at page level granularity so that the device does
29 IOMMUs can be single-master or multiple-master. Single-master IOMMU devices
30 typically have a fixed association to the master device, whereas multiple-
33 The device tree node of the IOMMU device's parent bus must contain a valid
34 "dma-ranges" property that describes how the physical address space of the
35 IOMMU maps to memory. An empty "dma-ranges" property means that there is a
39 --------------------
40 - #iommu-cells: The number of cells in an IOMMU specifier needed to encode an
43 The meaning of the IOMMU specifier is defined by the device tree binding of
[all …]
/linux/Documentation/devicetree/bindings/display/imx/
H A Dnxp,imx8mq-dcss.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/imx/nxp,imx8mq-dcss.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Laurentiu Palcu <laurentiu.palcu@nxp.com>
17 2.2) or MIPI-DSI. The DCSS is intended to support up to 4kp60 displays. HDR10
23 const: nxp,imx8mq-dcss
27 - description: DCSS base address and size, up to IRQ steer start
28 - description: DCSS BLKCTL base address and size
32 - description: Context loader completion and error interrupt
[all …]
/linux/Documentation/devicetree/bindings/media/
H A Dhix5hd2-ir.txt1 Device-Tree bindings for hix5hd2 ir IP
4 - compatible: Should contain "hisilicon,hix5hd2-ir", or:
5 - "hisilicon,hi3796cv300-ir" for Hi3796CV300 IR device.
6 - reg: Base physical address of the controller and length of memory
8 - interrupts: interrupt-specifier for the sole interrupt generated by
9 the device. The interrupt specifier format depends on the interrupt
10 controller parent.
11 - clocks: clock phandle and specifier pair.
14 - linux,rc-map-name: see rc.txt file in the same directory.
15 - hisilicon,power-syscon: DEPRECATED. Don't use this in new dts files.
[all …]
H A Dst-rc.txt1 Device-Tree bindings for ST IRB IP
4 - compatible: Should contain "st,comms-irb".
5 - reg: Base physical address of the controller and length of memory
7 - interrupts: interrupt-specifier for the sole interrupt generated by
8 the device. The interrupt specifier format depends on the interrupt
9 controller parent.
10 - rx-mode: can be "infrared" or "uhf". This property specifies the L1
11 protocol used for receiving remote control signals. rx-mode should
13 - tx-mode: should be "infrared". This property specifies the L1
14 protocol used for transmitting remote control signals. tx-mode should
[all …]
/linux/Documentation/devicetree/bindings/hsi/
H A Domap-ssi.txt9 - compatible: Should include "ti,omap3-ssi" or "ti,omap4-hsi"
10 - reg-names: Contains the values "sys" and "gdd" (in this order).
11 - reg: Contains a matching register specifier for each entry
12 in reg-names.
13 - interrupt-names: Contains the value "gdd_mpu".
14 - interrupts: Contains matching interrupt information for each entry
15 in interrupt-names.
16 - ranges: Represents the bus address mapping between the main
18 - clock-names: Must include the following entries:
22 - clocks: Contains a matching clock specifier for each entry in
[all …]
/linux/Documentation/devicetree/bindings/mailbox/
H A Daltera-mailbox.txt5 - compatible : "altr,mailbox-1.0".
6 - reg : physical base address of the mailbox and length of
8 - #mbox-cells: Common mailbox binding property to identify the number
9 of cells required for the mailbox specifier. Should be 1.
12 - interrupts : interrupt number. The interrupt specifier format
13 depends on the interrupt controller parent.
17 compatible = "altr,mailbox-1.0";
19 interrupt-parent = < &gic_0 >;
21 #mbox-cells = <1>;
25 compatible = "altr,mailbox-1.0";
[all …]
H A Dti,omap-mailbox.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
35 lines can also be routed to different processor sub-systems on DRA7xx as they
49 within a SoC. The sub-mailboxes (actual communication channels) are
50 represented as child nodes of this parent node.
56 "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
58 the mailbox controller device node and an args specifier that will be the
[all …]
/linux/Documentation/devicetree/bindings/misc/
H A Dfsl,qoriq-mc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/misc/fsl,qoriq-m
[all...]
/linux/kernel/irq/
H A Dirqdomain.c1 // SPDX-License-Identifier: GPL-2.0
38 struct fwnode_handle *parent;
56 return fwid->name;
63 return fwid->parent;
73 * __irq_domain_alloc_fwnode - Allocate a fwnode_handle suitable for
78 * @pa: Optional user-provided physical address
79 * @parent
36 struct fwnode_handle *parent; global() member
90 __irq_domain_alloc_fwnode(unsigned int type,int id,const char * name,phys_addr_t * pa,struct fwnode_handle * parent) __irq_domain_alloc_fwnode() argument
1474 struct irq_domain *parent; irq_domain_alloc_irq_data() local
[all...]
/linux/drivers/of/
H A Dirq.c1 // SPDX-License-Identifier: GPL-2.0+
6 * Copyright (C) 1995-1996 Gary Thomas (gdt@linuxppc.org)
8 * Copyright (C) 1996-2001 Cort Dougan
32 * irq_of_parse_and_map - Parse and map an interrupt into linux virq space
55 * of_irq_find_parent - Given a device node, find its interrupt parent node
58 * Return: A pointer to the interrupt parent node with refcount increased
59 * or NULL if the interrupt parent coul
64 phandle parent; of_irq_find_parent() local
652 struct device_node *np, *parent = NULL; of_irq_init() local
[all...]
/linux/Documentation/devicetree/bindings/gpio/
H A Dgpio-adnp.txt1 Avionic Design N-bit GPIO expander bindings
4 - compatible: should be "ad,gpio-adnp"
5 - reg: The I2C slave address for this device.
6 - interrupts: Interrupt specifier for the controllers interrupt.
7 - #gpio-cells: Should be 2. The first cell is the GPIO number and the
9 - bit 0: polarity (0: normal, 1: inverted)
10 - gpio-controller: Marks the device as a GPIO controller
11 - nr-gpios: The number of pins supported by the controller.
14 which case it uses the default two cell specifier as described in
15 Documentation/devicetree/bindings/interrupt-controller/interrupts.txt.
[all …]
/linux/Documentation/devicetree/bindings/net/bluetooth/
H A Dbrcm,bluetooth.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linusw@kernel.org>
13 This binding describes Broadcom UART-attached bluetooth chips.
18 - items:
19 - enum:
20 - infineon,cyw43439-bt
21 - const: brcm,bcm4329-bt
22 - enum:
[all …]
/linux/Documentation/devicetree/bindings/power/
H A Dpower-domain.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rafael J. Wysocki <rafael@kernel.org>
11 - Kevi
[all...]
/linux/Documentation/devicetree/bindings/watchdog/
H A Drealtek,otto-wdt.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/watchdog/realtek,otto-wdt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sander Vanheule <sander@svanheule.net>
17 - Phase 1: During this phase, the WDT can be pinged to reset the timeout.
18 - Phase 2: Starts after phase 1 has timed out, and only serves to give the
24 - $ref: watchdog.yaml#
29 - realtek,rtl8380-wdt
30 - realtek,rtl8390-wdt
[all …]
/linux/Documentation/devicetree/bindings/input/
H A Datmel,maxtouch.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schema
[all...]
/linux/Documentation/devicetree/bindings/display/bridge/
H A Dti,sn65dsi86.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Douglas Anderson <dianders@chromium.org>
23 enable-gpios:
25 description: GPIO specifier for bridge_en pin (active high).
27 suspend-gpios:
29 description: GPIO specifier for GPIO1 pin on bridge (active low).
31 no-hpd:
37 vccio-supply:
[all …]
/linux/drivers/of/unittest-data/
H A Dtestcases.dtso1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
13 testcase-data {
14 testcase-device2 {
15 compatible = "testcase-device";
16 interrupt-parent = <&test_intc2>;
17 interrupts = <1>; /* invalid specifier - too short */
/linux/Documentation/devicetree/bindings/rtc/
H A Dcdns,rtc.txt4 The alarm may wake the system from low-power state.
7 - compatible: Should be "cdns,rtc-r109v3"
8 - reg: Specifies base physical address and size of the register area.
9 - interrupts: A single interrupt specifier.
10 - clocks: Must contain two entries:
11 - pclk: APB registers clock
12 - ref_clk: reference 1Hz or 100Hz clock, depending on IP configuration
13 See ../clocks/clock-bindings.txt for details.
17 compatible = "cdns,rtc-r109v3";
20 clock-names = "pclk", "ref_clk";
[all …]
/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,davinci-rproc.txt4 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
5 is used to offload some of the processor-intensive tasks or algorithms, for
8 The processor cores in the sub-system usually contain additional sub-modules
15 Each DSP Core sub-system is represented as a single DT node.
18 --------------------
21 - compatible: Should be one of the following,
22 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
24 - reg: Should contain an entry for each value in 'reg-names'.
27 the parent node's '#address-cells' and '#size-cells' values.
29 - reg-names: Should contain strings with the following names, each
[all …]
/linux/Documentation/devicetree/bindings/mfd/
H A Dnetronix,ntxec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jonathan Neuschäfer <j.neuschaefer@gmx.net>
13 This EC is found in e-book readers of multiple brands (e.g. Kobo, Tolino), and
22 - description: The I2C address of the EC
24 system-power-controller:
26 description: See Documentation/devicetree/bindings/power/power-controller.txt
33 "#pwm-cells":
36 Number of cells in a PWM specifier.
[all …]

123