From: Willy Tarreau <w@1wt.eu>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: rockchip-otp: Handle internal word_size in main reg_read op
Date: Mon, 28 Jul 2025 21:06:37 +0200 [thread overview]
Message-ID: <20250728190637.GB24527@1wt.eu> (raw)
In-Reply-To: <3635379.iIbC2pHGDl@diego>
On Tue, Apr 22, 2025 at 11:37:06AM +0200, Heiko Stübner wrote:
> Am Sonntag, 16. März 2025, 20:18:58 Mitteleuropäische Sommerzeit schrieb Jonas Karlman:
> > Rockchip SoCs RK3576 and RK3588 read data from the OTP using 32-bit
> > words instead of normal 8-bit bytes. Similar RK3506, RK3528, RK3562 and
> > RK3568 will read data from OTP using 16-bit words.
> >
> > The nvmem core stride and word_size cannot fully be used as cells is not
> > always aligned. Continue to report a stride=1 and word_size=1 in
> > nvmem_config and instead handle use of SoC specific word_size internally
> > in the driver.
> >
> > Move current SoC specific word_size handling from the RK3588 read_reg
> > operation to the main read_reg operation to help simplify the SoC
> > specific read_reg operation and allow code reuse in a future RK3568
> > reg_read operation.
> >
> > Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>
> On both rk3576 and rk3588 compared nvmem content before and after
> the change, so
>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
My understanding is that it's part of the dependency chain needed to
get TSADC to work, and since I could get it to work on my E20C using
Jonas' extra patches, I guess it confirms that it works as well on
RK3528:
Tested-by: Willy Tarreau <w@1wt.eu>
Willy
prev parent reply other threads:[~2025-07-28 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 19:18 Jonas Karlman
2025-04-22 9:37 ` Heiko Stübner
2025-07-28 19:06 ` Willy Tarreau [this message]
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=20250728190637.GB24527@1wt.eu \
--to=w@1wt.eu \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®