On Mon, Jul 20, 2015 at 03:30:36PM +0200, Michal Simek wrote:
> Hi Nicolas,
>
> have you had a time to look at this?
>
> Thanks,
> Michal
>
> On 07/13/2015 06:48 AM, Punnaiah Choudary Kalluri wrote:
> > This patch is to add support for the design that has multiple ethernet
> > mac controllers and single mdio bus connected to multiple phy devices.
> > i.e mdio lines are connected to any of the ethernet mac controller and
> > all the phy devices will be accessed using the phy maintenance interface
> > in that mac controller.
> >
> > ______ _____
> > | | |PHY0 |
> > | MAC0 |-----------------| |
> > |______| | |_____|
> > |
> > ______ | _____
> > | | | | |
> > | MAC1 | |_________|PHY1 |
> > |______| |____ |
> >
> > So, i come up with two implementations for addressing the above
> > configuration.
> >
> > Implementation 1:
> > Have separate driver for mdio bus
> > Create a DT node for all the PHY devices connected to the mdio bus
> > This driver will share the register space of the mac controller that has
> > mdio bus connected.
> >
Hi Michal
The above it what Marvell, Freescale FEC and probably others do. It is
well defined in Documentation/devicetree/bindings/net/ethernet.txt
that you can have a phy-handle property containing a phandle to the
actual phy device on some random MDIO bus.
Andrew
--
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
