Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Vladimir Oltean <vladimir.oltean@nxp.com>
To:     "David S . Miller" <davem@davemloft.net>,
        Jakub Kicinski <kuba@kernel.org>, netdev@vger.kernel.org
Cc:     devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org,
        Rob Herring <robh+dt@kernel.org>,
        Shawn Guo <shawnguo@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
        Heiner Kallweit <hkallweit1@gmail.com>,
        Russell King <linux@armlinux.org.uk>,
        Vivien Didelot <vivien.didelot@gmail.com>,
        Vladimir Oltean <olteanv@gmail.com>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Prasanna Vengateshan <prasanna.vengateshan@microchip.com>,
        Ansuel Smith <ansuelsmth@gmail.com>,
        =?UTF-8?q?Alvin=20=C5=A0ipraga?= <alsi@bang-olufsen.dk>
Subject: [PATCH net-next 2/6] ARM: dts: ls1021a-tsn: update RGMII delays for sja1105 switch
Date:   Thu, 14 Oct 2021 01:23:09 +0300
Message-Id: <20211013222313.3767605-3-vladimir.oltean@nxp.com>
In-Reply-To: <20211013222313.3767605-1-vladimir.oltean@nxp.com>
References: <20211013222313.3767605-1-vladimir.oltean@nxp.com>
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?P/h041JbknUVmQsvxAkfrjnjEtxy4iMYb29yYpOUwfJvYoQVzZNqGGaA2K9j?=
 =?us-ascii?Q?5Ng/HWOXNY/OXIfLx0GL7/kgZAfZ89jr0eYPOfN6ywNRnv9XnYuu3dpvQ+zZ?=
 =?us-ascii?Q?NzRKvsOq8iBpWmVvudVJQZq5d+LkF8jkifYxiIuyFAjPDxVaPgq+MKHJMwbK?=
 =?us-ascii?Q?qMxhzVuWPWSXHeYoFaAFoZcQhYJGHcJKPUjhCfhU1jYYPAAHvFnREnUgT/Xf?=
 =?us-ascii?Q?3X6auyEMv8MpL87Gn4klZckV40hyumM65gbOHey+dIzKs7az8IkutdNvSvq7?=
 =?us-ascii?Q?J+Fav+ZZK2Q0gCo09Vx8EzJNuuNgOfn8N2aLnhMVCAfPXrZW1csXIraualle?=
 =?us-ascii?Q?wMl5kcNFwqjHI3vl095lgvxW0wHT+f6Qt1T+KRDZUU4BID8CtxsGXxoJhEHF?=
 =?us-ascii?Q?q3SSa21vOxgKL6k4Q8iphVkN2rNWkoAf9PTM7wtlqY9xmIhSO9WciMjj5F11?=
 =?us-ascii?Q?oRKENwLQHLBC1v9xP+Eh3MmG0MVjYQwd7XLQiELJVG272TyelXrxgw/E1Wvd?=
 =?us-ascii?Q?RiPvcFkfYDbcbBMxvg/djF0rPij8onvUOV3K2DSGb8il/o9JfAhUGV9Ipesp?=
 =?us-ascii?Q?j3Xuv9D2WwPxit0BGUWPrcNPDxwormZi7XAjNQtqeSN3hCN5GcP7m1ZO5az1?=
 =?us-ascii?Q?G4qC4qsiYsg0N2EXeRUnOBlp5x3OEX8qQI4MQ1Qj20857Lah2b4AcwAaFOK1?=
 =?us-ascii?Q?YANZCz8Rrn+cUPnVqzyIW1fxVT5EB+USqB/vxcX/RuKJ3lY8ZmhKYZ6+0Jew?=
 =?us-ascii?Q?FvjiaawxvU/cta6i3uyq21xUjFRoiKQb6DfaF+CBp+kWtKhxh/B1ZHoh66Z+?=
 =?us-ascii?Q?dNW5juPCx+DhFNwMjKmhuOvpW3avdoOAQLQMRHBQtZ99poK2xaYSs1MLU70a?=
 =?us-ascii?Q?mmqw3OyKlbVMOI1/wDee5Dg/To2NRi7asHP7/FGntpJBcdQd2dl8EOAUD7jC?=
 =?us-ascii?Q?RYlfJSVp8OAMTyVQAzA8t4jrFPJKHANj5n+1WbwIvPWj4V1THbXMxi6iBahX?=
 =?us-ascii?Q?lSvBvWoTRz5MSvZuG8FRiPi43j2ET8F/kjrB3vAFtsD95PwB/r+5HnqExfff?=
 =?us-ascii?Q?12Ve/Umnb84jwFrbHnETRF3k37PMfgU17Hj49taBfsEZMM6d+l8FLPv5Gu0Q?=
 =?us-ascii?Q?4TY3lFPoeoTgSnZxDoB7Xcd1G1XHwOVKhxtayfcpd2iS7veJXMaZg3VKcUHN?=
 =?us-ascii?Q?IJY7f7ylLuBG5KpULN57ekNScpA3Xkr3sDjk6OEv6VijBvOsZ7JiXER6M1Ml?=
 =?us-ascii?Q?6eMipZE4brShxGxz3e9XAqUTMGQef9+lreglpW/KjBP+8FOV6lZqZNkiXSdV?=
 =?us-ascii?Q?/wT9ojS5SLlZ1BYNkN5cj8H0?=
X-OriginatorOrg: nxp.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cebc3b88-6e8a-4146-ecce-08d98e98338e
X-MS-Exchange-CrossTenant-AuthSource: VI1PR04MB5136.eurprd04.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Oct 2021 22:24:20.2672
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: n5CfpsIOOSk5jw3JHI6T/hrEPYEfLHrAGsKJ/8Cs8s0JAv/Ycz7o4fu0nM0vX6y662lxp39OXoHK3ea08mTLAA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR04MB4816
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

In the new behavior, the sja1105 driver expects there to be explicit
RGMII delays present on the fixed-link ports, otherwise it will complain
that it falls back to legacy behavior, which is to apply RGMII delays
incorrectly derived from the phy-mode string.

In this case, the legacy behavior of the driver is to not apply delays
in any direction (mostly because the SJA1105T can't do that, so this
board uses PCB traces). To preserve that but also silence the driver,
use explicit delays of 0 ns. The delay information from the phy-mode is
ignored by new kernels (it's still RGMII as long as it's "rgmii*"
something), and the explicit {rx,tx}-internal-delay-ps properties are
ignored by old kernels, so the change works both ways.

Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
 arch/arm/boot/dts/ls1021a-tsn.dts | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/boot/dts/ls1021a-tsn.dts b/arch/arm/boot/dts/ls1021a-tsn.dts
index 9d8f0c2a8aba..517286073451 100644
--- a/arch/arm/boot/dts/ls1021a-tsn.dts
+++ b/arch/arm/boot/dts/ls1021a-tsn.dts
@@ -90,6 +90,8 @@ port@4 {
 				/* Internal port connected to eth2 */
 				ethernet = <&enet2>;
 				phy-mode = "rgmii";
+				rx-internal-delay-ps = <0>;
+				tx-internal-delay-ps = <0>;
 				reg = <4>;
 
 				fixed-link {
-- 
2.25.1