Re: [PATCH v4 1/7] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM
Rob Herring <[email protected]>
| Newsgroups | org.infradead.lists.linux-mtd,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.netdev |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jul 02, 2026 at 06:55:15AM +0000, [email protected] 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/