Thanks Sergei, Is it better if the documentation say: " Optional property: - interrupt-parent: the phandle of the associated interrupt controller. " or should I also add that "it may be inherited from the parent nodes."? Jules Maselbas. ----- Mail original ----- De: "Sergei Shtylyov" <sergei.shtylyov@xxxxxxxxxxxxxxxxxx> À: "Jules Maselbas" <jules.maselbas@xxxxxxxxxxxxxxxx>, gregkh@xxxxxxxxxxxxxxxxxxx Cc: "julia lawall" <julia.lawall@xxxxxxx>, robh@xxxxxxxxxx, "mark rutland" <mark.rutland@xxxxxxx>, devicetree@xxxxxxxxxxxxxxx, linux-usb@xxxxxxxxxxxxxxx Envoyé: Lundi 16 Octobre 2017 22:21:53 Objet: Re: [PATCH v2 2/2] dt-bindings: max3421: Add bindings documentation On 10/16/2017 12:04 PM, Sergei Shtylyov wrote: >> Adds bindings documentation for the max3421 driver. >> >> Signed-off-by: Jules Maselbas <jules.maselbas@xxxxxxxxxxxxxxxx> >> --- >> .../devicetree/bindings/usb/maxim,max3421.txt | 24 >> ++++++++++++++++++++++ >> 1 file changed, 24 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/usb/maxim,max3421.txt >> >> diff --git a/Documentation/devicetree/bindings/usb/maxim,max3421.txt >> b/Documentation/devicetree/bindings/usb/maxim,max3421.txt >> new file mode 100644 >> index 000000000000..7536c3ab3e5a >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/usb/maxim,max3421.txt >> @@ -0,0 +1,24 @@ >> +Maxim Integrated SPI-based USB 2.0 host controller MAX3421E >> + >> +Required properties: >> + - compatible: "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. >> + - interrupt-parent: the phandle of the associated interrupt controller. > > This is never a required prob, it may be inherited from the parent nodes. Prop, sorry. :-) [...] MBR, Sergei -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
