From: FUKAUMI Naoki <naoki@radxa.com>
To: heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jbx6244@gmail.com, pbrobinson@gmail.com,
damon.ding@rock-chips.com, sebastian.reichel@collabora.com,
kylepzak@projectinitiative.io, alchark@gmail.com,
dsimic@manjaro.org, amadeus@jmu.edu.cn,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
FUKAUMI Naoki <naoki@radxa.com>
Subject: [PATCH 0/4] arm64: dts: rockchip: Fix eeprom description for Radxa ROCK 3C/5A/5C
Date: Tue, 11 Nov 2025 05:09:19 +0000 [thread overview]
Message-ID: <20251111050924.54880-1-naoki@radxa.com> (raw)
This patch series fixes incorrect or missing entries related to the
eeprom on the Radxa ROCK 3C, 5A, and 5C.
FUKAUMI Naoki (4):
arm64: dts: rockchip: Move eeprom correct bus for Radxa ROCK 5A
arm64: dts: rockchip: Add eeprom vcc-supply for Radxa ROCK 5A
arm64: dts: rockchip: Add eeprom vcc-supply for Radxa ROCK 3C
arm64: dts: rockchip: Make eeprom read-only for Radxa ROCK 3C/5A/5C
arch/arm64/boot/dts/rockchip/rk3566-rock-3c.dts | 2 ++
arch/arm64/boot/dts/rockchip/rk3588s-rock-5a.dts | 16 +++++++++-------
arch/arm64/boot/dts/rockchip/rk3588s-rock-5c.dts | 1 +
3 files changed, 12 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2025-11-11 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 5:09 FUKAUMI Naoki [this message]
2025-11-11 5:09 ` [PATCH 1/4] arm64: dts: rockchip: Move eeprom correct bus for Radxa ROCK 5A FUKAUMI Naoki
2025-11-11 5:29 ` Dragan Simic
2025-11-11 5:09 ` [PATCH 2/4] arm64: dts: rockchip: Add eeprom vcc-supply " FUKAUMI Naoki
2025-11-11 5:34 ` Dragan Simic
2025-11-11 5:09 ` [PATCH 3/4] arm64: dts: rockchip: Add eeprom vcc-supply for Radxa ROCK 3C FUKAUMI Naoki
2025-11-11 5:37 ` Dragan Simic
2025-11-11 5:09 ` [PATCH 4/4] arm64: dts: rockchip: Make eeprom read-only for Radxa ROCK 3C/5A/5C FUKAUMI Naoki
2025-11-11 5:38 ` Dragan Simic
2025-11-11 5:46 ` [PATCH 0/4] arm64: dts: rockchip: Fix eeprom description " Dragan Simic
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=20251111050924.54880-1-naoki@radxa.com \
--to=naoki@radxa.com \
--cc=alchark@gmail.com \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=damon.ding@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kylepzak@projectinitiative.io \
--cc=linux-rockchip@lists.infradead.org \
--cc=pbrobinson@gmail.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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