On Saturday 21 December 2013, Iyappan Subramanian wrote: > @@ -0,0 +1,67 @@ > +APM X-Gene SoC Ethernet nodes > + > +Ethernet nodes are defined to describe on-chip ethernet interfaces in > +APM X-Gene SoC. Ethernet subsystem communicates with a central Queue Manager > +(QMTM) using messages for transmit, receive and allocating data buffers. > +There are multiple ethernet interfaces in APM X-Gene SoC. Each ethernet > +interface has its own node. Its corresponding clock nodes are shown below. > + > +Required properties: > +- compatible : Shall be "apm,xgene-enet" > +- reg : First memory resource shall be the Ethernet CSR > + memory resource for indirect MAC access. > + Second memory resource shall be the Ethernet CSR > + memory resource. > + Third memory resource shall be the Ethernet CSR > + memory resource for indirect MII access. What is a "CSR"? > +- interrupts : First interrupt resource shall be the Ethernet global > + Error interrupt. > + : Second interrupt resource shall be the Ethernet MAC > + Error interrupt. > + : Third interrupt resource shall be the Ethernet QM > + interface interrupt. No regular interrupts? > +- clocks : Reference to the clock entry. > +- local-mac-address : Shall be ethernet mac address. > +- max-frame-size : Shall be maximum ethernet frame size. > +- devid : Shall be ethernet interface number. > +- phyid : Shall be ethernet MII phy address. > +- phy-mode : Shall be ethernet MII mode. Can you explain what the interface number is for? Is the phy actually part of the ethernet device? Since it has its own register range, it seems likely that it's actually a separate device that just happens to be used together with the mac and should have its own device node and driver. Arnd -- 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
