On Fri, Jul 08, 2016 at 11:07:30AM +0200, Linus Walleij wrote: > This adds device tree bindings for: > > - An optional GPIO line for releasing the RESET signal to the > SMSC911x devices > > - An optional PME (power management event) interrupt line that > can be utilized to wake up the system on network activity. > This signal exist on all the SMSC911x devices, it is just not > very often routed. > > Both these lines are routed to the SoC on the Qualcomm APQ8060 > Dragonboard and thus needs to be bound in the device tree. > > Cc: devicetree@xxxxxxxxxxxxxxx > Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/net/smsc911x.txt | 16 ++++++++++++---- > 1 file changed, 12 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/net/smsc911x.txt b/Documentation/devicetree/bindings/net/smsc911x.txt > index 3fed3c124411..7b01c37272c1 100644 > --- a/Documentation/devicetree/bindings/net/smsc911x.txt > +++ b/Documentation/devicetree/bindings/net/smsc911x.txt > @@ -3,9 +3,12 @@ > Required properties: > - compatible : Should be "smsc,lan<model>", "smsc,lan9115" > - reg : Address and length of the io space for SMSC LAN > -- interrupts : Should contain SMSC LAN interrupt line > -- interrupt-parent : Should be the phandle for the interrupt controller > - that services interrupts for this device > +- interrupts/extended-interrupts : Should contain the SMSC LAN It's interrupts-extended. Documentation-wise both are always supported, so we just document 'interrupts' unless interrupts-extended is only ever valid which would not be the case here. > + interrupt line as cell 0, cell 1 is an OPTIONAL PME (power > + management event) interrupt that is able to wake up the host > + system with a 50ms pulse on network activity > + For generic bindings for interrupt controller parents, refer to > + interrupt-controller/interrupts.txt > - phy-mode : See ethernet.txt file in the same directory -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
