From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH v3 0/2] arm64: dts: renesas: white-hawk: Add AVB1 and AVB2
Date: Sat, 13 Apr 2024 16:18:04 +0200 [thread overview]
Message-ID: <20240413141806.300989-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hello Geert,
This small series describes the AVB1 and AVB2 found on White-Hawk.
Patch 1/2 prepares the AVB base nodes for r8a779g0 to use a dedicated
MDIO node and switches to use this for AVB0, which is the only node who
currently describes a PHY. The driver and binding change needed to use a
MDIO node are merged in net-next already.
Patch 2/2 add the description for AVB1 and AVB2 found on the Ethernet
sub-board.
See individual patch for change log.
Niklas Söderlund (2):
arm64: dts: renesas: r8a779g0: Use MDIO node for all AVB devices
arm64: dts: renesas: white-hawk: ethernet: Describe AVB1 and AVB2
arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 6 -
.../dts/renesas/white-hawk-cpu-common.dtsi | 23 ++--
.../boot/dts/renesas/white-hawk-ethernet.dtsi | 103 ++++++++++++++++++
3 files changed, 117 insertions(+), 15 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-13 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 14:18 Niklas Söderlund [this message]
2024-04-13 14:18 ` [PATCH v3 1/2] arm64: dts: renesas: r8a779g0: Use MDIO node for all AVB devices Niklas Söderlund
2024-04-24 15:18 ` Geert Uytterhoeven
2024-04-13 14:18 ` [PATCH v3 2/2] arm64: dts: renesas: white-hawk: ethernet: Describe AVB1 and AVB2 Niklas Söderlund
2024-04-24 15:19 ` Geert Uytterhoeven
2024-05-27 11:30 ` [PATCH v3 0/2] arm64: dts: renesas: white-hawk: Add " 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=20240413141806.300989-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@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 read-only IMAP folder(s) and NNTP newsgroup(s).