On Tue, May 1, 2018 at 8:16 AM Rob Herring <robh@xxxxxxxxxx> wrote:
...
> You don't need both properties. If the ethernet driver needs the phy,
> then it can decend into the child nodes to find it.
Ah, in the scenario I hit, the phy was on a separate mdio bus. So the
phy-handle was necessary. Is it common behavior for an Ethernet
controller to attach to the first phy on its own mdio bus? That wasn't
clear to me looking at the documentation, and is where I messed up
and attached the Ethernet to the gmiitorgmii phy.
I could refactor the example to more closely resemble my scenario, e.g.
ethernet0 {
mdio {
phy: ethernet-phy@0 {
...
}
gmiitorgmii@8 {
...
}
}
}
ethernet1 {
phy-handle = <&phy>;
}
But that would make the example too specific. So I'm inclined
to resubmit with just the added description, and drop the example changes.
--
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
