From: Heiko Stuebner <heiko@sntech.de>
To: heiko@sntech.de
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kever.yang@rock-chips.com, finley.xiao@rock-chips.com, w@1wt.eu,
jonas@kwiboo.se
Subject: [PATCH v2 0/3] Add devicetree nodes for RK3528, RK3562 and RK356x
Date: Thu, 12 Mar 2026 22:30:16 +0100 [thread overview]
Message-ID: <20260312213019.13965-1-heiko@sntech.de> (raw)
This is a companion series to the binding+driver changes [0], that adds
the relevant OTP controller nodes to the core SoC devicetrees.
[0] https://lore.kernel.org/linux-rockchip/20260205211901.490181-1-heiko@sntech.de/T/#t
changes in v2:
- rename node-names to be efuse@... following the dt-specfication
2.2.2. Generic Names Recommendation
Heiko Stuebner (2):
arm64: dts: rockchip: Enable OTP controller for RK3562
arm64: dts: rockchip: Enable OTP controller for RK356x
Jonas Karlman (1):
arm64: dts: rockchip: Enable OTP controller for RK3528
arch/arm64/boot/dts/rockchip/rk3528.dtsi | 47 +++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3562.dtsi | 46 ++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk356x-base.dtsi | 46 ++++++++++++++++++
3 files changed, 139 insertions(+)
--
2.47.3
next reply other threads:[~2026-03-12 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 21:30 Heiko Stuebner [this message]
2026-03-12 21:30 ` [PATCH v2 1/3] arm64: dts: rockchip: Enable OTP controller for RK3562 Heiko Stuebner
2026-03-12 21:30 ` [PATCH v2 2/3] arm64: dts: rockchip: Enable OTP controller for RK356x Heiko Stuebner
[not found] ` <DH4BCBM75EA1.3S6GHUO64SAMA@cknow-tech.com>
2026-03-16 16:22 ` Diederik de Haas
2026-03-12 21:30 ` [PATCH v2 3/3] arm64: dts: rockchip: Enable OTP controller for RK3528 Heiko Stuebner
2026-03-24 19:53 ` [PATCH v2 0/3] Add devicetree nodes for RK3528, RK3562 and RK356x Heiko Stuebner
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=20260312213019.13965-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=finley.xiao@rock-chips.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=w@1wt.eu \
/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