[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yk7Ex5ltaxC7Z+N6@sirena.org.uk>
Date: Thu, 7 Apr 2022 12:02:31 +0100
From: Mark Brown <broonie@...nel.org>
To: Kavyasree Kotagiri <kavyasree.kotagiri@...rochip.com>
Cc: robh+dt@...nel.org, krzk+dt@...nel.org,
nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com,
claudiu.beznea@...rochip.com, tudor.ambarus@...rochip.com,
linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
UNGLinuxDriver@...rochip.com, Manohar.Puri@...rochip.com
Subject: Re: [PATCH] spi: atmel,quadspi: Define lan966x QSPI
On Thu, Apr 07, 2022 at 04:24:20PM +0530, Kavyasree Kotagiri wrote:
> @@ -19,6 +19,7 @@ properties:
> - microchip,sam9x60-qspi
> - microchip,sama7g5-qspi
> - microchip,sama7g5-ospi
> + - microchip,lan966x-qspi
Generally DT compatibles should be for specific SoCs rather than having
wildcards in them, even if that means you have to list a lot of SoCs.
Having used wildcards in the past doesn't mean it's a good idea to
continue adding them!
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists