[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170824171301.GH28443@kwain>
Date: Thu, 24 Aug 2017 19:13:01 +0200
From: Antoine Tenart <antoine.tenart@...e-electrons.com>
To: Russell King - ARM Linux <linux@...linux.org.uk>
Cc: Andrew Lunn <andrew@...n.ch>,
Antoine Tenart <antoine.tenart@...e-electrons.com>,
davem@...emloft.net, kishon@...com, jason@...edaemon.net,
sebastian.hesselbarth@...il.com,
gregory.clement@...e-electrons.com,
thomas.petazzoni@...e-electrons.com, nadavh@...vell.com,
linux-kernel@...r.kernel.org, mw@...ihalf.com, stefanc@...vell.com,
miquel.raynal@...e-electrons.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 09/13] net: mvpp2: dynamic reconfiguration of
the PHY mode
On Thu, Aug 24, 2017 at 06:04:01PM +0100, Russell King - ARM Linux wrote:
> On Thu, Aug 24, 2017 at 06:57:43PM +0200, Andrew Lunn wrote:
> > > I see what could be the issue but I do not understand one aspect though:
> > > how could we switch from one PHY to another, as there's only one output
> > > between the SoC (and so a given GoP#) and the board. So if a given PHY
> > > can handle multiple modes I see, but in the other case a muxing
> > > somewhere would be needed? Or did I miss something?
> >
> > I think we need a hardware diagram...
> >
> > How are the RJ45, copper PHY, SFP module connected to the SoC?
> >
> > Somewhere there must be a mux, to select between copper and
> > fibre. Where is that mux?
>
> In the 88x3310 PHY:
>
> .------- RJ45
> MVPP2 ----- 88x3310 PHY
> `------- SFP+
And the "MVPP2" part can be expended to:
.-- GoP #0 --.
MVPP2 ----- GoP #1 ---- Comphy lane #X -- 88x3310
`-- GoP #2 --'
Thanks!
Antoine
--
Antoine Ténart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists