[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMuHMdWQ6kGZyUNfcNwrbQhnREA=U8TVpHD0cXPY9dWqFxvjhQ@mail.gmail.com>
Date: Sun, 21 Jun 2020 10:26:17 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Rob Herring <robh+dt@...nel.org>, Andrew Lunn <andrew@...n.ch>,
Oleksij Rempel <linux@...pel-privat.de>,
Philippe Schenker <philippe.schenker@...adex.com>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Kazuya Mizuguchi <kazuya.mizuguchi.ks@...esas.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
netdev <netdev@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH/RFC 1/5] dt-bindings: net: renesas,ravb: Document internal
clock delay properties
Hi Sergei,
On Sat, Jun 20, 2020 at 8:16 PM Sergei Shtylyov
<sergei.shtylyov@...entembedded.com> wrote:
> On 06/19/2020 10:15 PM, Geert Uytterhoeven wrote:
> > Some EtherAVB variants support internal clock delay configuration, which
> > can add larger delays than the delays that are typically supported by
> > the PHY (using an "rgmii-*id" PHY mode, and/or "[rt]xc-skew-ps"
> > properties).
> >
> > Add properties for configuring the internal MAC delays.
> > These properties are mandatory, even when specified as zero, to
> > distinguish between old and new DTBs.
> >
> > Update the example accordingly.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> > --- a/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > +++ b/Documentation/devicetree/bindings/net/renesas,ravb.txt
> > @@ -64,6 +64,18 @@ Optional properties:
> > AVB_LINK signal.
> > - renesas,ether-link-active-low: boolean, specify when the AVB_LINK signal is
> > active-low instead of normal active-high.
> > +- renesas,rxc-delay-ps: Internal RX clock delay.
> > + This property is mandatory and valid only on R-Car Gen3
> > + and RZ/G2 SoCs.
> > + Valid values are 0 and 1800.
> > + A non-zero value is allowed only if phy-mode = "rgmii".
> > + Zero is not supported on R-Car D3.
>
> Hm, where did you see about the D3 limitation?
R-Car Gen3 Hardware User's Manual, Section 50.2.7 ("AVB-DMAC Product
Specific Register (APSR)"), "RDM" bit:
For R-Car D3, delayed mode is only available
> > +- renesas,txc-delay-ps: Internal TX clock delay.
> > + This property is mandatory and valid only on R-Car H3,
> > + M3-W, M3-W+, M3-N, V3M, and V3H, and RZ/G2M and RZ/G2N.
> > + Valid values are 0 and 2000.
> > + A non-zero value is allowed only if phy-mode = "rgmii".
> > + Zero is not supported on R-Car V3H.
>
> Same question about V3H here...
Same section, "TDM" bit:
For R-Car V3H, delayed mode is only available.
> > @@ -105,8 +117,10 @@ Example:
> > "ch24";
> > clocks = <&cpg CPG_MOD 812>;
> > power-domains = <&cpg>;
> > - phy-mode = "rgmii-id";
> > + phy-mode = "rgmii";
> > phy-handle = <&phy0>;
> > + renesas,rxc-delay-ps = <0>;
>
> Mhm, zero RX delay in RGMII-ID mode?
Please ignore the actual contents of the old example. It was based on a
very old DTS, which has received several fixes in the mean time.
Should have written:
Update the (bogus) example accordingly.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists