[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250306210950.1686713-1-jonas@kwiboo.se>
Date: Thu, 6 Mar 2025 21:09:44 +0000
From: Jonas Karlman <jonas@...boo.se>
To: Heiko Stuebner <heiko@...ech.de>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: netdev@...r.kernel.org,
devicetree@...r.kernel.org,
linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Jonas Karlman <jonas@...boo.se>
Subject: [PATCH 0/2] net: stmmac: dwmac-rk: Validate rockchip,grf and php-grf during probe
All Rockchip GMAC variants require writing to GRF to configure e.g.
interface mode and MAC rx/tx delay. The GRF syscon regmap is located
with help of a rockchip,grf and rockchip,php-grf phandle.
However, validating the rockchip,grf and rockchip,php-grf syscon regmap
is deferred until e.g. interface mode or speed is configured.
This series change to validate the rockchip,grf and rockchip,php-grf
syscon regmap at probe time to help simplify the SoC specific operations.
I do not expect that this will introduce any regression. Prior to this,
use of a device tree without a rockchip,grf would fail when interface
mode or speed is configured, with this use of such device tree would
instead result in failure at probe time.
Jonas Karlman (2):
dt-bindings: net: rockchip-dwmac: Require rockchip,grf and
rockchip,php-grf
net: stmmac: dwmac-rk: Validate rockchip,grf and php-grf during probe
.../bindings/net/rockchip-dwmac.yaml | 17 +-
.../net/ethernet/stmicro/stmmac/dwmac-rk.c | 269 ++----------------
2 files changed, 32 insertions(+), 254 deletions(-)
--
2.48.1
Powered by blists - more mailing lists