From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [RFC fs_enet: Convert MII bitbang driver to use GPIO lib
Date: Tue, 22 Apr 2008 17:21:49 +0200 [thread overview]
Message-ID: <200804221721.51461.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <20080422150844.GA15474@ld0162-tx32.am.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
On Tuesday 22 April 2008 17:08, Scott Wood wrote:
> On Tue, Apr 22, 2008 at 10:55:06AM +0200, Laurent Pinchart wrote:
> > On Monday 21 April 2008 19:56, Scott Wood wrote:
> > > The memory-constrained platform I had in mind was 8xx, which doesn't use
> > > bitbanged MDIO. It might nice to keep the gpiolib bit separate to avoid
> > > situations such as ep8248e where mdiobb would be the only thing
> > > requiring a gpiolib binding, though -- but it shouldn't be two separate
> > > bitbang drivers, just the existing bitbang driver plus some glue code
> > > that binds it to gpiolib.
> >
> > I would be fine with that if the glue code wasn't 90% of the whole driver.
> > There is really little (not to say nothing) that can be shared between the
> > two drivers.
>
> I think we're thinking of a different pair of drivers... I thought you
> were talking about duplicating drivers/net/phy/mdio-bitbang.c, not
> drivers/net/fs_enet/mii-bitbang.c.
I don't plan to touch drivers/net/phy/mdio-bitbang.c at all, it does its job
well enough.
As the openfirmware + gpio + mdio driver might benefit non-powerpc platforms,
I plan to create a new driver (probably drivers/net/phy/mdio-ofgpio.c) that
mostly ports drivers/net/fs_enet/mii-bitbang.c to the gpiolib (this replaces
around 90% of the code).
If both drivers/net/fs_enet/mii-bitbang.c and drivers/net/phy/mdio-ofgpio.c
must live together, I'll have a problem in
drivers/net/fs_enet/fs_enet-main.c. The net device probing code searches the
device tree for an associated PHY, and creates a PHY id from the PHY node. As
the id will be generated from different bus ids in the two mdio drivers (the
bus number is the register address for drivers/net/fs_enet/mii-bitbang.c, and
is the gpio index for drivers/net/phy/mdio-ofgpio.c), things will break.
Any idea regarding how to get rid of that fs_enet/mii-bitbang hardcoded
dependency ?
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-22 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 14:40 [RFC fs_enet: Convert MII bitbang driver to use GPIO lib Laurent Pinchart
2008-04-16 16:05 ` Anton Vorontsov
2008-04-16 16:09 ` Laurent Pinchart
2008-04-18 11:34 ` Laurent Pinchart
2008-04-21 17:56 ` Scott Wood
2008-04-22 8:55 ` Laurent Pinchart
2008-04-22 15:08 ` Scott Wood
2008-04-22 15:21 ` Laurent Pinchart [this message]
2008-04-22 15:36 ` Anton Vorontsov
2008-04-22 15:36 ` Scott Wood
2008-04-22 15:55 ` Laurent Pinchart
2008-04-22 16:04 ` Scott Wood
2008-04-20 22:42 ` Grant Likely
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=200804221721.51461.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=scottwood@freescale.com \
/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).