[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140325123739.05017fcf@marrow.netinsight.se>
Date: Tue, 25 Mar 2014 12:37:39 +0100
From: Simon Kågström <simon.kagstrom@...insight.net>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Krzysztof Halasa <khc@...waw.pl>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Arnd Bergmann <arnd@...db.de>, netdev <netdev@...r.kernel.org>,
"arm@...nel.org" <arm@...nel.org>,
David Miller <davem@...emloft.net>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH RFC] ixp4xx_eth: Allow setting the MDIO bus name in
platform data
On Mon, 24 Mar 2014 13:42:29 -0700
Florian Fainelli <f.fainelli@...il.com> wrote:
> 2014-03-24 13:34 GMT-07:00 Krzysztof Halasa <khc@...waw.pl>:
> > Simon Kågström <simon.kagstrom@...insight.net> writes:
> >
> >> Allows using e.g., a fixed MDIO bus with the ixp4xx_eth driver.
> >> Example:
> >
> >
> > Why do we need it? I'm not sure I know what constitutes a "fixed MDIO
> > bus".
>
> This is a software emulation MDIO bus for when your Ethernet MAC is
> connected to a PHY which does not appear on the MDIO bus. This is
> typically used to provide the Ethernet driver with a link that is
> always seen as UP, when you cannot directly query it via MDIO/MDC.
Yes, exactly. We have a board which uses two of the ipx4xx NPE:s, one
which uses a real PHY via the ixp4xx_eth MDIO bus and one which uses
the fixed PHY driver.
To support this, we need this patch as the driver would otherwise
always look for the PHY on the ixp4xx_eth MDIO bus.
// Simon
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists