From: Alexander Dahl <ada@thorsis.com>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: Alexander Dahl <ada@thorsis.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ryan Wanner <ryan.wanner@microchip.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
Srinivas Kandagatla <srini@kernel.org>
Subject: Re: [PATCH v3 14/19] nvmem: microchip-otpc: Expose UID registers as 2nd nvmem device
Date: Fri, 20 Feb 2026 11:38:23 +0100 [thread overview]
Message-ID: <20260220-maximize-glance-a0abd1806c44@thorsis.com> (raw)
In-Reply-To: <05128a16-553d-49d5-b09d-2c3e03cb4421@tuxon.dev>
Hello Claudiu,
thanks for your feedback on this, see my remarks inline below.
Am Sat, Jan 31, 2026 at 06:11:56PM +0200 schrieb Claudiu Beznea:
>
>
> On 1/20/26 17:44, Alexander Dahl wrote:
> > For SAM9X60 the Product UID x Register containing the Unique Product ID
> > is part of the OTPC registers.
>
> SAMA7G5 as well.
>
> > We have everything at hand here to just
> > create a trivial nvmem device for those.
>
> Please massage a bit the patch description to match https://www.kernel.org/doc/html/v6.13/process/submitting-patches.html#describe-your-changes
>
> >
> > Signed-off-by: Alexander Dahl <ada@thorsis.com>
> > ---
> >
> > Notes:
> > v3:
> > - no changes
> > v2:
> > - Use dev_err_probe() for error reporting (thanks Claudiu)
> > - Move required register definition over here from removed patch
> >
> > drivers/nvmem/microchip-otpc.c | 38 +++++++++++++++++++++++++++++++++-
> > 1 file changed, 37 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/nvmem/microchip-otpc.c b/drivers/nvmem/microchip-otpc.c
> > index 34c0d7611f3e4..b35ed13b004bb 100644
> > --- a/drivers/nvmem/microchip-otpc.c
> > +++ b/drivers/nvmem/microchip-otpc.c
> > @@ -25,10 +25,14 @@
> > #define MCHP_OTPC_HR (0x20)
> > #define MCHP_OTPC_HR_SIZE GENMASK(15, 8)
> > #define MCHP_OTPC_DR (0x24)
> > +#define MCHP_OTPC_UID0R (0x60)
> > #define MCHP_OTPC_NAME "mchp-otpc"
> > #define MCHP_OTPC_SIZE (11 * 1024)
> > +#define MCHP_OTPC_UID_NAME "mchp-uid"
> > +#define MCHP_OTPC_UID_SIZE 16
>
> I think you can drop these as they are used (individually) in a single place.
If you don't mind I would rather keep it here together with already
present similar definitions, instead of sprinkling new literals over
this c file.
>
> > +
> > /**
> > * struct mchp_otpc - OTPC private data structure
> > * @base: base address
> > @@ -230,6 +234,16 @@ static int mchp_otpc_init_packets_list(struct mchp_otpc *otpc, u32 *size)
> > return 0;
> > }
> > +static int mchp_otpc_uid_read(void *priv, unsigned int offset,
> > + void *val, size_t bytes)
> > +{
> > + struct mchp_otpc *otpc = priv;
> > +
> > + memcpy_fromio(val, otpc->base + MCHP_OTPC_UID0R + offset, bytes);
>
> Include <asm-generic/logic_io.h> for this one?
Yes, include what you use, I'd add `#include <linux/io.h>` then, seems
the usual way in drivers/nvmem.
>
> > +
> > + return 0;
> > +}
> > +
> > static struct nvmem_config mchp_nvmem_config = {
> > .name = MCHP_OTPC_NAME,
> > .type = NVMEM_TYPE_OTP,
> > @@ -239,6 +253,15 @@ static struct nvmem_config mchp_nvmem_config = {
> > .reg_read = mchp_otpc_read,
> > };
> > +static struct nvmem_config mchp_otpc_uid_nvmem_config = {
> > + .name = MCHP_OTPC_UID_NAME,
>
> Should the type be filled here?
In general I would say yes, but looking at `enum nvmem_type` none of
them seems to match. IIRC I more or less copied the approach from
drivers/soc/atmel/sfr.c here.
Greets
Alex
>
>
> > + .read_only = true,
> > + .word_size = 4,
> > + .stride = 4,
> > + .size = MCHP_OTPC_UID_SIZE,
> > + .reg_read = mchp_otpc_uid_read,
> > +};
> > +
> > static int mchp_otpc_probe(struct platform_device *pdev)
> > {
> > struct nvmem_device *nvmem;
> > @@ -269,8 +292,21 @@ static int mchp_otpc_probe(struct platform_device *pdev)
> > mchp_nvmem_config.size = size;
> > mchp_nvmem_config.priv = otpc;
> > nvmem = devm_nvmem_register(&pdev->dev, &mchp_nvmem_config);
> > + if (IS_ERR(nvmem)) {
> > + return dev_err_probe(&pdev->dev, PTR_ERR(nvmem),
> > + "Error registering OTP as nvmem device\n");
> > + }
> > - return PTR_ERR_OR_ZERO(nvmem);
> > + mchp_otpc_uid_nvmem_config.dev = otpc->dev;
> > + mchp_otpc_uid_nvmem_config.priv = otpc;
> > +
> > + nvmem = devm_nvmem_register(&pdev->dev, &mchp_otpc_uid_nvmem_config);
> > + if (IS_ERR(nvmem)) {
> > + return dev_err_probe(&pdev->dev, PTR_ERR(nvmem),
> > + "Error registering UIDxR as nvmem device\n");
> > + }
> > +
> > + return 0;
> > }
> > static const struct of_device_id __maybe_unused mchp_otpc_ids[] = {
>
next prev parent reply other threads:[~2026-02-20 10:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 14:37 [PATCH v3 00/19] Microchip OTPC driver on SAM9X60 exposing UIDxR as additional nvmem device Alexander Dahl
2026-01-20 14:37 ` [PATCH v3 01/19] MAINTAINERS: Add sam9/sama to (AT91) SoC support Alexander Dahl
2026-01-20 14:37 ` [PATCH v3 02/19] dt-bindings: clock: at91: Split up per SoC partially Alexander Dahl
2026-01-22 16:46 ` Rob Herring (Arm)
2026-01-31 15:43 ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 03/19] dt-bindings: clock: at91: Allow referencing main rc oscillator in DT Alexander Dahl
2026-01-31 15:44 ` Claudiu Beznea
2026-02-09 8:08 ` Alexander Dahl
2026-03-08 16:43 ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 04/19] clk: at91: Use new PMC bindings Alexander Dahl
2026-01-31 15:44 ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 05/19] clk: at91: sama7d65: Use highest PMC definition as max index Alexander Dahl
2026-01-31 15:45 ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 06/19] clk: at91: Allow enabling main_rc_osc through DT Alexander Dahl
2026-01-31 15:45 ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 07/19] clk: at91: Add peripheral id for OTPC Alexander Dahl
2026-01-31 15:45 ` Claudiu Beznea
2026-01-20 15:44 ` Alexander Dahl
2026-01-20 15:44 ` [PATCH v3 08/19] dt-bindings: nvmem: microchip-otpc: Add compatible for SAM9X60 Alexander Dahl
2026-01-20 15:44 ` [PATCH v3 09/19] dt-bindings: nvmem: microchip-otpc: Add required clocks Alexander Dahl
2026-01-20 16:30 ` Rob Herring (Arm)
2026-01-31 15:47 ` Claudiu Beznea
2026-01-31 15:51 ` Claudiu Beznea
2026-02-20 9:58 ` Alexander Dahl
2026-03-08 16:42 ` Claudiu Beznea
2026-03-08 16:45 ` Claudiu Beznea
2026-01-20 15:44 ` [PATCH v3 10/19] nvmem: microchip-otpc: Avoid reading a write-only register Alexander Dahl
2026-01-31 15:58 ` Claudiu Beznea
2026-01-20 15:44 ` [PATCH v3 11/19] nvmem: microchip-otpc: Fix swapped 'sleep' and 'timeout' parameters Alexander Dahl
2026-01-31 16:00 ` Claudiu Beznea
2026-01-20 15:44 ` [PATCH v3 12/19] nvmem: microchip-otpc: Add SAM9X60 support Alexander Dahl
2026-01-31 15:53 ` Claudiu Beznea
2026-01-20 15:44 ` [PATCH v3 13/19] nvmem: microchip-otpc: Enable necessary clocks Alexander Dahl
2026-01-31 16:03 ` Claudiu Beznea
2026-01-20 15:44 ` [PATCH v3 14/19] nvmem: microchip-otpc: Expose UID registers as 2nd nvmem device Alexander Dahl
2026-01-31 16:11 ` Claudiu Beznea
2026-02-20 10:38 ` Alexander Dahl [this message]
2026-03-08 16:40 ` Claudiu Beznea
2026-01-20 15:44 ` [PATCH v3 15/19] ARM: dts: microchip: Use new PMC bindings Alexander Dahl
2026-01-20 15:44 ` [PATCH v3 16/19] ARM: dts: microchip: sama7g5: Add OTPC clocks Alexander Dahl
2026-01-20 15:44 ` [PATCH v3 17/19] ARM: dts: microchip: sam9x60: Add OTPC node Alexander Dahl
2026-01-20 15:44 ` [PATCH v3 18/19] ARM: dts: microchip: sam9x60_curiosity: Enable OTP Controller Alexander Dahl
2026-01-20 15:44 ` [PATCH v3 19/19] dt-bindings: clock: at91: Remove old PMC definitions Alexander Dahl
2026-01-22 16:47 ` Rob Herring (Arm)
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=20260220-maximize-glance-a0abd1806c44@thorsis.com \
--to=ada@thorsis.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=ryan.wanner@microchip.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