From: Rob Herring <robh@kernel.org>
To: Manikandan.M@microchip.com
Cc: krzk@kernel.org, pratyush@kernel.org, mwalle@kernel.org,
takahiro.kuwano@infineon.com, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, 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 1/7] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM
Date: Thu, 2 Jul 2026 11:37:23 -0500 [thread overview]
Message-ID: <20260702163723.GA227454-robh@kernel.org> (raw)
In-Reply-To: <860213fd-6a4b-42d4-a8f7-7308e070f09e@microchip.com>
On Thu, Jul 02, 2026 at 06:55:15AM +0000, Manikandan.M@microchip.com wrote:
> Hi Krzysztof,
>
> On 7/2/26 11:46 AM, Krzysztof Kozlowski wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Tue, Jun 30, 2026 at 02:54:00PM +0530, Manikandan Muralidharan wrote:
> >> Add an optional "sfdp" child node (compatible "jedec,sfdp") that
> >> describes the SFDP as a read-only NVMEM provider via nvmem.yaml, so its
> >
> > What is SFDP?
> >
> SFDP is the Serial Flash Discoverable Parameters -- a JEDEC-standardised
> (JESD216) read-only parameter table present in most SPI NOR flashes, the
> table contents provide basic information about the flash. There are
> standard tables which are specified by the JEDEC standard and there are
> vendor tables.
Is SFDP present or not discoverable? Or we have a table of discoverable
parameters that itself is not discoverable.
If it is discoverable, why does this need to be in DT?
Rob
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Manikandan.M@microchip.com
Cc: krzk@kernel.org, pratyush@kernel.org, mwalle@kernel.org,
takahiro.kuwano@infineon.com, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, 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 1/7] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM
Date: Thu, 2 Jul 2026 11:37:23 -0500 [thread overview]
Message-ID: <20260702163723.GA227454-robh@kernel.org> (raw)
In-Reply-To: <860213fd-6a4b-42d4-a8f7-7308e070f09e@microchip.com>
On Thu, Jul 02, 2026 at 06:55:15AM +0000, Manikandan.M@microchip.com wrote:
> Hi Krzysztof,
>
> On 7/2/26 11:46 AM, Krzysztof Kozlowski wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Tue, Jun 30, 2026 at 02:54:00PM +0530, Manikandan Muralidharan wrote:
> >> Add an optional "sfdp" child node (compatible "jedec,sfdp") that
> >> describes the SFDP as a read-only NVMEM provider via nvmem.yaml, so its
> >
> > What is SFDP?
> >
> SFDP is the Serial Flash Discoverable Parameters -- a JEDEC-standardised
> (JESD216) read-only parameter table present in most SPI NOR flashes, the
> table contents provide basic information about the flash. There are
> standard tables which are specified by the JEDEC standard and there are
> vendor tables.
Is SFDP present or not discoverable? Or we have a table of discoverable
parameters that itself is not discoverable.
If it is discoverable, why does this need to be in DT?
Rob
next prev parent reply other threads:[~2026-07-02 16:37 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 [this message]
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
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=20260702163723.GA227454-robh@kernel.org \
--to=robh@kernel.org \
--cc=Manikandan.M@microchip.com \
--cc=Nicolas.Ferre@microchip.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=krzk@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=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=richardcochran@gmail.com \
--cc=srini@kernel.org \
--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 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.