[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170120000645.GA31483@lunn.ch>
Date: Fri, 20 Jan 2017 01:06:45 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Cc: Gregory CLEMENT <gregory.clement@...e-electrons.com>,
Florian Fainelli <f.fainelli@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Jason Cooper <jason@...edaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org,
Nadav Haklai <nadavh@...vell.com>,
Wilson Ding <dingwei@...vell.com>,
Kostya Porotchkin <kostap@...vell.com>,
Joe Zhou <shjzhou@...vell.com>,
Jon Pannell <jpannell@...vell.com>
Subject: Re: [PATCH v5 1/2] net: dsa: mv88e6xxx: Don't forbid MDIO I/Os for
PHY addr >= num_of_ports
On Thu, Jan 19, 2017 at 05:13:12PM -0500, Vivien Didelot wrote:
> Hi Gregory,
>
> Gregory CLEMENT <gregory.clement@...e-electrons.com> writes:
>
> > From: Romain Perier <romain.perier@...e-electrons.com>
> >
> > Some Marvell ethernet switches have internal ethernet transceivers with
> > hardcoded phy addresses. These addresses can be greater than the number
> > of ports or its value might be different than the associated port number.
> > This is for example the case for MV88E6341 that has 6 ports and internal
> > Port 1 to Port4 PHYs mapped at SMI addresses from 0x11 to 0x14.
>
> Isn't there an hardware table used to map the PHY addresses on such chip?
The 6390 has something like this. But if we can avoid it, lets keep it
KISS.
Andrew
Powered by blists - more mailing lists