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>
24 lines
791 B
Plaintext
24 lines
791 B
Plaintext
Maxim Integrated SPI-based USB 2.0 host controller MAX3421E
|
|
|
|
Required properties:
|
|
- compatible: Should be "maxim,max3421"
|
|
- spi-max-frequency: maximum frequency for this device must not exceed 26 MHz.
|
|
- reg: chip select number to which this device is connected.
|
|
- maxim,vbus-en-pin: <GPOUTx ACTIVE_LEVEL>
|
|
GPOUTx is the number (1-8) of the GPOUT pin of MAX3421E to drive Vbus.
|
|
ACTIVE_LEVEL is 0 or 1.
|
|
- interrupts: the interrupt line description for the interrupt controller.
|
|
The driver configures MAX3421E for active low level triggered interrupts,
|
|
configure your interrupt line accordingly.
|
|
|
|
Example:
|
|
|
|
usb@0 {
|
|
compatible = "maxim,max3421";
|
|
reg = <0>;
|
|
maxim,vbus-en-pin = <3 1>;
|
|
spi-max-frequency = <26000000>;
|
|
interrupt-parent = <&PIC>;
|
|
interrupts = <42>;
|
|
};
|