From: "Heiko Stübner" <heiko@sntech.de>
To: Willy Tarreau <w@1wt.eu>
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 <srini@kernel.org>
Subject: Re: [PATCH v3 3/3] nvmem: rockchip-otp: Add support for rk3562
Date: Thu, 05 Feb 2026 22:29:15 +0100 [thread overview]
Message-ID: <4412828.687JKscXgg@diego> (raw)
In-Reply-To: <aYS5ATObatoDnKFs@1wt.eu>
Hi Willy,
Am Donnerstag, 5. Februar 2026, 16:36:33 Mitteleuropäische Normalzeit schrieb Willy Tarreau:
> On Thu, Feb 05, 2026 at 01:50:34PM +0100, Heiko Stübner wrote:
> > 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?
[...]
> 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!
Really, no worries ... it just confused me a bit, while I was
resurrecting the whole thing :-)
[...]
> 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.
With Jonas' blessing I added his patches for the RK3528 and send
the driver thing rebased onto a recent kernel just now [0] with you
in Cc.
I've also send in the corresponding DTS patches for all 3 [1], again
with you in Cc :-) .
So if you can give them a spin on your RK3528 board, that would be great.
Because I need to find my RK3528 board first :-) .
Thanks a lot
Heiko
[0] https://lore.kernel.org/linux-rockchip/20260205211901.490181-1-heiko@sntech.de/T/#t
[1] https://lore.kernel.org/linux-rockchip/20260205212347.490636-1-heiko@sntech.de/T/#t
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Willy Tarreau <w@1wt.eu>
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 <srini@kernel.org>
Subject: Re: [PATCH v3 3/3] nvmem: rockchip-otp: Add support for rk3562
Date: Thu, 05 Feb 2026 22:29:15 +0100 [thread overview]
Message-ID: <4412828.687JKscXgg@diego> (raw)
In-Reply-To: <aYS5ATObatoDnKFs@1wt.eu>
Hi Willy,
Am Donnerstag, 5. Februar 2026, 16:36:33 Mitteleuropäische Normalzeit schrieb Willy Tarreau:
> On Thu, Feb 05, 2026 at 01:50:34PM +0100, Heiko Stübner wrote:
> > 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?
[...]
> 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!
Really, no worries ... it just confused me a bit, while I was
resurrecting the whole thing :-)
[...]
> 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.
With Jonas' blessing I added his patches for the RK3528 and send
the driver thing rebased onto a recent kernel just now [0] with you
in Cc.
I've also send in the corresponding DTS patches for all 3 [1], again
with you in Cc :-) .
So if you can give them a spin on your RK3528 board, that would be great.
Because I need to find my RK3528 board first :-) .
Thanks a lot
Heiko
[0] https://lore.kernel.org/linux-rockchip/20260205211901.490181-1-heiko@sntech.de/T/#t
[1] https://lore.kernel.org/linux-rockchip/20260205212347.490636-1-heiko@sntech.de/T/#t
_______________________________________________
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 21:29 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
2026-02-05 15:36 ` Willy Tarreau
2026-02-05 21:29 ` Heiko Stübner [this message]
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=4412828.687JKscXgg@diego \
--to=heiko@sntech.de \
--cc=finley.xiao@rock-chips.com \
--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=srini@kernel.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 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.