From: Willy Tarreau <w@1wt.eu>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Kever Yang <kever.yang@rock-chips.com>,
linux-rockchip@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v3 3/3] nvmem: rockchip-otp: Add support for rk3562
Date: Thu, 5 Feb 2026 16:36:33 +0100 [thread overview]
Message-ID: <aYS5ATObatoDnKFs@1wt.eu> (raw)
In-Reply-To: <3080333.vCJZsxu672@diego>
Hi Heiko,
On Thu, Feb 05, 2026 at 01:50:34PM +0100, Heiko Stübner wrote:
> Hi Willy,
>
> Am Montag, 28. Juli 2025, 21:01:54 Mitteleuropäische Normalzeit schrieb Willy Tarreau:
> > On Tue, Apr 15, 2025 at 06:32:03PM +0800, Kever Yang wrote:
> > > From: Finley Xiao <finley.xiao@rock-chips.com>
> > >
> > > This adds the necessary data for handling otp on the rk3562.
> > >
> > > Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> > > Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> >
> > Successfully tested with Jonas' patches on top of it on my
> > Radxa E20C (RK3528):
> >
> > Tested-by: Willy Tarreau <w@1wt.eu>
>
> as you replied to the rk3562 variant, does that mean the rk3528
> uses the same variant data?
Now you make me doubt, I'll have to recheck the original message
in its series and the patches that I had applied. I seem to
rememeber there were certain common patches between the two but
I don't remember which ones, and it's also possibly that I replied
by accident to the wrong message in the series or that I mistook
one patch for another when comparing them :-/
Ah, I seem to have found it, there's indeed the 3562 in my local
patches and the 3528 as well, both of which rely on the 3568 one:
commit a68433c468c8a9d4789641eb6a40ae571fb7f01f
Author: Finley Xiao <finley.xiao@rock-chips.com>
Date: Tue Apr 15 18:32:03 2025 +0800
nvmem: rockchip-otp: Add support for RK3562
This adds the necessary data for handling otp on the rk3562.
Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
and:
commit 249b07e24d3d1d47b7ec23d5f09a56837b66d7f5
Author: Jonas Karlman <jonas@kwiboo.se>
Date: Sun Mar 16 00:05:45 2025 +0000
nvmem: rockchip-otp: Add support for RK3528
Add support for the OTP controller in RK3528. The OTPC is similar to the
OTPC in RK3562 and RK3568, exept for a missing phy clock and reset.
Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
It's very possible that I visually mistook one for the other when
responding to the series, and if so, I'm really sorry about that!
The former relies on rk3568_data and the latter on rk3528_data, which
is defined like this:
+static const char * const rk3528_otp_clocks[] = {
+ "otp", "apb_pclk", "sbpi",
+};
+
+static const struct rockchip_data rk3528_data = {
+ .size = 0x80,
+ .word_size = sizeof(u16),
+ .clks = rk3528_otp_clocks,
+ .num_clks = ARRAY_SIZE(rk3528_otp_clocks),
+ .reg_read = rk3568_otp_read,
+};
Looks like the patches originally come from this branch that I
manually cherry-picked:
https://github.com/Kwiboo/linux-rockchip/commits/next-20250620-rk3528
I have one extra E20C that's not yet in prod if you're interested in
me running some specific tests. It will not happen quickly but just let
me know if I can help, as it's a nice little machine.
Willy
WARNING: multiple messages have this Message-ID (diff)
From: Willy Tarreau <w@1wt.eu>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Kever Yang <kever.yang@rock-chips.com>,
linux-rockchip@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v3 3/3] nvmem: rockchip-otp: Add support for rk3562
Date: Thu, 5 Feb 2026 16:36:33 +0100 [thread overview]
Message-ID: <aYS5ATObatoDnKFs@1wt.eu> (raw)
In-Reply-To: <3080333.vCJZsxu672@diego>
Hi Heiko,
On Thu, Feb 05, 2026 at 01:50:34PM +0100, Heiko Stübner wrote:
> Hi Willy,
>
> Am Montag, 28. Juli 2025, 21:01:54 Mitteleuropäische Normalzeit schrieb Willy Tarreau:
> > On Tue, Apr 15, 2025 at 06:32:03PM +0800, Kever Yang wrote:
> > > From: Finley Xiao <finley.xiao@rock-chips.com>
> > >
> > > This adds the necessary data for handling otp on the rk3562.
> > >
> > > Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> > > Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> >
> > Successfully tested with Jonas' patches on top of it on my
> > Radxa E20C (RK3528):
> >
> > Tested-by: Willy Tarreau <w@1wt.eu>
>
> as you replied to the rk3562 variant, does that mean the rk3528
> uses the same variant data?
Now you make me doubt, I'll have to recheck the original message
in its series and the patches that I had applied. I seem to
rememeber there were certain common patches between the two but
I don't remember which ones, and it's also possibly that I replied
by accident to the wrong message in the series or that I mistook
one patch for another when comparing them :-/
Ah, I seem to have found it, there's indeed the 3562 in my local
patches and the 3528 as well, both of which rely on the 3568 one:
commit a68433c468c8a9d4789641eb6a40ae571fb7f01f
Author: Finley Xiao <finley.xiao@rock-chips.com>
Date: Tue Apr 15 18:32:03 2025 +0800
nvmem: rockchip-otp: Add support for RK3562
This adds the necessary data for handling otp on the rk3562.
Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
and:
commit 249b07e24d3d1d47b7ec23d5f09a56837b66d7f5
Author: Jonas Karlman <jonas@kwiboo.se>
Date: Sun Mar 16 00:05:45 2025 +0000
nvmem: rockchip-otp: Add support for RK3528
Add support for the OTP controller in RK3528. The OTPC is similar to the
OTPC in RK3562 and RK3568, exept for a missing phy clock and reset.
Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
It's very possible that I visually mistook one for the other when
responding to the series, and if so, I'm really sorry about that!
The former relies on rk3568_data and the latter on rk3528_data, which
is defined like this:
+static const char * const rk3528_otp_clocks[] = {
+ "otp", "apb_pclk", "sbpi",
+};
+
+static const struct rockchip_data rk3528_data = {
+ .size = 0x80,
+ .word_size = sizeof(u16),
+ .clks = rk3528_otp_clocks,
+ .num_clks = ARRAY_SIZE(rk3528_otp_clocks),
+ .reg_read = rk3568_otp_read,
+};
Looks like the patches originally come from this branch that I
manually cherry-picked:
https://github.com/Kwiboo/linux-rockchip/commits/next-20250620-rk3528
I have one extra E20C that's not yet in prod if you're interested in
me running some specific tests. It will not happen quickly but just let
me know if I can help, as it's a nice little machine.
Willy
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-02-05 15:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 10:32 [PATCH v3 0/3] rockchip,otp: Add support for rk3562 and rk3568 Kever Yang
2025-04-15 10:32 ` Kever Yang
2025-04-15 10:32 ` [PATCH v3 1/3] dt-bindings: nvmem: " Kever Yang
2025-04-15 10:32 ` Kever Yang
2025-04-21 18:45 ` Rob Herring (Arm)
2025-04-21 18:45 ` Rob Herring (Arm)
2025-04-22 10:06 ` Heiko Stübner
2025-04-22 10:06 ` Heiko Stübner
2025-04-15 10:32 ` [PATCH v3 2/3] nvmem: rockchip-otp: Add support for rk3568-otp Kever Yang
2025-04-15 10:32 ` Kever Yang
2025-04-22 10:07 ` Heiko Stübner
2025-04-22 10:07 ` Heiko Stübner
2025-04-15 10:32 ` [PATCH v3 3/3] nvmem: rockchip-otp: Add support for rk3562 Kever Yang
2025-04-15 10:32 ` Kever Yang
2025-04-22 10:07 ` Heiko Stübner
2025-04-22 10:07 ` Heiko Stübner
2025-07-28 19:01 ` Willy Tarreau
2025-07-28 19:01 ` Willy Tarreau
2026-02-05 12:50 ` Heiko Stübner
2026-02-05 12:50 ` Heiko Stübner
2026-02-05 15:36 ` Willy Tarreau [this message]
2026-02-05 15:36 ` Willy Tarreau
2026-02-05 21:29 ` Heiko Stübner
2026-02-05 21:29 ` Heiko Stübner
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=aYS5ATObatoDnKFs@1wt.eu \
--to=w@1wt.eu \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.