On Fri, Sep 11, 2015 at 09:12:17AM +0200, Geert Uytterhoeven wrote: > Hi Simon, > > On Fri, Sep 11, 2015 at 4:01 AM, Simon Horman > <horms+rene...@verge.net.au> wrote: > > --- a/Documentation/devicetree/bindings/net/renesas,ravb.txt > > +++ b/Documentation/devicetree/bindings/net/renesas,ravb.txt > > @@ -6,8 +6,11 @@ interface contains. > > Required properties: > > - compatible: "renesas,etheravb-r8a7790" if the device is a part of > > R8A7790 SoC. > > "renesas,etheravb-r8a7794" if the device is a part of R8A7794 > > SoC. > > + "renesas,etheravb-r8a7795" if the device is a part of R8A7795 > > SoC. > > - reg: offset and length of (1) the register block and (2) the stream > > buffer. > > -- interrupts: interrupt specifier for the sole interrupt. > > +- interrupts: interrupt specifiers. > > + One for each entry in interrupt-names the R8A7795 SoC; > > ... for the R8A7795 SoC > > > + One entry for a multiplexed interrupt otherwise. > > - phy-mode: see ethernet.txt file in the same directory. > > - phy-handle: see ethernet.txt file in the same directory. > > - #address-cells: number of address cells for the MDIO bus, must be equal > > to 1. > > @@ -18,6 +21,9 @@ Required properties: > > Optional properties: > > - interrupt-parent: the phandle for the interrupt controller that services > > interrupts for this device. > > +- interrupt-names: One entry per interrupt named "ch%u". > > + For the R8A7795 SoC this property is mandatory, > > + and "ch0" through "ch24" are mandatory. > > This suggests the single multiplexed interrupt on R-Car Gen2 can be called > "ch0". Is that what you want? I know the driver doesn't care.
No, its not what I intended. I think its reasonable to allow the multiplexed interrupt to be named, but to what I wonder. The documentation seems to call the interrupt "EthernetAVB", which isn't very exciting. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
