From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: maitysanchayan@gmail.com
Cc: arnd@arndb.de, shawnguo@kernel.org, stefan@agner.ch,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node
Date: Thu, 7 Jul 2016 14:16:36 +0100 [thread overview]
Message-ID: <577E5634.7020805@linaro.org> (raw)
In-Reply-To: <20160707123350.GA18563@Sanchayan-Arch.localdomain>
On 07/07/16 13:33, maitysanchayan@gmail.com wrote:
> Hello Srinivas,
>
> On 16-07-07 10:18:49, Srinivas Kandagatla wrote:
>>
>>
>> On 07/07/16 07:39, Sanchayan Maity wrote:
>>> From: Stefan Agner <stefan@agner.ch>
>>>
>>> The existing NVMEM consumer API's do not allow to get a
>>> NVMEM cell directly given a device tree node. This patch
>>> adds a function to provide this functionality.
>>>
>>> Assuming the nvmem cell id name is known, this can be used
>>> as follows
>>>
>>> struct device_node *cell_np;
>>> struct nvmem_cell *foo_cell;
>>>
>>> cell_np = of_find_node_by_name(parent, "foo");
>>> foo_cell = of_nvmem_cell_get_direct(cell_np);
>>
>> I don't see a real gain in adding this new api,
>> This will encourage people to use non-standard nvmem bindings.
>>
>> why not just use standard nvmem bindings.. and use
>>
>> of_nvmem_cell_get(np, "foo");
>>
>> which should work in your case.
>
> It will not work in our case. I believe what you are referring to will
> work if I were to pass the device node pointer which was a NVMEM consumer
> containing the nvmem-cells property. In our case, we pass the device node
> pointer pointing to /soc which is not a nvmem consumer. In this case it
> will not have nvmem-cells property causing of_nvmem_cell_get to return
> EINVAL when it calls of_parse_phandle with "nvmem-cells".
I could not see any bindings/ dt patches or dt examples for this this
series.. so Am guessing your node would look like:
soc {
cfg0: cfg0 {
...
};
cfg1: cfg1 {
...
};
};
If this is not how it looks, can you share the details.
What Am saying is that why not have:
soc {
nvmem-cells = <&cfg0>, <&cfg1>;
nvmem-cell-names = "cfg0", "cfg1";
cfg0: cfg0 {
...
};
cfg1: cfg1 {
...
};
};
>
> Our requirement is to be able to pass the soc node pointer and then
> be able to get a nvmem cell by specifying it's name. So for our case
Why?
> ocotp node has cfg0 and cfg1 which we want but we cannot use existing
> nvmem consumer API since that requires having the nvmem consumer properties
> in the node we are binding to viz. is a direct nvmem consumer.
>
> Regards,
> Sanchayan.
>
>>
>> thanks,
>> srini
>>>
>>> Parent node can also be the of_node of the main SoC device
>>> node.
>>>
>>> Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
>>> ---
>>> drivers/nvmem/core.c | 44 +++++++++++++++++++++++++++++-------------
>>> include/linux/nvmem-consumer.h | 1 +
>>> 2 files changed, 32 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
>>> index 965911d..470abee 100644
>>> --- a/drivers/nvmem/core.c
>>> +++ b/drivers/nvmem/core.c
>>> @@ -743,29 +743,21 @@ static struct nvmem_cell *nvmem_cell_get_from_list(const char *cell_id)
>>>
>>> #if IS_ENABLED(CONFIG_NVMEM) && IS_ENABLED(CONFIG_OF)
>>> /**
>>> - * of_nvmem_cell_get() - Get a nvmem cell from given device node and cell id
>>> + * of_nvmem_cell_get_direct() - Get a nvmem cell from given device node
>>> *
>>> - * @dev node: Device tree node that uses the nvmem cell
>>> - * @id: nvmem cell name from nvmem-cell-names property.
>>> + * @dev node: Device tree node that uses nvmem cell
>>> *
>>> * Return: Will be an ERR_PTR() on error or a valid pointer
>>> * to a struct nvmem_cell. The nvmem_cell will be freed by the
>>> * nvmem_cell_put().
>>> */
>>> -struct nvmem_cell *of_nvmem_cell_get(struct device_node *np,
>>> - const char *name)
>>> +struct nvmem_cell *of_nvmem_cell_get_direct(struct device_node *cell_np)
>>> {
>>> - struct device_node *cell_np, *nvmem_np;
>>> + struct device_node *nvmem_np;
>>> struct nvmem_cell *cell;
>>> struct nvmem_device *nvmem;
>>> const __be32 *addr;
>>> - int rval, len, index;
>>> -
>>> - index = of_property_match_string(np, "nvmem-cell-names", name);
>>> -
>>> - cell_np = of_parse_phandle(np, "nvmem-cells", index);
>>> - if (!cell_np)
>>> - return ERR_PTR(-EINVAL);
>>> + int rval, len;
>>>
>>> nvmem_np = of_get_next_parent(cell_np);
>>> if (!nvmem_np)
>>> @@ -824,6 +816,32 @@ err_mem:
>>>
>>> return ERR_PTR(rval);
>>> }
>>> +EXPORT_SYMBOL_GPL(of_nvmem_cell_get_direct);
>>> +
>>> +/**
>>> + * of_nvmem_cell_get() - Get a nvmem cell from given device node and cell id
>>> + *
>>> + * @dev node: Device tree node that uses the nvmem cell
>>> + * @id: nvmem cell name from nvmem-cell-names property.
>>> + *
>>> + * Return: Will be an ERR_PTR() on error or a valid pointer
>>> + * to a struct nvmem_cell. The nvmem_cell will be freed by the
>>> + * nvmem_cell_put().
>>> + */
>>> +struct nvmem_cell *of_nvmem_cell_get(struct device_node *np,
>>> + const char *name)
>>> +{
>>> + struct device_node *cell_np;
>>> + int index;
>>> +
>>> + index = of_property_match_string(np, "nvmem-cell-names", name);
>>> +
>>> + cell_np = of_parse_phandle(np, "nvmem-cells", index);
>>> + if (!cell_np)
>>> + return ERR_PTR(-EINVAL);
>>> +
>>> + return of_nvmem_cell_get_direct(cell_np);
>>> +}
>>> EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
>>> #endif
>>>
>>> diff --git a/include/linux/nvmem-consumer.h b/include/linux/nvmem-consumer.h
>>> index 9bb77d3..bf879fc 100644
>>> --- a/include/linux/nvmem-consumer.h
>>> +++ b/include/linux/nvmem-consumer.h
>>> @@ -136,6 +136,7 @@ static inline int nvmem_device_write(struct nvmem_device *nvmem,
>>> #endif /* CONFIG_NVMEM */
>>>
>>> #if IS_ENABLED(CONFIG_NVMEM) && IS_ENABLED(CONFIG_OF)
>>> +struct nvmem_cell *of_nvmem_cell_get_direct(struct device_node *cell_np);
>>> struct nvmem_cell *of_nvmem_cell_get(struct device_node *np,
>>> const char *name);
>>> struct nvmem_device *of_nvmem_device_get(struct device_node *np,
>>>
next prev parent reply other threads:[~2016-07-07 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 6:39 [PATCH v4 0/5] Implement SoC driver for Vybrid Sanchayan Maity
2016-07-07 6:39 ` [PATCH v4 1/5] ARM: dts: vfxxx: Add device tree node for OCOTP Sanchayan Maity
2016-07-07 6:39 ` [PATCH v4 2/5] ARM: dts: vfxxx: Add On-Chip ROM node for Vybrid Sanchayan Maity
[not found] ` <cover.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-07 6:39 ` [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node Sanchayan Maity
[not found] ` <0e6294d931bf181376a6f4e1a86df3f6c6a5d575.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-07 9:18 ` Srinivas Kandagatla
[not found] ` <577E1E79.4090809-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-07 12:33 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-07-07 13:16 ` Srinivas Kandagatla [this message]
[not found] ` <577E5634.7020805-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-07 13:48 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <20160707134811.GA2692-2b/appYahYDPUjlVagVGR1Kr0EmMEXJSn9A1Ff6Mc9Q@public.gmane.org>
2016-07-08 15:41 ` Srinivas Kandagatla
[not found] ` <577FC9BA.2020402-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-08 16:42 ` Stefan Agner
2016-07-08 17:23 ` Srinivas Kandagatla
2016-07-14 5:28 ` Stefan Agner
[not found] ` <577FE19E.4000100-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-08-02 5:34 ` maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w
2016-07-07 6:39 ` [PATCH v4 4/5] soc: Add SoC driver for Freescale Vybrid platform Sanchayan Maity
[not found] ` <f600ac1c747813b26c80149b6fdf32d42b114235.1467872014.git.maitysanchayan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-07 7:22 ` Arnd Bergmann
2016-07-07 22:25 ` kbuild test robot
2016-07-07 6:39 ` [PATCH v4 5/5] ARM: dts: vfxxx: Add a compatible binding for Vybrid SoC bus driver Sanchayan Maity
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=577E5634.7020805@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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;
as well as URLs for NNTP newsgroup(s).