From: Paul Barker <paul.barker.ct@bp.renesas.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Paul Barker <paul.barker.ct@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/9] Configure GbEth for RGMII on RZ/G2L family
Date: Fri, 24 May 2024 10:45:54 +0100 [thread overview]
Message-ID: <20240524094603.988-1-paul.barker.ct@bp.renesas.com> (raw)
For devices in the RZ/G2L family, we have so far relied on U-Boot correctly
configuring the Ethernet interfaces in RGMII mode with PVDD=1.8V before the
kernel is booted. Instead, the required configuration should be described in the
device tree and activated within the pinctrl driver.
Paul Barker (9):
pinctrl: renesas: rzg2l: Fix variable names in OEN functions
pinctrl: renesas: rzg2l: Refactor pin to OEN bit translation
pinctrl: renesas: rzg2l: Support output enable on RZ/G2L
arm64: dts: renesas: rzg2l: Enable Ethernet TXC output
arm64: dts: renesas: rzg2lc: Enable Ethernet TXC output
arm64: dts: renesas: rzg2ul: Enable Ethernet TXC output
arm64: dts: renesas: rzg2l: Set Ethernet PVDD to 1.8V
arm64: dts: renesas: rzg2lc: Set Ethernet PVDD to 1.8V
arm64: dts: renesas: rzg2ul: Set Ethernet PVDD to 1.8V
.../boot/dts/renesas/rzg2l-smarc-som.dtsi | 86 ++++++++++++-------
.../boot/dts/renesas/rzg2lc-smarc-som.dtsi | 43 ++++++----
.../boot/dts/renesas/rzg2ul-smarc-som.dtsi | 86 ++++++++++++-------
drivers/pinctrl/renesas/pinctrl-rzg2l.c | 78 ++++++++++-------
4 files changed, 182 insertions(+), 111 deletions(-)
--
2.39.2
next reply other threads:[~2024-05-24 9:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 9:45 Paul Barker [this message]
2024-05-24 9:45 ` [PATCH 1/9] pinctrl: renesas: rzg2l: Fix variable names in OEN functions Paul Barker
2024-05-30 12:47 ` Geert Uytterhoeven
2024-05-24 9:45 ` [PATCH 2/9] pinctrl: renesas: rzg2l: Refactor pin to OEN bit translation Paul Barker
2024-05-30 12:51 ` Geert Uytterhoeven
2024-05-30 13:55 ` Paul Barker
2024-05-24 9:45 ` [PATCH 3/9] pinctrl: renesas: rzg2l: Support output enable on RZ/G2L Paul Barker
2024-05-30 13:13 ` Geert Uytterhoeven
2024-05-24 9:45 ` [PATCH 4/9] arm64: dts: renesas: rzg2l: Enable Ethernet TXC output Paul Barker
2024-05-30 13:40 ` Geert Uytterhoeven
2024-05-24 9:45 ` [PATCH 5/9] arm64: dts: renesas: rzg2lc: " Paul Barker
2024-05-30 13:47 ` Geert Uytterhoeven
2024-05-24 9:46 ` [PATCH 6/9] arm64: dts: renesas: rzg2ul: " Paul Barker
2024-05-30 13:50 ` Geert Uytterhoeven
2024-05-24 9:46 ` [PATCH 7/9] arm64: dts: renesas: rzg2l: Set Ethernet PVDD to 1.8V Paul Barker
2024-05-30 13:51 ` Geert Uytterhoeven
2024-05-24 9:46 ` [PATCH 8/9] arm64: dts: renesas: rzg2lc: " Paul Barker
2024-05-30 13:51 ` Geert Uytterhoeven
2024-05-24 9:46 ` [PATCH 9/9] arm64: dts: renesas: rzg2ul: " Paul Barker
2024-05-30 13:51 ` Geert Uytterhoeven
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=20240524094603.988-1-paul.barker.ct@bp.renesas.com \
--to=paul.barker.ct@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
/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).