From: Michael Walle <michael@walle.cc>
To: Alexander Williams <awill@google.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <p.yadav@ti.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Yicong Yang <yangyicong@hisilicon.com>,
Heiko Thiery <heiko.thiery@gmail.com>
Subject: Re: [PATCH v3 2/2] mtd: spi-nor: add initial sysfs support
Date: Thu, 29 Apr 2021 23:54:08 +0200 [thread overview]
Message-ID: <ceae5479c5146e09a945a89da7d99b10@walle.cc> (raw)
In-Reply-To: <CACqsJN9283nSmgdDTz+LhfiQwfi4ZmrSJEP+0JJ24-KZ7isMEA@mail.gmail.com>
Am 2021-04-29 23:34, schrieb Alexander Williams:
> On Thu, Apr 29, 2021 at 8:57 AM Michael Walle <michael@walle.cc> wrote:
>>
>> Add support to show the manufacturer, the partname and JEDEC
>> identifier
>> as well as to dump the SFDP table. Not all flashes list their SFDP
>> table
>> contents in their datasheet. So having that is useful. It might also
>> be
>> helpful in bug reports from users.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>> Pratyush, Heiko, I've dropped your Acked and Tested-by because there
>> were some changes.
>>
>> .../ABI/testing/sysfs-bus-spi-devices-spi-nor | 31 +++++++
>> drivers/mtd/spi-nor/Makefile | 2 +-
>> drivers/mtd/spi-nor/core.c | 1 +
>> drivers/mtd/spi-nor/core.h | 2 +
>> drivers/mtd/spi-nor/sysfs.c | 92
>> +++++++++++++++++++
>> 5 files changed, 127 insertions(+), 1 deletion(-)
>> create mode 100644
>> Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor
>> create mode 100644 drivers/mtd/spi-nor/sysfs.c
>>
>> diff --git a/Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor
>> b/Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor
>> new file mode 100644
>> index 000000000000..4c88307759e2
>> --- /dev/null
>> +++ b/Documentation/ABI/testing/sysfs-bus-spi-devices-spi-nor
>> @@ -0,0 +1,31 @@
>> +What: /sys/bus/spi/devices/.../jedec_id
>
> Since mtd/spi-nor doesn't own this device (belongs to the spi
> subsystem), should
> we put its attributes under a named subdirectory? Perhaps something
> like
> /sys/bus/spi/devices/.../spi_nor/jedec_id ?
>
> I'm just thinking about avoiding any potential for namespace clashes.
Good idea! Will change that in the next version.
-michael
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2021-04-29 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 15:57 [PATCH v3 0/2] mtd: spi-nor: support dumping sfdp tables Michael Walle
2021-04-29 15:57 ` [PATCH v3 1/2] mtd: spi-nor: sfdp: save a copy of the SFDP data Michael Walle
2021-04-29 15:57 ` [PATCH v3 2/2] mtd: spi-nor: add initial sysfs support Michael Walle
2021-04-29 16:23 ` Alexander Williams
2021-04-29 16:44 ` Michael Walle
2021-04-29 17:38 ` Alexander Williams
2021-04-29 21:34 ` Alexander Williams
2021-04-29 21:54 ` Michael Walle [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=ceae5479c5146e09a945a89da7d99b10@walle.cc \
--to=michael@walle.cc \
--cc=awill@google.com \
--cc=heiko.thiery@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
--cc=yangyicong@hisilicon.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