mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-25 12:04:46 +08:00
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>
26 lines
692 B
Plaintext
26 lines
692 B
Plaintext
Alpine MSIX controller
|
|
|
|
See arm,gic-v3.txt for SPI and MSI definitions.
|
|
|
|
Required properties:
|
|
|
|
- compatible: should be "al,alpine-msix"
|
|
- reg: physical base address and size of the registers
|
|
- interrupt-controller: identifies the node as an interrupt controller
|
|
- msi-controller: identifies the node as an PCI Message Signaled Interrupt
|
|
controller
|
|
- al,msi-base-spi: SPI base of the MSI frame
|
|
- al,msi-num-spis: number of SPIs assigned to the MSI frame, relative to SPI0
|
|
|
|
Example:
|
|
|
|
msix: msix {
|
|
compatible = "al,alpine-msix";
|
|
reg = <0x0 0xfbe00000 0x0 0x100000>;
|
|
interrupt-parent = <&gic>;
|
|
interrupt-controller;
|
|
msi-controller;
|
|
al,msi-base-spi = <160>;
|
|
al,msi-num-spis = <160>;
|
|
};
|