[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250319233024.GA2625856-robh@kernel.org>
Date: Wed, 19 Mar 2025 18:30:24 -0500
From: Rob Herring <robh@...nel.org>
To: Takahiro Kuwano <tkuw584924@...il.com>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>,
Pratyush Yadav <pratyush@...nel.org>,
Michael Walle <mwalle@...nel.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-mtd@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Bacem Daassi <Bacem.Daassi@...ineon.com>,
Takahiro Kuwano <Takahiro.Kuwano@...ineon.com>
Subject: Re: [PATCH 2/3] mtd: spi-nor: use rdid-dummy-ncycles DT property
On Wed, Mar 19, 2025 at 06:47:44PM +0900, Takahiro Kuwano wrote:
> There are infineon flashes [1] that require 8 dummy cycles for the
> 1-1-1 Read ID command. Since the command is not covered by JESD216
> or any other standard, get the number of dummy cycles from DT and use
> them to correctly identify the flash.
If Read ID fails, then couldn't you just retry with dummy cycles? Or
would unconditionally adding dummy cycles adversely affect other chips?
Otherwise, add a specific compatible to imply this requirement. Adding
quirk properties doesn't scale.
Rob
Powered by blists - more mailing lists