[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <D2BT0DT9UQ66.2L497FSY7GMAL@kernel.org>
Date: Fri, 28 Jun 2024 18:51:08 +0200
From: "Michael Walle" <mwalle@...nel.org>
To: "Erez" <erezgeva2@...il.com>
Cc: "Conor Dooley" <conor@...nel.org>, "Erez Geva" <erezgeva@...ime.org>,
<linux-mtd@...ts.infradead.org>, "Tudor Ambarus"
<tudor.ambarus@...aro.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>
Subject: Re: [PATCH 3/4] dt-bindings: mtd: macronix,mx25l12833f: add SPI-NOR
chip
On Fri Jun 28, 2024 at 6:30 PM CEST, Erez wrote:
> I do not know why they decided to use the same JEDEC ID for two chips.
> Your guess is as good as mine.
That's a common pattern and we try hard to figure that out during
probe time instead of hardcoding it. E.g. by looking at the SFDP
data. Have a look at various fixups in drivers/mtd/spi-nor/.
compatibles are really the last resort to distinguish flash devices.
Next time, please mention such information in the commit message,
please.
Also please have a look at
https://docs.kernel.org/driver-api/mtd/spi-nor.html
-michael
Powered by blists - more mailing lists