From: Andrew Lunn <andrew@lunn.ch>
To: YUAN Linyu <Linyu.Yuan@alcatel-sbell.com.cn>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"cugyly@163.com" <cugyly@163.com>
Subject: Re: create drivers/net/mdio and move mdio drivers into it
Date: Thu, 23 Feb 2017 11:29:49 +0100 [thread overview]
Message-ID: <20170223102949.GB14312@lunn.ch> (raw)
In-Reply-To: <8729016553E3654398EA69218DA29EEF15A81F13@cnshjmbx02>
On Thu, Feb 23, 2017 at 09:51:17AM +0000, YUAN Linyu wrote:
>
>
> > -----Original Message-----
> > From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.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@vger.kernel.org; cugyly@163.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
prev parent reply other threads:[~2017-02-23 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 0:20 create drivers/net/mdio and move mdio drivers into it YUAN Linyu
2017-02-20 5:03 ` Florian Fainelli
2017-02-20 5:23 ` YUAN Linyu
2017-02-20 5:42 ` Florian Fainelli
2017-02-20 6:10 ` YUAN Linyu
2017-02-20 6:15 ` Florian Fainelli
2017-02-20 6:26 ` YUAN Linyu
2017-02-20 22:30 ` Florian Fainelli
2017-02-20 6:29 ` YUAN Linyu
2017-02-20 22:31 ` Florian Fainelli
2017-02-21 0:47 ` YUAN Linyu
2017-02-22 5:38 ` YUAN Linyu
2017-02-22 10:21 ` Andrew Lunn
2017-02-23 0:10 ` YUAN Linyu
2017-02-23 9:30 ` Andrew Lunn
2017-02-23 9:51 ` YUAN Linyu
2017-02-23 10:29 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170223102949.GB14312@lunn.ch \
--to=andrew@lunn.ch \
--cc=Linyu.Yuan@alcatel-sbell.com.cn \
--cc=cugyly@163.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).