linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Kim Phillips'" <kim.phillips@freescale.com>, <linuxppc-dev@ozlabs.org>
Subject: RE: [PATCH 1/4] powerpc: document max-speed and interface-type properties
Date: Wed, 11 Apr 2007 23:45:36 +0200	[thread overview]
Message-ID: <006a01c77c82$bd304b40$6667a8c0@Jocke> (raw)
In-Reply-To: <20070410165639.1b619c34.kim.phillips@freescale.com>

> -----Original Message-----
> From: 
> linuxppc-dev-bounces+joakim.tjernlund=transmode.se@ozlabs.org 
> [mailto:linuxppc-dev-bounces+joakim.tjernlund=transmode.se@ozl
> abs.org] On Behalf Of Kim Phillips
> Sent: den 10 april 2007 23:57
> To: linuxppc-dev@ozlabs.org
> Subject: [PATCH 1/4] powerpc: document max-speed and 
> interface-type properties
> 
> Since ucc_geth is being migrated to use the phylib, the existing
> (undocumented) 'interface' property is being deprecated in favour
> of unconjoined variations 'max-speed' and 'interface-type'.
> 
> max-speed is necessary for QE UEC devices that do not make that
> information available through their programming model.
> 
> interface-type is now maintained one-to-one with definitions
> in include/linux/phy.h.
> 
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> ---
> please consider for 2.6.22
> 
>  Documentation/powerpc/booting-without-of.txt |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/powerpc/booting-without-of.txt 
> b/Documentation/powerpc/booting-without-of.txt
> index 88cdb59..92fa74c 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -1556,6 +1556,9 @@ platforms are moved over to use the 
> flattened-device-tree model.
>     Required properties for network device_type:
>     - mac-address : list of bytes representing the ethernet address.
>     - phy-handle : The phandle for the PHY connected to this 
> controller.
> +   - max-speed : The maximum speed supported by the 
> controller (in Mbit/s)
> +   - interface-type : a string naming the controller/PHY 
> interface type,
> +     i.e., one of "mii", "gmii", "sgmii", "tbi", "rmii", 
> "rgmii", or "rtbi".

Hmm, what if I have a direct MII to MII connection without a PHY in between?
Will this support such a "fixed" connection?
How do I express that in OF speak?

 Jocke

  parent reply	other threads:[~2007-04-11 21:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 21:56 [PATCH 1/4] powerpc: document max-speed and interface-type properties Kim Phillips
2007-04-10 22:48 ` Olof Johansson
2007-04-10 23:19   ` Kim Phillips
2007-04-11  1:49     ` Olof Johansson
2007-04-11 18:09       ` Kim Phillips
2007-04-11 18:32         ` Olof Johansson
2007-04-11 21:45 ` Joakim Tjernlund [this message]
2007-04-11 22:56   ` Kim Phillips
2007-04-12  6:49     ` Joakim Tjernlund
2007-04-12  7:06 ` Segher Boessenkool
2007-04-16 17:28   ` Andy Fleming
2007-04-16 18:19     ` Kumar Gala

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='006a01c77c82$bd304b40$6667a8c0@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=kim.phillips@freescale.com \
    --cc=linuxppc-dev@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).