From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property
Date: Tue, 27 Nov 2007 14:39:35 +0300 [thread overview]
Message-ID: <20071127113935.GA26867@localhost.localdomain> (raw)
In-Reply-To: <1196089448.12625.62.camel@gentoo-jocke.transmode.se>
On Mon, Nov 26, 2007 at 04:04:08PM +0100, Joakim Tjernlund wrote:
> On Mon, 2007-11-26 at 17:29 +0300, Vitaly Bordug wrote:
> > fixed-link says: register new "Fixed/emulated PHY", i.e. PHY that
> > not connected to the real MDIO bus.
> >
> > Signed-off-by: Vitaly Bordug <vitb@kernel.crashing.org>
> > Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> >
> > ---
> >
> > Documentation/powerpc/booting-without-of.txt | 3 +
> > arch/powerpc/sysdev/fsl_soc.c | 56 ++++++++++++++++++--------
> > 2 files changed, 42 insertions(+), 17 deletions(-)
> >
> >
> > diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> > index e9a3cb1..cf25070 100644
> > --- a/Documentation/powerpc/booting-without-of.txt
> > +++ b/Documentation/powerpc/booting-without-of.txt
> > @@ -1254,6 +1254,9 @@ platforms are moved over to use the flattened-device-tree model.
> > services interrupts for this device.
> > - phy-handle : The phandle for the PHY connected to this ethernet
> > controller.
> > + - fixed-link : <a b c> where a is emulated phy id - choose any,
> > + but unique to the all specified fixed-links, b is duplex - 0 half,
> > + 1 full, c is link speed - d#10/d#100/d#1000.
>
> Good work!
> May I suggest adding a "d" to <a b c> where d is flow control - 0 no, 1 yes
Well, I see no reference of the "flow" neither in the include/linux/mii.h
nor in the drivers/net/phy/*. :-/ Thus today there is no such register
bit we can emulate?..
> flow control or not just popped up here today so I got a use for it.
..and I looked into few drivers (gianfar, ucc), and they seem to use
hard-coded flow control values, thus they don't speak to the PHYs
about that.
Can you give any reference to the driver that needs that parameter?
Does it use PHY subsystem to obtain flow-control on/off information?
Thanks,
--
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2007-11-27 11:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 14:29 [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Vitaly Bordug
2007-11-26 14:29 ` [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property Vitaly Bordug
2007-11-26 15:04 ` Joakim Tjernlund
2007-11-27 11:39 ` Anton Vorontsov [this message]
2007-11-27 13:17 ` Joakim Tjernlund
2007-11-27 13:59 ` Anton Vorontsov
2007-11-27 14:01 ` Joakim Tjernlund
2007-11-26 14:29 ` [PATCH 3/3] [POWERPC] MPC8349E-mITX: Vitesse 7385 PHY is not connected to the MDIO bus Vitaly Bordug
2007-12-01 13:48 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Jochen Friedrich
2007-12-01 19:07 ` Vitaly Bordug
2007-12-01 21:34 ` Anton Vorontsov
2007-12-01 22:22 ` Vitaly Bordug
2007-12-01 23:27 ` Stephen Rothwell
2007-12-02 11:54 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHYlayer functionality Joakim Tjernlund
2007-12-02 12:13 ` Anton Vorontsov
2007-12-01 21:59 ` [PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality Jeff Garzik
2007-12-01 22:16 ` Vitaly Bordug
2007-12-04 20:07 ` Jeff Garzik
2007-12-05 1:22 ` Vitaly Bordug
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 22:51 Vitaly Bordug
2007-12-06 22:51 ` [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property Vitaly Bordug
2008-01-18 6:46 ` 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=20071127113935.GA26867@localhost.localdomain \
--to=avorontsov@ru.mvista.com \
--cc=jeff@garzik.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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).