From: Kim Phillips <kim.phillips@freescale.com>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties
Date: Fri, 13 Apr 2007 01:25:42 -0500 [thread overview]
Message-ID: <20070413012542.343eb848.kim.phillips@freescale.com> (raw)
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'.
interface-type is now maintained one-to-one with definitions
in include/linux/phy.h. If not specified, "mii" is assumed.
max-speed is available for users to override the interface-derived
speed, e.g. rgmii at 100Mbit/s.
Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
---
moved to recommended section (from required), removed sgmii, added rgmii-id.
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..cb8c6fb 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -1562,6 +1562,10 @@ 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.
+ - interface-type : a string naming the controller/PHY interface type,
+ i.e., "mii" (default), "rmii", "gmii", "rgmii", "rgmii-id", "tbi", or "rtbi".
+ - max-speed : The maximum speed supported by the controller (in Mbit/s)
+ this is used if the user wants to override the interface-derived speed.
Example:
ucc@2000 {
@@ -1573,6 +1577,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 ];
+ interface-type = "rgmii";
rx-clock = "none";
tx-clock = "clk9";
phy-handle = <212000>;
--
1.5.0.1
next reply other threads:[~2007-04-13 6:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 6:25 Kim Phillips [this message]
2007-04-13 17:00 ` [PATCH 1/4 v2] powerpc: document max-speed and interface-type properties Kumar Gala
2007-04-13 17:36 ` Kim Phillips
2007-04-13 17:42 ` Kumar Gala
2007-04-13 17:52 ` Kim Phillips
2007-04-13 17:59 ` Kumar Gala
2007-04-13 19:02 ` Segher Boessenkool
2007-04-16 15:25 ` Kim Phillips
2007-04-16 15:34 ` Kumar Gala
2007-04-16 15:47 ` Segher Boessenkool
2007-04-16 16:57 ` Kim Phillips
2007-04-16 23:18 ` Segher Boessenkool
2007-04-17 0:31 ` Kim Phillips
2007-04-17 10:25 ` Segher Boessenkool
2007-04-17 20:27 ` Kim Phillips
2007-04-17 23:18 ` Segher Boessenkool
2007-04-18 1:13 ` Kim Phillips
2007-04-18 10:34 ` Segher Boessenkool
2007-04-18 21:48 ` Kim Phillips
2007-04-20 8:34 ` Segher Boessenkool
2007-04-20 19:13 ` Andy Fleming
2007-04-21 17:22 ` Segher Boessenkool
2007-04-23 16:58 ` Andy Fleming
2007-04-23 21:24 ` Segher Boessenkool
2007-04-16 18:40 ` Andy Fleming
2007-04-16 23:25 ` Segher Boessenkool
2007-04-17 7:04 ` Andy Fleming
2007-04-17 10:40 ` 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=20070413012542.343eb848.kim.phillips@freescale.com \
--to=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).