On Mon, Dec 10, 2007 at 02:18:16PM -0700, Dale Farnsworth wrote:
> David Gibson wrote:
> > On Thu, Nov 29, 2007 at 06:28:36PM +0300, Andrei Dolnikov wrote:
> > > Device tree source file for the Emerson Katana Qp board
>
> [snip]
>
> > > + [EMAIL PROTECTED] { /* Marvell Discovery */
> > > + #address-cells = <1>;
> > > + #size-cells = <1>;
> > > + model = "mv64460"; /* Default */
> > > + compatible = "marvell,mv64x60";
>
> [snip]
>
> > > + mdio {
> >
> > There must be some way of actuall accessing the mdio bus, so this node
> > ought to have a 'reg' property and unit address.
>
> There is no way for the cpu to directly access the mdio bus. The
> mdio bus is internally accessed by the ethernet MAC. That being the
> case, maybe it makes more sense to move the mdio node inside of the
> multiethernet node, as follows, but I don't see how we can give it
> a reg property or a unit address.
Ah, I see. If the mdio interface isn't distinct from the other
pieces, then it probably shouldn't get a device node at all. Having
an explicit mdio bus with the phys hanging off it is convenient for
hardware which actually works that way, but it doesn't have to be done
like that.
Of course, then the question is where to hang the phy nodes, which
look like they have information you need. Since you already have a
local addressing scheme for the MACs under the multiethernet, what
probably makes sense would be to hang the phys directly under the
multiethernet, using an encoding scheme for the reg properties so that
the MACs and PHYs aren't confused (say, MACs are 0x0, 0x1, 0x2, PHYs
are 0x80000000, 0x80000001, 0x80000002).
Incidentally, although I suggested it, I'm not all that fond of the
"multiethernet" name, it was just the first thing that occurred to me.
>
> [EMAIL PROTECTED] {
> reg = <0x2000 0x2000>;
> [EMAIL PROTECTED] {
> device_type = "network";
> compatible = "marvell,mv64360-eth";
> reg = <0>;
> interrupts = <32>;
> interrupt-parent = <&PIC>;
> phy = <&PHY0>;
> local-mac-address = [ 00 00 00 00 00 00 ];
> };
> [EMAIL PROTECTED] {
> device_type = "network";
> compatible = "marvell,mv64360-eth";
> reg = <1>;
> interrupts = <33>;
> interrupt-parent = <&PIC>;
> phy = <&PHY1>;
> local-mac-address = [ 00 00 00 00 00 00 ];
> };
> mdio {
> #address-cells = <1>;
> #size-cells = <0>;
> device_type = "mdio";
> compatible = "marvell,mv64360-mdio";
> PHY0: [EMAIL PROTECTED] {
> device_type = "ethernet-phy";
> compatible = "broadcom,bcm5421";
> interrupts = <76>; /* GPP 12 */
> interrupt-parent = <&PIC>;
> reg = <1>;
> };
> PHY1: [EMAIL PROTECTED] {
> device_type = "ethernet-phy";
> compatible = "broadcom,bcm5421";
> interrupts = <76>; /* GPP 12 */
> interrupt-parent = <&PIC>;
> reg = <3>;
> };
> };
> };
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
