mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Frank Li <Frank.li@nxp.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
	NXP S32 Linux Team <s32@nxp.com>,
	linaro-s32@linaro.org, linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH V2 2/3] nvmem: s32g-ocotp: Add driver for S32G OCOTP
Date: Mon, 1 Sep 2025 23:35:35 +0300	[thread overview]
Message-ID: <aLYDl1lyL1jLMw8c@stanley.mountain> (raw)
In-Reply-To: <aK8zg3sA4csHwAHU@lizhi-Precision-Tower-5810>

On Wed, Aug 27, 2025 at 12:34:11PM -0400, Frank Li wrote:
> > +static int s32g_ocotp_read(void *context, unsigned int offset,
> > +			    void *val, size_t bytes)
> > +{
> > +	struct s32g_ocotp_priv *s32g_data = context;
> > +	u32 *dst = val;
> > +
> > +	while (bytes >= sizeof(u32)) {
> > +		*dst++ = ioread32(s32g_data->base + offset);
> > +
> > +		bytes -= sizeof(u32);
> > +		offset += sizeof(u32);
> > +	}
> 
> readsw() ?
> 

Hi Frank,

I've learned a lot from your reviews.  Thanks.  :)  It would be readsl()
since it's a u32.  But readsl() doesn't increment the offset, it just
reads from the same memory address over and over.

I've made all the other changes.

regards,
dan carpenter


  reply	other threads:[~2025-09-01 20:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 16:37 [PATCH v2 0/3] " Dan Carpenter
2025-08-26 16:38 ` [PATCH V2 1/3] dt-bindings: nvmem: Add the nxp,s32g-ocotp yaml file Dan Carpenter
2025-08-27 16:27   ` Frank Li
2025-08-27 17:26   ` Conor Dooley
2025-08-26 16:38 ` [PATCH V2 2/3] nvmem: s32g-ocotp: Add driver for S32G OCOTP Dan Carpenter
2025-08-27 16:34   ` Frank Li
2025-09-01 20:35     ` Dan Carpenter [this message]
2025-08-26 16:38 ` [PATCH V2 3/3] arm64: dts: s32g: Add device tree information for the OCOTP driver Dan Carpenter
2025-08-26 16:46   ` Frank Li

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=aLYDl1lyL1jLMw8c@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=Frank.li@nxp.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linaro-s32@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s32@nxp.com \
    --cc=srini@kernel.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®