[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0d7e468b-ade5-ea84-97f7-31755c56a853@gmail.com>
Date: Tue, 17 Nov 2020 10:32:21 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
davem@...emloft.net, kuba@...nel.org,
linux-amlogic@...ts.infradead.org, devicetree@...r.kernel.org,
robh+dt@...nel.org, netdev@...r.kernel.org
Cc: jianxin.pan@...ogic.com, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, khilman@...libre.com,
narmstrong@...libre.com, jbrunet@...libre.com, andrew@...n.ch
Subject: Re: [PATCH RFC v2 1/5] dt-bindings: net: dwmac-meson: use picoseconds
for the RGMII RX delay
On 11/15/20 10:52 AM, Martin Blumenstingl wrote:
> Amlogic Meson G12A, G12B and SM1 SoCs have a more advanced RGMII RX
> delay register which allows picoseconds precision. Deprecate the old
> "amlogic,rx-delay-ns" in favour of a new "amlogic,rgmii-rx-delay-ps"
> property.
>
> For older SoCs the only known supported values were 0ns and 2ns. The new
> SoCs have 200ps precision and support RGMII RX delays between 0ps and
> 3000ps.
>
> While here, also update the description of the RX delay to indicate
> that:
> - with "rgmii" or "rgmii-id" the RX delay should be specified
> - with "rgmii-id" or "rgmii-rxid" the RX delay is added by the PHY so
> any configuration on the MAC side is ignored
> - with "rmii" the RX delay is not applicable and any configuration is
> ignored
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
--
Florian
Powered by blists - more mailing lists