From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmem: core: add managed version of nvmem_register
Date: Thu, 8 Jun 2017 07:26:15 +0100 [thread overview]
Message-ID: <a6a7d0a7-d8a9-7253-7c9b-40b206e8516a@linaro.org> (raw)
In-Reply-To: <a8b28cf2-8d24-dcf7-4b31-5c21dea0127d@gmail.com>
On 07/06/17 22:55, Heiner Kallweit wrote:
> Am 07.06.2017 um 18:19 schrieb Srinivas Kandagatla:
>>
>> On 04/06/17 12:06, Heiner Kallweit wrote:
>>> Add a device-managed version of nvmem_register.
>>>
>>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>>> ---
>>> Documentation/nvmem/nvmem.txt | 1 +
>>> drivers/nvmem/core.c | 35 +++++++++++++++++++++++++++++++++++
>>> include/linux/nvmem-provider.h | 7 +++++++
>>> 3 files changed, 43 insertions(+)
>>>
>>
>> Thanks for the patch, one comments..
>>> diff --git a/Documentation/nvmem/nvmem.txt b/Documentation/nvmem/nvmem.txt
>>> index dbd40d87..b4ff7862 100644
>>> --- a/Documentation/nvmem/nvmem.txt
>>> +++ b/Documentation/nvmem/nvmem.txt
>>> @@ -37,6 +37,7 @@ and write the non-volatile memory.
>>> A NVMEM provider can register with NVMEM core by supplying relevant
>>> nvmem configuration to nvmem_register(), on success core would return a valid
>>> nvmem_device pointer.
>>> +devm_nvmem_register() is a device-managed version of nvmem_register.
>>>
>>> nvmem_unregister(nvmem) is used to unregister a previously registered provider.
>>>
>>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
>>> index 783eb431..55db219f 100644
>>> --- a/drivers/nvmem/core.c
>>> +++ b/drivers/nvmem/core.c
>>> @@ -531,6 +531,41 @@ int nvmem_unregister(struct nvmem_device *nvmem)
>>> }
>>> EXPORT_SYMBOL_GPL(nvmem_unregister);
>>>
>>> +static void devm_nvmem_release(struct device *dev, void *res)
>>> +{
>>> + nvmem_unregister(*(struct nvmem_device **)res);
>>
>> nvmem_unregister() can fail, how are you going to deal with this error cases?
>>
> As stated in my answer to your other review comment:
> Currently no caller of nvmem_unregister checks the return code.
Currently all nvmem provider drivers check return code of unregister in
remove path.
> Checking the refcount I see more as a debug feature and I think making
No, I don't think its a debug feature!! without this check we would end
up dereferencing a freed pointer.
> nvmem_unregister return void plus a WARN() if refcount != 0 would be better.
WARN() would not be enough to stop the system to crash, in case the
provider just unregisters with active users.
>
> Rgds, Heiner
>
>>
>>> +}
>>> +
>>> +/**
>>> + * devm_nvmem_register() - managed version of nvmem_register
>>> + *
>>> + * @config: nvmem device configuration with which nvmem device is created.
>>> + *
>>> + * Return: Will be an ERR_PTR() on error or a valid pointer to nvmem_device
>>> + * on success.
>>> + */
>>> +
>>> +struct nvmem_device *devm_nvmem_register(const struct nvmem_config *config)
>>
>> For consistency reasons, devm versions of apis should always have dev at as first argument.
>>
>>> +{
>>> + struct nvmem_device *nv, **dr;
>>> +
>>> + dr = devres_alloc(devm_nvmem_release, sizeof(*dr), GFP_KERNEL);
>>> + if (!dr)
>>> + return ERR_PTR(-ENOMEM);
>>> +
>>> + nv = nvmem_register(config);
>>> + if (IS_ERR(nv)) {
>>> + devres_free(dr);
>>> + return nv;
>>> + }
>>> +
>>> + *dr = nv;
>>> + devres_add(config->dev, dr);
>>> +
>>> + return nv;
>>> +}
>>> +EXPORT_SYMBOL_GPL(devm_nvmem_register);
>>> +
>>
>
next prev parent reply other threads:[~2017-06-08 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 11:06 Heiner Kallweit
2017-06-07 16:19 ` Srinivas Kandagatla
2017-06-07 21:55 ` Heiner Kallweit
2017-06-08 6:26 ` Srinivas Kandagatla [this message]
2017-06-08 19:00 ` Heiner Kallweit
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=a6a7d0a7-d8a9-7253-7c9b-40b206e8516a@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.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®