mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +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
703 B
Plaintext
25 lines
703 B
Plaintext
* Microchip MCP251X stand-alone CAN controller device tree bindings
|
|
|
|
Required properties:
|
|
- compatible: Should be one of the following:
|
|
- "microchip,mcp2510" for MCP2510.
|
|
- "microchip,mcp2515" for MCP2515.
|
|
- reg: SPI chip select.
|
|
- clocks: The clock feeding the CAN controller.
|
|
- interrupts: Should contain IRQ line for the CAN controller.
|
|
|
|
Optional properties:
|
|
- vdd-supply: Regulator that powers the CAN controller.
|
|
- xceiver-supply: Regulator that powers the CAN transceiver.
|
|
|
|
Example:
|
|
can0: can@1 {
|
|
compatible = "microchip,mcp2515";
|
|
reg = <1>;
|
|
clocks = <&clk24m>;
|
|
interrupt-parent = <&gpio4>;
|
|
interrupts = <13 0x2>;
|
|
vdd-supply = <®5v0>;
|
|
xceiver-supply = <®5v0>;
|
|
};
|