On Fri, Mar 23, 2018 at 09:11:13PM +0100, Alexandre Belloni wrote: > DT bindings for the Ethernet switch found on Microsemi Ocelot platforms. > > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Signed-off-by: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx> > --- > .../devicetree/bindings/net/mscc-ocelot.txt | 62 ++++++++++++++++++++++ > 1 file changed, 62 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/mscc-ocelot.txt > > diff --git a/Documentation/devicetree/bindings/net/mscc-ocelot.txt b/Documentation/devicetree/bindings/net/mscc-ocelot.txt > new file mode 100644 > index 000000000000..ee092a85b5a0 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/mscc-ocelot.txt > @@ -0,0 +1,62 @@ > +Microsemi Ocelot network Switch > +=============================== > + > +The Microsemi Ocelot network switch can be found on Microsemi SoCs (VSC7513, > +VSC7514) > + > +Required properties: > +- compatible: Should be "mscc,ocelot-switch" > +- reg: Must contain an (offset, length) pair of the register set for each > + entry in reg-names. > +- reg-names: Must include the following entries: > + - "sys" > + - "rew" > + - "qs" > + - "hsio" > + - "qsys" > + - "ana" > + - "portX" with X from 0 to the number of last port index available on that > + switch > +- interrupts: Should contain the switch interrupts for frame extraction and > + frame injection > +- interrupt-names: should contain the interrupt names: "xtr", "inj" > + > +Example: > + > + switch@1010000 { > + #address-cells = <1>; > + #size-cells = <0>; > + compatible = "mscc,ocelot-switch"; > + reg = <0x1010000 0x10000>, > + <0x1030000 0x10000>, > + <0x1080000 0x100>, > + <0x10d0000 0x10000>, > + <0x11e0000 0x100>, > + <0x11f0000 0x100>, > + <0x1200000 0x100>, > + <0x1210000 0x100>, > + <0x1220000 0x100>, > + <0x1230000 0x100>, > + <0x1240000 0x100>, > + <0x1250000 0x100>, > + <0x1260000 0x100>, > + <0x1270000 0x100>, > + <0x1280000 0x100>, > + <0x1800000 0x80000>, > + <0x1880000 0x10000>; > + reg-names = "sys", "rew", "qs", "hsio", "port0", > + "port1", "port2", "port3", "port4", "port5", > + "port6", "port7", "port8", "port9", "port10", > + "qsys", "ana"; > + interrupts = <21 22>; > + interrupt-names = "xtr", "inj"; > + > + port0: port@0 { > + reg = <0>; > + phy-handle = <&phy0>; > + }; > + port1: port@1 { > + reg = <1>; > + phy-handle = <&phy1>; > + }; Hi Alexandre Is there anything else in the switch which in the future might need child nodes? At the moment, you can do for_each_available_child_of_node() and walk the ports. But if you do need to add some other sorts of children in the future it gets messy. With DSA, we have a ports {} container. Andrew -- 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