From: Randy Dunlap <rdunlap@infradead.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Rob Herring <robh@kernel.org>,
Tim Gover <tim.gover@raspberrypi.com>
Subject: Re: [PATCH 4/5] nvmem: Add driver to expose reserved memory as nvmem
Date: Fri, 29 Jan 2021 09:51:54 -0800 [thread overview]
Message-ID: <730c11da-7ca0-97d9-207b-24b365d9d540@infradead.org> (raw)
In-Reply-To: <20210129171430.11328-5-srinivas.kandagatla@linaro.org>
Hi,
On 1/29/21 9:14 AM, Srinivas Kandagatla wrote:
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index 954d3b4a52ab..fecc19b884bf 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -270,4 +270,12 @@ config SPRD_EFUSE
> This driver can also be built as a module. If so, the module
> will be called nvmem-sprd-efuse.
>
> +config NVMEM_RMEM
> + tristate "Reserved Memory Based Driver Support"
> + help
> + This drivers maps reserved memory into an nvmem device. It might be
This driver
> + useful to expose information left by firmware in memory.
> +
> + This driver can also be built as a module. If so, the module
> + will be called nvmem-rmem.
> endif
next prev parent reply other threads:[~2021-01-29 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:14 [PATCH 0/5] nvmem: patches (set 1) for 5.12 Srinivas Kandagatla
2021-01-29 17:14 ` [PATCH 1/5] nvmem: core: Fix a resource leak on error in nvmem_add_cells_from_of() Srinivas Kandagatla
2021-01-29 17:14 ` [PATCH 2/5] nvmem: imx-iim: Use of_device_get_match_data() Srinivas Kandagatla
2021-01-29 17:14 ` [PATCH 3/5] dt-bindings: nvmem: Add bindings for rmem driver Srinivas Kandagatla
2021-01-29 17:14 ` [PATCH 4/5] nvmem: Add driver to expose reserved memory as nvmem Srinivas Kandagatla
2021-01-29 17:51 ` Randy Dunlap [this message]
2021-01-29 17:14 ` [PATCH 5/5] nvmem: core: skip child nodes not matching binding Srinivas Kandagatla
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=730c11da-7ca0-97d9-207b-24b365d9d540@infradead.org \
--to=rdunlap@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tim.gover@raspberrypi.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).