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 v4 4/4] nvmem: eeprom: at25: export FRAM serial num
Date: Thu, 20 May 2021 07:52:34 +0200 [thread overview]
Message-ID: <YKX5Iqm3AoCXsDV6@kroah.com> (raw)
In-Reply-To: <20210520054714.8736-5-jiri.prchal@aksignal.cz>
On Thu, May 20, 2021 at 07:47:14AM +0200, Jiri Prchal wrote:
> This exports serial number of FRAM in sysfs file named "sernum".
> Formatted in hex, each byte separated by space.
> Example:
> $ cat /sys/class/spi_master/spi0/spi0.0/sernum
No new Documentation/ABI/ entry for this?
> a4 36 44 f2 ae 6c 00 00
>
> Signed-off-by: Jiri Prchal <jiri.prchal@aksignal.cz>
> ---
> v2: no change here
> v3: resend and added more recipients
> v4: resend
> ---
> drivers/misc/eeprom/at25.c | 28 +++++++++++++++++++++++++++-
> 1 file changed, 27 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/misc/eeprom/at25.c b/drivers/misc/eeprom/at25.c
> index 4f6e983c278b..b2cffeb3af2c 100644
> --- a/drivers/misc/eeprom/at25.c
> +++ b/drivers/misc/eeprom/at25.c
> @@ -38,6 +38,7 @@ struct at25_data {
> struct nvmem_config nvmem_config;
> struct nvmem_device *nvmem;
> int has_sernum;
> + char *sernum;
> };
>
> #define AT25_WREN 0x06 /* latch the write enable */
> @@ -172,6 +173,19 @@ static int fm25_aux_read(struct at25_data *at25, char *buf, uint8_t command,
> return status;
> }
>
> +static ssize_t sernum_show(struct device *dev, struct device_attribute *attr, char *buf)
> +{
> + struct at25_data *at25;
> + int i;
> +
> + at25 = dev_get_drvdata(dev);
> + for (i = 0; i < FM25_SN_LEN; i++)
> + buf += sprintf(buf, "%02x ", at25->sernum[i]);
> + sprintf(--buf, "\n");
> + return (3 * i);
No, that is not how sysfs files work, sorry. They are "one value per
file". This looks like multiple values in the same file, why not just
one file per "sernum"?
Also, please use sysfs_emit() in the future.
> +}
> +static DEVICE_ATTR_RO(sernum);
> +
> static int at25_ee_write(void *priv, unsigned int off, void *val, size_t count)
> {
> struct at25_data *at25 = priv;
> @@ -427,8 +441,13 @@ static int at25_probe(struct spi_device *spi)
> else
> at25->chip.flags |= EE_ADDR2;
>
> - if (id[8])
> + if (id[8]) {
> at25->has_sernum = 1;
> + at25->sernum = kzalloc(FM25_SN_LEN, GFP_KERNEL);
> + if (!at25->sernum)
> + return -ENOMEM;
> + fm25_aux_read(at25, at25->sernum, FM25_RDSN, FM25_SN_LEN);
> + }
> else
> at25->has_sernum = 0;
>
> @@ -467,6 +486,13 @@ static int at25_probe(struct spi_device *spi)
> if (IS_ERR(at25->nvmem))
> return PTR_ERR(at25->nvmem);
>
> + /* Export the FM25 serial number */
> + if (at25->has_sernum) {
> + err = device_create_file(&spi->dev, &dev_attr_sernum);
You just raced with userspace and lost :(
Please do this correctly, by setting the driver group if you need a file
like this.
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-20 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 5:47 [PATCH v4 0/4] add support for FRAM Jiri Prchal
2021-05-20 5:47 ` [PATCH v4 1/4] nvmem: eeprom: at25: " Jiri Prchal
2021-05-20 5:53 ` Greg Kroah-Hartman
2021-05-20 6:54 ` Jiří Prchal
2021-05-20 7:08 ` Greg Kroah-Hartman
2021-05-20 5:47 ` [PATCH v4 2/4] " Jiri Prchal
2021-05-20 5:53 ` Greg Kroah-Hartman
2021-05-20 5:47 ` [PATCH v4 3/4] nvmem: eeprom: add documentation " Jiri Prchal
2021-05-20 5:47 ` [PATCH v4 4/4] nvmem: eeprom: at25: export FRAM serial num Jiri Prchal
2021-05-20 5:52 ` Greg Kroah-Hartman [this message]
2021-05-20 6:56 ` Jiří Prchal
2021-05-20 7:08 ` 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=YKX5Iqm3AoCXsDV6@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