From: Scott Wood <oss@buserror.net>
To: Valentin Longchamp <valentin@longchamp.me>,
linuxppc-dev@lists.ozlabs.org, galak@kernel.crashing.org
Cc: Madalin Bucur <madalin.bucur@nxp.com>
Subject: Re: [PATCH] powerpc/kmcent2: update the ethernet devices' phy properties
Date: Sun, 28 Jul 2019 14:26:34 -0500 [thread overview]
Message-ID: <2243421e574c72c5e75d27cc0122338e2e0bde63.camel@buserror.net> (raw)
In-Reply-To: <CADYrJDwvwVThmOwHZ4Moqenf=-iqoHC+yJ_uxtrD8sDso33rjg@mail.gmail.com>
On Sun, 2019-07-28 at 18:01 +0200, Valentin Longchamp wrote:
> Hi Scott, Kumar,
>
> Looking at this patch I have realised that I had already submitted it
> to the mailing list nearly 2 years ago:
> https://patchwork.ozlabs.org/patch/842944/
>
> Could you please make sure that this one gets merged in the next
> window, so that I avoid forgetting such a patch a 2nd time ?
>
> Thanks a lot
I added it to my patchwork todo list; thanks for the reminder.
> Le dim. 14 juil. 2019 à 22:05, Valentin Longchamp
> <valentin@longchamp.me> a écrit :
> >
> > Change all phy-connection-type properties to phy-mode that are better
> > supported by the fman driver.
> >
> > Use the more readable fixed-link node for the 2 sgmii links.
> >
> > Change the RGMII link to rgmii-id as the clock delays are added by the
> > phy.
> >
> > Signed-off-by: Valentin Longchamp <valentin@longchamp.me>
I don't see any other uses of phy-mode in arch/powerpc/boot/dts/fsl, and I see
lots of phy-connection-type with fman. Madalin, does this patch look OK?
-Scott
> > ---
> > arch/powerpc/boot/dts/fsl/kmcent2.dts | 16 +++++++++++-----
> > 1 file changed, 11 insertions(+), 5 deletions(-)
> >
> > diff --git a/arch/powerpc/boot/dts/fsl/kmcent2.dts
> > b/arch/powerpc/boot/dts/fsl/kmcent2.dts
> > index 48b7f9797124..c3e0741cafb1 100644
> > --- a/arch/powerpc/boot/dts/fsl/kmcent2.dts
> > +++ b/arch/powerpc/boot/dts/fsl/kmcent2.dts
> > @@ -210,13 +210,19 @@
> >
> > fman@400000 {
> > ethernet@e0000 {
> > - fixed-link = <0 1 1000 0 0>;
> > - phy-connection-type = "sgmii";
> > + phy-mode = "sgmii";
> > + fixed-link {
> > + speed = <1000>;
> > + full-duplex;
> > + };
> > };
> >
> > ethernet@e2000 {
> > - fixed-link = <1 1 1000 0 0>;
> > - phy-connection-type = "sgmii";
> > + phy-mode = "sgmii";
> > + fixed-link {
> > + speed = <1000>;
> > + full-duplex;
> > + };
> > };
> >
> > ethernet@e4000 {
> > @@ -229,7 +235,7 @@
> >
> > ethernet@e8000 {
> > phy-handle = <&front_phy>;
> > - phy-connection-type = "rgmii";
> > + phy-mode = "rgmii-id";
> > };
> >
> > mdio0: mdio@fc000 {
> > --
> > 2.17.1
> >
>
>
next prev parent reply other threads:[~2019-07-28 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 20:05 [PATCH] powerpc/kmcent2: update the ethernet devices' phy properties Valentin Longchamp
2019-07-28 16:01 ` Valentin Longchamp
2019-07-28 19:26 ` Scott Wood [this message]
2019-07-28 20:26 ` Valentin Longchamp
2019-07-30 9:44 ` Madalin-cristian Bucur
2019-08-08 21:09 ` Valentin Longchamp
2019-08-28 4:19 ` Scott Wood
2019-08-29 11:25 ` Madalin-cristian Bucur
2019-09-14 14:29 ` Scott Wood
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=2243421e574c72c5e75d27cc0122338e2e0bde63.camel@buserror.net \
--to=oss@buserror.net \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=valentin@longchamp.me \
/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).