From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Tom Rini" <trini@konsulko.com>,
"Michael Walle" <michael@walle.cc>,
linux-arm-kernel@lists.infradead.org, u-boot@lists.denx.de,
linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] nvmem: u-boot-env: find Device Tree nodes for NVMEM cells
Date: Fri, 16 Sep 2022 10:57:13 +0100 [thread overview]
Message-ID: <fd7cf2d0-b115-a13b-7056-0b96fc14b618@linaro.org> (raw)
In-Reply-To: <20220915200629.10270-1-zajec5@gmail.com>
On 15/09/2022 21:06, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> DT binding allows specifying NVMEM cells as NVMEM device (provider)
> subnodes. Looks for such subnodes when building NVMEM cells.
>
> This allows NVMEM consumers to use U-Boot environment variables.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Applied thanks,
--srini
> ---
> drivers/nvmem/u-boot-env.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/nvmem/u-boot-env.c b/drivers/nvmem/u-boot-env.c
> index 9b9abfb8f187..d17a164ae705 100644
> --- a/drivers/nvmem/u-boot-env.c
> +++ b/drivers/nvmem/u-boot-env.c
> @@ -92,6 +92,7 @@ static int u_boot_env_add_cells(struct u_boot_env *priv, uint8_t *buf,
> return -ENOMEM;
> priv->cells[idx].offset = data_offset + value - data;
> priv->cells[idx].bytes = strlen(value);
> + priv->cells[idx].np = of_get_child_by_name(dev->of_node, priv->cells[idx].name);
> }
>
> if (WARN_ON(idx != priv->ncells))
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-16 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 20:06 [PATCH] nvmem: u-boot-env: find Device Tree nodes for NVMEM cells Rafał Miłecki
2022-09-16 9:57 ` Srinivas Kandagatla [this message]
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=fd7cf2d0-b115-a13b-7056-0b96fc14b618@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=rafal@milecki.pl \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).