[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D4DSTDA3HE2B.20ACE70SQAL7A@kernel.org>
Date: Mon, 23 Sep 2024 18:19:15 +0200
From: "Michael Walle" <mwalle@...nel.org>
To: "Erez" <erezgeva2@...il.com>
Cc: "Tudor Ambarus" <tudor.ambarus@...aro.org>, "Erez Geva"
<erezgeva@...ime.org>, <linux-mtd@...ts.infradead.org>, "Pratyush Yadav"
<pratyush@...nel.org>, <linux-kernel@...r.kernel.org>, "Miquel Raynal"
<miquel.raynal@...tlin.com>, "Richard Weinberger" <richard@....at>,
"Vignesh Raghavendra" <vigneshr@...com>, <devicetree@...r.kernel.org>, "Rob
Herring" <robh@...nel.org>, "Krzysztof Kozlowski" <krzk+dt@...nel.org>,
"Conor Dooley" <conor+dt@...nel.org>, "Esben Haabendal" <esben@...nix.com>
Subject: Re: [PATCH v5 1/5] mtd: spi-nor: core: add manufacturer flags
Hi,
> > > I would gladly remove the obsolete mx25l12805d.
> > Why? I don't see any need for that.
> Maybe because we do not want compatibility table?
I don't get this? Anyway, we do not remove support for older
flashes for no reason.
> No, reading the SFDP is great.
> Except for OTP parameters/configuration.
> As there is not way to find OTP parameters using JEDEC ID/SFDP
> So as I understand there are only 2 ways to set the OTP parameters:
> * Use a compatibility.
> * Use dynamic OTP configuration, through DT, sysfs,
* Use the in-kernel database to look up the parameters as it is done
with any other flash device. If the id is reused, look for
differences in the SFDP to figure out the correct flash device,
then add some .fixups to manually add the OTP flags and
parameters.
-michael
Download attachment "signature.asc" of type "application/pgp-signature" (298 bytes)
Powered by blists - more mailing lists