From: Srinivas Kandagatla <srini@kernel.org>
To: Ruoyu Wang <ruoyuw560@gmail.com>, Srinivas Kandagatla <srini@kernel.org>
Cc: Heiko Stuebner <heiko@sntech.de>, Jonas Karlman <jonas@kwiboo.se>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] nvmem: rockchip-otp: skip zero-byte reads
Date: Thu, 16 Jul 2026 22:21:24 +0100 [thread overview]
Message-ID: <0348730b-d16c-48f9-a21e-3ee0b1334c60@kernel.org> (raw)
In-Reply-To: <20260618040859.407326-1-ruoyuw560@gmail.com>
On 6/18/26 5:08 AM, Ruoyu Wang wrote:
> nvmem_device_read() does not reject a zero-byte read before calling the
> provider reg_read callback. rockchip_otp_read() then enables clocks and
> dispatches to the SoC-specific callback.
>
if the core does not do this check then the check belongs in the core
not in individual providers.
--srini
> Return 0 from rockchip_otp_read() before enabling clocks when bytes is
> zero. This avoids hardware access for empty reads and prevents zero
> counts from reaching the internal reg_read callbacks.
>
> Fixes: 8ab099fafbbc ("nvmem: rockchip-otp: Add support for RK3588")
> Suggested-by: Jonas Karlman <jonas@kwiboo.se>
> Signed-off-by: Ruoyu Wang <ruoyuw560@gmail.com>
> ---
> v2:
> - Handle empty reads in rockchip_otp_read() instead of initializing ret in
> rk3588_otp_read().
>
> drivers/nvmem/rockchip-otp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/nvmem/rockchip-otp.c b/drivers/nvmem/rockchip-otp.c
> index 0ec78b5e19e7d..95685a9fcc77b 100644
> --- a/drivers/nvmem/rockchip-otp.c
> +++ b/drivers/nvmem/rockchip-otp.c
> @@ -272,6 +272,9 @@ static int rockchip_otp_read(void *context, unsigned int offset,
> if (!otp->data || !otp->data->reg_read)
> return -EINVAL;
>
> + if (!bytes)
> + return 0;
> +
> ret = clk_bulk_prepare_enable(otp->data->num_clks, otp->clks);
> if (ret < 0) {
> dev_err(otp->dev, "failed to prepare/enable clks\n");
prev parent reply other threads:[~2026-07-16 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 4:08 Ruoyu Wang
2026-07-16 21:21 ` Srinivas Kandagatla [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=0348730b-d16c-48f9-a21e-3ee0b1334c60@kernel.org \
--to=srini@kernel.org \
--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=ruoyuw560@gmail.com \
/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
Powered by JetHome