Re: [PATCH v5 3/7] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device

--===============7180654269549199444==
Content-Type: multipart/signed;
 boundary=ab797b970cb1ccfb3d1ed84bb9c19a1fb24835b66e0e80a735c859388d87;
 micalg=pgp-sha384; protocol="application/pgp-signature"

--ab797b970cb1ccfb3d1ed84bb9c19a1fb24835b66e0e80a735c859388d87
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

Hi,

On Tue Jul 21, 2026 at 12:17 PM CEST, Manikandan.M wrote:
>> Or rather NVEMEM_DEVID_NONE? There will ever be just one SFDP nvmem
>> device.
>>=20
>> How does the sysfs path looks like?
> Currently the sysfs looks like:
>
> /sys/bus/nvmem/devices/sfdp0
>
> I kept AUTO so that the bare "sfdp" name would clash on a board(if any)=
=20
> with a second flash exposing a "jedec,sfdp" node.

Ah ok. I thought it would have something with spi0,0 in it's path.
So yeah, there could of course be multiple flashes with SFDP.

-michael

--ab797b970cb1ccfb3d1ed84bb9c19a1fb24835b66e0e80a735c859388d87
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iKgEABMJADAWIQTIVZIcOo5wfU/AngkSJzzuPgIf+AUCal9UNBIcbXdhbGxlQGtl
cm5lbC5vcmcACgkQEic87j4CH/hhTQF+KZoFG4/icFLa+LRtgnRP2iyB/1wM4IpR
ZTM2zKxAVZxOaUG+3GTVHda/yUa1WcR6AX4oRgKid0SEZGVzAaONi7xZxyo28lL1
zsopOz7ovlyRsOxy5atv1KquEEQCsyUY3Ug=
=rxYz
-----END PGP SIGNATURE-----

--ab797b970cb1ccfb3d1ed84bb9c19a1fb24835b66e0e80a735c859388d87--


--===============7180654269549199444==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============7180654269549199444==--