From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Erez Geva <erezgeva@nwtime.org>,
linux-mtd@lists.infradead.org,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Esben Haabendal <esben@geanix.com>,
Erez Geva <ErezGeva2@gmail.com>
Subject: Re: [PATCH v5 1/5] mtd: spi-nor: core: add manufacturer flags
Date: Mon, 23 Sep 2024 07:04:22 +0100 [thread overview]
Message-ID: <4e0cf43c-4843-451c-ac6f-86775dbccb2b@linaro.org> (raw)
In-Reply-To: <20240920181231.20542-2-erezgeva@nwtime.org>
Hi,
On 9/20/24 7:12 PM, Erez Geva wrote:
> From: Erez Geva <ErezGeva2@gmail.com>
>
> Add flag for always trying reading SFDP:
> Some vendors reuse all JEDEC IDs on manufacture table
> with new chips that support SFDP.
>
> Add flag for reading OTP parameters from device tree.
> Some vendors reuse JEDEC IDs
> with several chips with different OTP parameters.
> Alternatively we read parameters from SFDP.
> But the OTP parameters are absent from the SFDP.
Do you have some specific flashes that you try to identify? Why can't
they be differentiated at runtime?
> So there is not other way but to add the OTP parameters in the device tree.
>
If there isn't any way to distinguish the flashes at runtime (which I
doubt/challenge btw), then as a last resort we introduce a dedicated
compatible for the flash in cause and specify all needed parameters in a
dedicated flash entry. This shall be more generic as further flash
parameters can be statically specified in the dedicated flash entry,
less invasive for dt, and less confusing for people when they decide
whether to use OTP or not. OTP params in device tree is a no-go.
But again, you have to prove why you can't distinguish the flash at
runtime before introducing a new flash compatible. So don't go this path
before sharing with us what you're trying to achieve.
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-09-23 6:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 18:12 [PATCH v5 0/5] Add support for SPI-NOR Macronix OTP Erez Geva
2024-09-20 18:12 ` [PATCH v5 1/5] mtd: spi-nor: core: add manufacturer flags Erez Geva
2024-09-23 6:04 ` Tudor Ambarus [this message]
2024-09-23 10:31 ` Erez
2024-09-23 10:46 ` Michael Walle
2024-09-23 13:25 ` Erez
2024-09-23 16:19 ` Michael Walle
2024-09-23 16:31 ` Erez
2024-09-23 18:04 ` Tudor Ambarus
2024-09-23 18:21 ` Tudor Ambarus
2024-09-26 7:46 ` Esben Haabendal
2024-09-26 11:08 ` Erez
2024-09-26 11:37 ` Esben Haabendal
2024-09-26 13:16 ` Erez
2024-09-23 12:07 ` Tudor Ambarus
2024-09-23 13:01 ` Erez
2024-09-23 14:18 ` Tudor Ambarus
2024-09-23 14:51 ` Erez
2024-09-23 17:52 ` Tudor Ambarus
2024-09-23 19:30 ` Erez
2024-09-23 21:41 ` Erez
2024-09-24 6:04 ` Tudor Ambarus
2024-09-24 6:01 ` Tudor Ambarus
2024-09-20 18:12 ` [PATCH v5 2/5] mtd: spi-nor: core: add generic functions Erez Geva
2024-09-20 18:12 ` [PATCH v5 3/5] dt-bindings: mtd: spi-nor: add OTP parameters Erez Geva
2024-09-22 20:40 ` Krzysztof Kozlowski
2024-09-23 9:21 ` Erez
2024-09-23 15:42 ` Krzysztof Kozlowski
2024-09-23 15:49 ` Erez
2024-09-20 18:12 ` [PATCH v5 4/5] mtd: spi-nor: macronix: add support for OTP Erez Geva
2024-09-20 18:12 ` [PATCH v5 5/5] mtd: spi-nor: macronix: add manufacturer flags Erez Geva
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=4e0cf43c-4843-451c-ac6f-86775dbccb2b@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=ErezGeva2@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=erezgeva@nwtime.org \
--cc=esben@geanix.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox