[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170223102949.GB14312@lunn.ch>
Date: Thu, 23 Feb 2017 11:29:49 +0100
From: Andrew Lunn <andrew@...n.ch>
To: YUAN Linyu <Linyu.Yuan@...atel-sbell.com.cn>
Cc: Florian Fainelli <f.fainelli@...il.com>,
"David S . Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"cugyly@....com" <cugyly@....com>
Subject: Re: create drivers/net/mdio and move mdio drivers into it
On Thu, Feb 23, 2017 at 09:51:17AM +0000, YUAN Linyu wrote:
>
>
> > -----Original Message-----
> > From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> > On Behalf Of Andrew Lunn
> > Sent: Thursday, February 23, 2017 5:30 PM
> > To: YUAN Linyu
> > Cc: Florian Fainelli; David S . Miller; netdev@...r.kernel.org; cugyly@....com
> > Subject: Re: create drivers/net/mdio and move mdio drivers into it
> >
> > > Big picture is we can remove struct mii_bus,
> >
> > So if you remove this, how do you represent MII as a bus? It is a bus,
> > clause 22 allows up to 32 devices on it, and i have boards with more
> > than 8 devices on the bus. Clause 44 allows many more devices on the
> > bus.
> >
> add a phy device list to mdio_device.
Hi Yuan
And where do you put the bus name? The bus operations? The mutex for
accessing devices on the bus? The bus is a device, so you need a
device structure somewhere, to make it part of the device
hierarchy. Where do you put that?
I think it is time to stop this discussion, and you need to submit
patches we can review, how you think this would work. That will make
you look at the details.
Andrew
Powered by blists - more mailing lists