mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Robin van der Gracht <robin@protonic.nl>
To: barebox@lists.infradead.org
Subject: Re: [PATCH] nvmem: regmap: Fix nvmem size
Date: Wed, 20 Dec 2023 08:56:53 +0100	[thread overview]
Message-ID: <bba9ad2f824b45f4e49db03b11b39f70@protonic.nl> (raw)
In-Reply-To: <20231219141435.163699-1-robin@protonic.nl>

After applying this patch the last register is writable, but still not 
readable.

The size is now correct:
barebox:/ ls -l /dev/stm32-bsec
crw-------            384 /dev/stm32-bsec

This now works:
mw -l -d /dev/stm32-bsec 0x0000017c+4 0x12345678

This still doesn't:
barebox:/ md -l -s /dev/stm32-bsec 0x0000017c+4
read: Invalid argument

On 2023-12-19 15:14, Robin van der Gracht wrote:
> We should add 1 to the max_register index since counting is zero based.
> 
> i.e. the stm32mp151 bsec has registers 0 - 95 with reg_stride 4.
> Size should be (95 + 1) * 4 = 384 bytes otherwise we can't access bsec
> register 95 (last one).
> 
> Signed-off-by: Robin van der Gracht <robin@protonic.nl>
> ---
>  drivers/nvmem/regmap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/nvmem/regmap.c b/drivers/nvmem/regmap.c
> index fa5405d7a8..ffc96a310f 100644
> --- a/drivers/nvmem/regmap.c
> +++ b/drivers/nvmem/regmap.c
> @@ -78,7 +78,7 @@ nvmem_regmap_register_with_pp(struct regmap *map,
> const char *name,
>  	config.priv = map;
>  	config.stride = 1;
>  	config.word_size = 1;
> -	config.size = regmap_get_max_register(map) * 
> regmap_get_reg_stride(map);
> +	config.size = (regmap_get_max_register(map) + 1) * 
> regmap_get_reg_stride(map);
>  	config.cell_post_process = cell_post_process;
>  	config.reg_write = nvmem_regmap_write;
>  	config.reg_read = nvmem_regmap_read;



      reply	other threads:[~2023-12-20  7:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 14:14 Robin van der Gracht
2023-12-20  7:56 ` Robin van der Gracht [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=bba9ad2f824b45f4e49db03b11b39f70@protonic.nl \
    --to=robin@protonic.nl \
    --cc=barebox@lists.infradead.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