mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-21 02:27:02 +07: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>
25 lines
825 B
Plaintext
25 lines
825 B
Plaintext
KEYMILE bfticu Chassis Management FPGA
|
|
|
|
The bfticu is a multifunction device that manages the whole chassis.
|
|
Its main functionality is to collect IRQs from the whole chassis and signals
|
|
them to a single controller.
|
|
|
|
Required properties:
|
|
- compatible: "keymile,bfticu"
|
|
- interrupt-controller: the bfticu FPGA is an interrupt controller
|
|
- interrupts: the main IRQ line to signal the collected IRQs
|
|
- #interrupt-cells : is 2 and their usage is compliant to the 2 cells variant
|
|
of Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
|
|
- reg: access on the parent local bus (chip select, offset in chip select, size)
|
|
|
|
Example:
|
|
|
|
chassis-mgmt@3,0 {
|
|
compatible = "keymile,bfticu";
|
|
interrupt-controller;
|
|
#interrupt-cells = <2>;
|
|
reg = <3 0 0x100>;
|
|
interrupt-parent = <&mpic>;
|
|
interrupts = <6 1 0 0>;
|
|
};
|