From: Robin van der Gracht <robin@protonic.nl>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master 2/7] nvmem: bsec: correct regmap's max_register
Date: Mon, 8 Jan 2024 13:48:48 +0100 [thread overview]
Message-ID: <20240108134848.5ed633d4@ERD993> (raw)
In-Reply-To: <20240108121709.0f40c768@ERD993>
On Mon, 8 Jan 2024 12:17:09 +0100
Robin van der Gracht <robin@protonic.nl> wrote:
...
> >
> > barebox@Linux Automation MC-1 board:/ ls -l /dev/stm32-bsec
> > crw------- 384 /dev/stm32-bsec
>
> Thats more like it. I'll apply the full series and recheck.
This works as expected. Thanks.
Minor note:
As you mention in your patch notes:
"struct regmap::max_register is in units of struct regmap::reg_stride"
This used to be the value of the maximum register number (index).
The doc in include/linux/regmap.h line 33 mentions 'index'. Maybe that
needs some mentioning of stride as well..
Regardless:
Tested-by: Robin van der Gracht <robin@protonic.nl>
next prev parent reply other threads:[~2024-01-08 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:00 [PATCH master 0/7] regmap: fix size of regmap-backed cdev and nvmem Ahmad Fatoum
2024-01-02 17:00 ` [PATCH master 1/7] regmap: fix calculation of regmap size when reg_stride != 1 Ahmad Fatoum
2024-01-02 17:00 ` [PATCH master 2/7] nvmem: bsec: correct regmap's max_register Ahmad Fatoum
2024-01-08 10:29 ` Robin van der Gracht
2024-01-08 10:44 ` Ahmad Fatoum
2024-01-08 11:17 ` Robin van der Gracht
2024-01-08 12:48 ` Robin van der Gracht [this message]
2024-01-11 7:35 ` Ahmad Fatoum
2024-01-02 17:00 ` [PATCH master 3/7] nvmem: startfive-otp: " Ahmad Fatoum
2024-01-02 17:00 ` [PATCH master 4/7] nvmem: imx-ocotp-ele: " Ahmad Fatoum
2024-01-02 17:00 ` [PATCH master 5/7] nvmem: ocotp: " Ahmad Fatoum
2024-01-02 17:00 ` [PATCH master 6/7] nvmem: ocotp: align OCOTP bank count with Linux Ahmad Fatoum
2024-01-02 17:01 ` [PATCH master 7/7] nvmem: regmap: Fix nvmem size Ahmad Fatoum
2024-01-08 9:43 ` [PATCH master 0/7] regmap: fix size of regmap-backed cdev and nvmem Sascha Hauer
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=20240108134848.5ed633d4@ERD993 \
--to=robin@protonic.nl \
--cc=a.fatoum@pengutronix.de \
--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