From: Nathaniel Case <ncase@xes-inc.com>
To: Olof Johansson <olof@lixom.net>
Cc: netdev@vger.kernel.org, pasemi-linux@ozlabs.org, afleming@freescale.com
Subject: Re: [Pasemi-linux] I2C MDIO support for pasemi_mac driver
Date: Fri, 07 Mar 2008 13:28:11 -0600 [thread overview]
Message-ID: <1204918091.8864.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20080307184854.GA23402@lixom.net>
On Fri, 2008-03-07 at 12:48 -0600, Olof Johansson wrote:
> On second thought, it might be a better idea to change from BUS:ID to
> BUSTYPE:BUS:ID in phylib, to separate the namespaces.
>
> That, plus a way to get to an i2c bus number from a device tree node,
> and we should be all set. That might be tricker though.
I like this idea, since it would eliminate the need for the MAC driver
to decide policy on a "global" MDIO bus numbering scheme. I was also
trying to make it compatible with the case (however unlikely) of having
both an SMBus PHY and a bit-banged MDIO PHY.
For getting the I2C bus number from a device tree node, I've just been
parsing the node->full_name for the number following the i2c@XXXXXX with
an ugly string parsing function (xes_of_get_node_loc() in one of the
older patches I sent you).
- Nate Case <ncase@xes-inc.com>
next prev parent reply other threads:[~2008-03-07 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1204911643.8864.15.camel@localhost.localdomain>
2008-03-07 18:37 ` I2C MDIO support for pasemi_mac driver Olof Johansson
2008-03-07 18:48 ` [Pasemi-linux] " Olof Johansson
2008-03-07 19:28 ` Nathaniel Case [this message]
2008-03-13 21:57 ` Nate Case
2008-04-02 22:45 ` Andy Fleming
2008-04-03 13:45 ` Nate Case
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=1204918091.8864.36.camel@localhost.localdomain \
--to=ncase@xes-inc.com \
--cc=afleming@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pasemi-linux@ozlabs.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).