All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Takahiro.Kuwano@infineon.com>
To: <manikandan.m@microchip.com>, <pratyush@kernel.org>,
	<mwalle@kernel.org>, <miquel.raynal@bootlin.com>,
	<richard@nod.at>, <vigneshr@ti.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <srini@kernel.org>,
	<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<claudiu.beznea@tuxon.dev>, <linux@armlinux.org.uk>,
	<richardcochran@gmail.com>, <linusw@kernel.org>, <arnd@arndb.de>,
	<michael@walle.cc>, <linux-mtd@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>
Subject: RE: [PATCH v4 3/7] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device
Date: Fri, 3 Jul 2026 09:21:33 +0000	[thread overview]
Message-ID: <d0823b0801bc4339a2653e4a51c488f4@infineon.com> (raw)
In-Reply-To: <8f3b422e0b7749b2a47b14a585dd0a0c@infineon.com>

> Hi,
> 
> > Register the cached SFDP as a read-only NVMEM device rooted at the
> > flash's "sfdp" child node, exposing it in on-flash byte order. This lets
> > NVMEM cells reference any SFDP data: a fixed-layout for parameters at a
> > known offset, or an nvmem-layout parser for vendor data whose location
> > must be discovered at runtime. The device is only registered when an
> > "sfdp" node is present in the device tree.
> >
> > Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
> 
> SFDP is exposed in sysfs (e.g., /sys/bus/spi/devices/spi0.0/spi-nor/sfdp).
> Why don't you just use this existing entry?

Sorry, sysfs is for userspace.
Please just disregard my previous comment.
 
Thanks,
Takahiro


WARNING: multiple messages have this Message-ID (diff)
From: <Takahiro.Kuwano@infineon.com>
To: <manikandan.m@microchip.com>, <pratyush@kernel.org>,
	<mwalle@kernel.org>, <miquel.raynal@bootlin.com>,
	<richard@nod.at>, <vigneshr@ti.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <srini@kernel.org>,
	<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<claudiu.beznea@tuxon.dev>, <linux@armlinux.org.uk>,
	<richardcochran@gmail.com>, <linusw@kernel.org>, <arnd@arndb.de>,
	<michael@walle.cc>, <linux-mtd@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>
Subject: RE: [PATCH v4 3/7] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device
Date: Fri, 3 Jul 2026 09:21:33 +0000	[thread overview]
Message-ID: <d0823b0801bc4339a2653e4a51c488f4@infineon.com> (raw)
In-Reply-To: <8f3b422e0b7749b2a47b14a585dd0a0c@infineon.com>

> Hi,
> 
> > Register the cached SFDP as a read-only NVMEM device rooted at the
> > flash's "sfdp" child node, exposing it in on-flash byte order. This lets
> > NVMEM cells reference any SFDP data: a fixed-layout for parameters at a
> > known offset, or an nvmem-layout parser for vendor data whose location
> > must be discovered at runtime. The device is only registered when an
> > "sfdp" node is present in the device tree.
> >
> > Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
> 
> SFDP is exposed in sysfs (e.g., /sys/bus/spi/devices/spi0.0/spi-nor/sfdp).
> Why don't you just use this existing entry?

Sorry, sysfs is for userspace.
Please just disregard my previous comment.
 
Thanks,
Takahiro


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2026-07-03  9:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  9:23 [PATCH v4 0/7] Read MAC address from SST vendor specific SFDP region Manikandan Muralidharan
2026-06-30  9:23 ` Manikandan Muralidharan
2026-06-30  9:24 ` [PATCH v4 1/7] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan
2026-06-30 22:12   ` Linus Walleij
2026-06-30 22:12     ` Linus Walleij
2026-07-01  8:34     ` Michael Walle
2026-07-01  8:34       ` Michael Walle
2026-07-01 10:53       ` Linus Walleij
2026-07-01 10:53         ` Linus Walleij
2026-07-02  6:13         ` Manikandan.M
2026-07-02  6:13           ` Manikandan.M
2026-07-02  6:16   ` Krzysztof Kozlowski
2026-07-02  6:16     ` Krzysztof Kozlowski
2026-07-02  6:55     ` Manikandan.M
2026-07-02  6:55       ` Manikandan.M
2026-07-02 16:37       ` Rob Herring
2026-07-02 16:37         ` Rob Herring
2026-07-03 10:10         ` Miquel Raynal
2026-07-03 10:10           ` Miquel Raynal
2026-07-03 13:05           ` Michael Walle
2026-07-03 13:05             ` Michael Walle
2026-06-30  9:24 ` [PATCH v4 2/7] dt-bindings: nvmem: layouts: add Microchip/SST SFDP EUI layout Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan
2026-06-30  9:24 ` [PATCH v4 3/7] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan
2026-06-30 22:25   ` Linus Walleij
2026-06-30 22:25     ` Linus Walleij
2026-07-03  5:35   ` Takahiro.Kuwano
2026-07-03  5:35     ` Takahiro.Kuwano
2026-07-03  9:21     ` Takahiro.Kuwano [this message]
2026-07-03  9:21       ` Takahiro.Kuwano
2026-06-30  9:24 ` [PATCH v4 4/7] nvmem: layouts: add Microchip/SST SFDP EUI layout driver Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan
2026-06-30  9:24 ` [PATCH v4 5/7] ARM: dts: microchip: sama5d27_wlsom1: use fixed-partitions for QSPI flash Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan
2026-06-30 22:27   ` Linus Walleij
2026-06-30 22:27     ` Linus Walleij
2026-06-30  9:24 ` [PATCH v4 6/7] ARM: dts: microchip: sama5d27_wlsom1: read MAC address from QSPI SFDP Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan
2026-06-30  9:24 ` [PATCH v4 7/7] ARM: configs: sama5: enable Microchip/SST SFDP EUI NVMEM layout Manikandan Muralidharan
2026-06-30  9:24   ` Manikandan Muralidharan

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=d0823b0801bc4339a2653e4a51c488f4@infineon.com \
    --to=takahiro.kuwano@infineon.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=manikandan.m@microchip.com \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=srini@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.