From: "Michael Walle" <mwalle@kernel.org>
To: "Fabio Estevam" <festevam@nabladev.com>
Cc: "Fabio Estevam" <festevam@gmail.com>, <pratyush@kernel.org>,
<takahiro.kuwano@infineon.com>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>, <heiko@sntech.de>,
<linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: spi-nor: xmc: Add XM25QH128C identification
Date: Tue, 21 Jul 2026 10:47:22 +0200 [thread overview]
Message-ID: <DK44A7A87AGB.U01P9983P29J@kernel.org> (raw)
In-Reply-To: <12de54ff-0f0f-a101-4f63-c0b72fd81cf4@nabladev.com>
[-- Attachment #1.1: Type: text/plain, Size: 1423 bytes --]
Hi Fabio,
On Mon Jul 20, 2026 at 8:43 PM CEST, Fabio Estevam wrote:
> On Monday, July 20, 2026 03:45 -03, "Michael Walle" <mwalle@kernel.org> wrote:
>
>> So why do you need an entry? We don't add .names on new entries.
>
> Currently, I see:
>
> root@rk3399-station-p1:~# cat /sys/bus/spi/devices/spi1.0/spi-nor/partname
> spi-nor-generic
> root@rk3399-station-p1:~# cat /sys/bus/spi/devices/spi1.0/spi-nor/jedec_id
> 204018204018
> root@rk3399-station-p1:~# cat /sys/bus/spi/devices/spi1.0/spi-nor/manufacturer
> cat: /sys/bus/spi/devices/spi1.0/spi-nor/manufacturer: No such file or directory
> root@rk3399-station-p1:~#
>
> After this patch:
>
> root@rk3399-station-p1:~# cat /sys/bus/spi/devices/spi1.0/spi-nor/partname
> XM25QH128C
> root@rk3399-station-p1:~# cat /sys/bus/spi/devices/spi1.0/spi-nor/jedec_id
> 204018
> root@rk3399-station-p1:~# cat /sys/bus/spi/devices/spi1.0/spi-nor/manufacturer
> xmc
>
> The advantage of this patch is to provide the partname and manufacturer entries for userspace.
Yeah I get that, but since vendors tend to reuse their flash ids for
different parts, the part name is useless (and probably wrong) most
of the time. The idea was to just expose the id nowadays and if you
really need the flash part name, it's the duty of an userspace
application to figure that out.
-michael
>
> If this is not wanted, feel free to discard this change.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-07-21 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 21:38 [PATCH] mtd: spi-nor: xmc: Add XM25QH128C identification Fabio Estevam
2026-07-20 6:45 ` Michael Walle
2026-07-20 18:43 ` Fabio Estevam
2026-07-21 8:47 ` Michael Walle [this message]
2026-07-21 12:05 ` Fabio Estevam
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=DK44A7A87AGB.U01P9983P29J@kernel.org \
--to=mwalle@kernel.org \
--cc=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=heiko@sntech.de \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=takahiro.kuwano@infineon.com \
--cc=vigneshr@ti.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