linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/4 v4] powerpc: document phy-connection-type property
Date: Mon, 23 Apr 2007 16:06:21 -0500	[thread overview]
Message-ID: <20070423160621.329d1a08.kim.phillips@freescale.com> (raw)
In-Reply-To: <5c96dd623e3a6737db48ab17c3550610@kernel.crashing.org>

On Mon, 23 Apr 2007 22:59:43 +0200
Segher Boessenkool <segher@kernel.crashing.org> wrote:

> > phy-connection-type is now maintained one-to-one with definitions
> > in include/linux/phy.h, albeit in the form of a string.
> 
> That's sort-of accidental though :-)
> 
sure..

> > --- a/Documentation/powerpc/booting-without-of.txt
> > +++ b/Documentation/powerpc/booting-without-of.txt
> > @@ -1562,6 +1562,9 @@ platforms are moved over to use the 
> > flattened-device-tree model.
> >       network device.  This is used by the bootwrapper to interpret
> >       MAC addresses passed by the firmware when no information other
> >       than indices is available to associate an address with a device.
> > +   - phy-connection-type : a string naming the controller/PHY 
> > interface type,
> > +     i.e., "mii" (default), "rmii", "gmii", "rgmii", "rgmii-id", 
> > "tbi",
> > +     or "rtbi".
> 
> Could you put this right after the "phy-handle" definition
> please?

phy-handle is a required property, whereas phy-connection-type is not
(it's recommended). Are you suggesting phy-connection-type be a required
property?

> 
> > @@ -1573,6 +1576,7 @@ platforms are moved over to use the 
> > flattened-device-tree model.
> >  		interrupts = <a0 0>;
> >  		interrupt-parent = <700>;
> >  		mac-address = [ 00 04 9f 00 23 23 ];
> > +		phy-connection-type = "gmii";
> >  		rx-clock = "none";
> >  		tx-clock = "clk9";
> >  		phy-handle = <212000>;
> 
> Same here.  It's nice to keep things grouped, it
> improves understanding ;-)

That's understandable.  Lemme know about the above though.

Kim

  reply	other threads:[~2007-04-23 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 19:40 [PATCH 1/4 v4] powerpc: document phy-connection-type property Kim Phillips
2007-04-23 20:59 ` Segher Boessenkool
2007-04-23 21:06   ` Kim Phillips [this message]
2007-04-23 21:16     ` Segher Boessenkool
2007-05-14  1:20     ` Matt Sealey
2007-05-14 12:44       ` Segher Boessenkool
2007-04-23 21:19   ` Segher Boessenkool

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=20070423160621.329d1a08.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).