From: Heiko Stuebner <heiko@sntech.de>
To: srinivas.kandagatla@linaro.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, detlev.casanova@collabora.com,
sebastian.reichel@collabora.com
Subject: [PATCH RESEND v2 0/6] RK3576 OTP support
Date: Mon, 10 Feb 2025 23:45:04 +0100 [thread overview]
Message-ID: <20250210224510.1194963-1-heiko@sntech.de> (raw)
This enables OTP support in the nvmem driver for rk3576.
I expect to pick the clock patch (patch1) and the arm64-dts patch (patch6)
myself, after the nvmem-driver and -binding patches have been applied
(patches 2-5).
But kept them together for people wanting to try this series.
changes in v2:
- fix register constant in clock definition (Diederik)
- add patch to set limits on variant-specific clock-names
- use correct limits for clocks + resets on rk3576 binding
RESEND, because I messed up my git-send-email which caused it to include
the list of patches 2 times, duplicating everything :-( .
Heiko Stuebner (6):
clk: rockchip: rk3576: define clk_otp_phy_g
nvmem: rockchip-otp: Move read-offset into variant-data
dt-bindings: nvmem: rockchip,otp: add missing limits for clock-names
dt-bindings: nvmem: rockchip,otp: Add compatible for RK3576
nvmem: rockchip-otp: add rk3576 variant data
arm64: dts: rockchip: add rk3576 otp node
.../bindings/nvmem/rockchip,otp.yaml | 25 ++++++++++++
arch/arm64/boot/dts/rockchip/rk3576.dtsi | 39 +++++++++++++++++++
drivers/clk/rockchip/clk-rk3576.c | 2 +
drivers/nvmem/rockchip-otp.c | 17 +++++++-
4 files changed, 81 insertions(+), 2 deletions(-)
--
2.47.2
next reply other threads:[~2025-02-10 22:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 22:45 Heiko Stuebner [this message]
2025-02-10 22:45 ` [PATCH RESEND v2 1/6] clk: rockchip: rk3576: define clk_otp_phy_g Heiko Stuebner
2025-02-10 22:45 ` [PATCH RESEND v2 2/6] nvmem: rockchip-otp: Move read-offset into variant-data Heiko Stuebner
2025-02-10 22:45 ` [PATCH RESEND v2 3/6] dt-bindings: nvmem: rockchip,otp: add missing limits for clock-names Heiko Stuebner
2025-02-11 17:56 ` Conor Dooley
2025-02-10 22:45 ` [PATCH RESEND v2 4/6] dt-bindings: nvmem: rockchip,otp: Add compatible for RK3576 Heiko Stuebner
2025-02-11 17:55 ` Conor Dooley
2025-02-10 22:45 ` [PATCH RESEND v2 5/6] nvmem: rockchip-otp: add rk3576 variant data Heiko Stuebner
2025-02-10 22:45 ` [PATCH RESEND v2 6/6] arm64: dts: rockchip: add rk3576 otp node Heiko Stuebner
2025-02-12 12:44 ` [PATCH RESEND v2 0/6] RK3576 OTP support Nicolas Frattaroli
2025-02-12 12:56 ` Heiko Stübner
2025-02-17 9:53 ` (subset) " Srinivas Kandagatla
2025-03-18 9:15 ` Heiko Stübner
2025-02-22 23:48 ` Heiko Stuebner
2025-04-25 22:09 ` 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=20250210224510.1194963-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=srinivas.kandagatla@linaro.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