From: <Manikandan.M@microchip.com>
To: <michael@walle.cc>, <pratyush@kernel.org>, <mwalle@kernel.org>,
<takahiro.kuwano@infineon.com>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <srini@kernel.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<claudiu.beznea@tuxon.dev>, <linux@armlinux.org.uk>,
<richardcochran@gmail.com>, <linusw@kernel.org>, <arnd@arndb.de>,
<aaro.koskinen@iki.fi>, <gregkh@linuxfoundation.org>,
<mathieu.dubois-briand@bootlin.com>,
<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v8 3/8] nvmem: core: take a reference on dev.of_node in nvmem_register()
Date: Thu, 15 Oct 2026 11:26:29 +0000 [thread overview]
Message-ID: <29e64d3d-a002-496d-a4b6-b696f3f3013d@microchip.com> (raw)
In-Reply-To: <DM5AO9LBE1OI.19L3SG4BQTNB0@walle.cc>
Hi Michael,
On 10/15/26 2:42 PM, Michael Walle wrote:
> On Wed Oct 14, 2026 at 8:40 AM CEST, Manikandan Muralidharan wrote:
>> nvmem_register() stores config->of_node (or config->dev->of_node)
>> into nvmem->dev.of_node without taking its own reference. Callers
>> that get the node via of_get_compatible_child() etc. and drop their
>> reference right after registering leave nvmem->dev.of_node backed by
>> no reference at all.
>>
>> Take an of_node_get() when assigning nvmem->dev.of_node and release
>> it in nvmem_release(). Existing callers that hold their own get/put
>> pair around the registration call need no changes, since get/put on
>> a device_node is per-holder and independent of core now also holding
>> one.
>>
>> Suggested-by: Michael Walle <mwalle@kernel.org>
>> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
>
> Nice!
>
> Did you check if any callers are also taking a reference, which
> might not be needed anymore now.
>
Yes, I checked — none of the callers hold a reference beyond the
registration call itself. The pattern I verified in each drivers is
short-lived, the reference is dropped right after
nvmem_register()/devm_nvmem_register() call.
> Reviewed-by: Michael Walle <mwalle@kernel.org>
>
> -michael
>
>> ---
>> drivers/nvmem/core.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
>> index 0556d140170a..98192597b935 100644
>> --- a/drivers/nvmem/core.c
>> +++ b/drivers/nvmem/core.c
>> @@ -541,6 +541,7 @@ static void nvmem_release(struct device *dev)
>>
>> ida_free(&nvmem_ida, nvmem->id);
>> gpiod_put(nvmem->wp_gpio);
>> + of_node_put(nvmem->dev.of_node);
>> kfree(nvmem->ops);
>> kfree(nvmem);
>> }
>> @@ -950,9 +951,9 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
>> nvmem->keepout = config->keepout;
>> nvmem->nkeepout = config->nkeepout;
>> if (config->of_node)
>> - nvmem->dev.of_node = config->of_node;
>> + nvmem->dev.of_node = of_node_get(config->of_node);
>> else
>> - nvmem->dev.of_node = config->dev->of_node;
>> + nvmem->dev.of_node = of_node_get(config->dev->of_node);
>>
>> switch (config->id) {
>> case NVMEM_DEVID_NONE:
>
--
Thanks and Regards,
Manikandan M.
next prev parent reply other threads:[~2026-10-15 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 6:40 [PATCH v8 0/8] Read MAC address from SST vendor specific SFDP region Manikandan Muralidharan
2026-10-14 6:40 ` [PATCH v8 1/8] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM Manikandan Muralidharan
2026-10-14 6:40 ` [PATCH v8 2/8] dt-bindings: nvmem: layouts: add Microchip/SST SFDP EUI layout Manikandan Muralidharan
2026-10-14 6:40 ` [PATCH v8 3/8] nvmem: core: take a reference on dev.of_node in nvmem_register() Manikandan Muralidharan
2026-10-14 8:36 ` Miquel Raynal
2026-10-15 9:12 ` Michael Walle
2026-10-15 11:26 ` Manikandan.M [this message]
2026-10-14 6:40 ` [PATCH v8 4/8] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device Manikandan Muralidharan
2026-10-14 8:38 ` Miquel Raynal
2026-10-15 9:21 ` Michael Walle
2026-10-14 6:40 ` [PATCH v8 5/8] nvmem: layouts: add Microchip/SST SFDP EUI layout driver Manikandan Muralidharan
2026-10-14 8:52 ` Miquel Raynal
2026-10-15 11:42 ` Manikandan.M
2026-10-14 6:40 ` [PATCH v8 6/8] ARM: dts: microchip: sama5d27_wlsom1: use fixed-partitions for QSPI flash Manikandan Muralidharan
2026-10-14 6:40 ` [PATCH v8 7/8] ARM: dts: microchip: sama5d27_wlsom1: read MAC address from QSPI SFDP Manikandan Muralidharan
2026-10-14 6:40 ` [PATCH v8 8/8] ARM: configs: sama5: enable Microchip/SST SFDP EUI NVMEM layout Manikandan Muralidharan
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=29e64d3d-a002-496d-a4b6-b696f3f3013d@microchip.com \
--to=manikandan.m@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=aaro.koskinen@iki.fi \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=takahiro.kuwano@infineon.com \
--cc=vigneshr@ti.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