791d3ef2e1
'interrupt-parent' is often documented as part of define bindings, but it is really outside the scope of a device binding. It's never required in a given node as it is often inherited from a parent node. Or it can be implicit if a parent node is an 'interrupt-controller' node. So remove it from all the binding files. Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Rob Herring <robh@kernel.org>
31 lines
1 KiB
Plaintext
31 lines
1 KiB
Plaintext
* Freescale Layerscape SCFG PCIe MSI controller
|
|
|
|
Required properties:
|
|
|
|
- compatible: should be "fsl,<soc-name>-msi" to identify
|
|
Layerscape PCIe MSI controller block such as:
|
|
"fsl,ls1021a-msi"
|
|
"fsl,ls1043a-msi"
|
|
"fsl,ls1046a-msi"
|
|
"fsl,ls1043a-v1.1-msi"
|
|
"fsl,ls1012a-msi"
|
|
- msi-controller: indicates that this is a PCIe MSI controller node
|
|
- reg: physical base address of the controller and length of memory mapped.
|
|
- interrupts: an interrupt to the parent interrupt controller.
|
|
|
|
This interrupt controller hardware is a second level interrupt controller that
|
|
is hooked to a parent interrupt controller: e.g: ARM GIC for ARM-based
|
|
platforms. If interrupt-parent is not provided, the default parent interrupt
|
|
controller will be used.
|
|
Each PCIe node needs to have property msi-parent that points to
|
|
MSI controller node
|
|
|
|
Examples:
|
|
|
|
msi1: msi-controller@1571000 {
|
|
compatible = "fsl,ls1043a-msi";
|
|
reg = <0x0 0x1571000 0x0 0x8>,
|
|
msi-controller;
|
|
interrupts = <0 116 0x4>;
|
|
};
|