From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiri Prchal <jiri.prchal@aksignal.cz>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Christian Eggers <ceggers@arri.de>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v7 1/5] nvmem: eeprom: at25: prepare basics for FRAM support
Date: Mon, 7 Jun 2021 14:35:07 +0200 [thread overview]
Message-ID: <YL4Se3bQfnBYV8yN@kroah.com> (raw)
In-Reply-To: <20210607122640.143582-2-jiri.prchal@aksignal.cz>
On Mon, Jun 07, 2021 at 02:26:36PM +0200, Jiri Prchal wrote:
> Added enum and string for FRAM to expose it as "fram".
>
> Signed-off-by: Jiri Prchal <jiri.prchal@aksignal.cz>
> ---
> v2: no change here
> v3: resend and added more recipients
> v4: resend
> v5: no change here
> v6: changed commit subject
> v7: no change here
> ---
> drivers/nvmem/core.c | 4 ++++
> include/linux/nvmem-provider.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index 177f5bf27c6d..01ef9a934b0a 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -180,6 +180,7 @@ static const char * const nvmem_type_str[] = {
> [NVMEM_TYPE_EEPROM] = "EEPROM",
> [NVMEM_TYPE_OTP] = "OTP",
> [NVMEM_TYPE_BATTERY_BACKED] = "Battery backed",
> + [NVMEM_TYPE_FRAM] = "FRAM",
> };
>
> #ifdef CONFIG_DEBUG_LOCK_ALLOC
> @@ -359,6 +360,9 @@ static int nvmem_sysfs_setup_compat(struct nvmem_device *nvmem,
> if (!config->base_dev)
> return -EINVAL;
>
> + if (config->type == NVMEM_TYPE_FRAM)
> + bin_attr_nvmem_eeprom_compat.attr.name = "fram";
> +
As this is a new sysfs file, where is the documentation for it?
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-07 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 12:26 [PATCH v7 0/5] add support for FRAM Jiri Prchal
2021-06-07 12:26 ` [PATCH v7 1/5] nvmem: eeprom: at25: prepare basics for FRAM support Jiri Prchal
2021-06-07 12:35 ` Greg Kroah-Hartman [this message]
2021-06-07 12:26 ` [PATCH v7 2/5] nvmem: eeprom: at25: add support for FRAM Jiri Prchal
2021-06-07 12:26 ` [PATCH v7 3/5] nvmem: eeprom: add documentation " Jiri Prchal
2021-06-07 13:09 ` Enrico Weigelt, metux IT consult
2021-06-07 12:26 ` [PATCH v7 4/5] nvmem: eeprom: at25: export FRAM serial num Jiri Prchal
2021-06-07 12:36 ` Greg Kroah-Hartman
2021-06-07 14:47 ` Jiří Prchal
2021-06-08 9:03 ` Greg Kroah-Hartman
2021-06-08 9:45 ` Jiří Prchal
2021-06-08 9:53 ` Greg Kroah-Hartman
2021-06-08 10:07 ` Jiří Prchal
2021-06-10 7:51 ` Jiří Prchal
2021-06-07 12:26 ` [PATCH v7 5/5] nvmem: eeprom: add documentation of sysfs sernum file Jiri Prchal
2021-06-07 12:37 ` Greg Kroah-Hartman
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=YL4Se3bQfnBYV8yN@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=ceggers@arri.de \
--cc=devicetree@vger.kernel.org \
--cc=jiri.prchal@aksignal.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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