[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y857VOG5upNJfpdM@sirena.org.uk>
Date: Mon, 23 Jan 2023 12:19:32 +0000
From: Mark Brown <broonie@...nel.org>
To: Alexandre Mergnat <amergnat@...libre.com>
Cc: Michael Walle <michael@...le.cc>, devicetree@...r.kernel.org,
krzysztof.kozlowski+dt@...aro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-spi@...r.kernel.org,
matthias.bgg@...il.com, robh+dt@...nel.org
Subject: Re: [PATCH 2/2] spi: spidev: add new mediatek support
On Mon, Jan 23, 2023 at 10:37:58AM +0100, Alexandre Mergnat wrote:
> Yes I want to expose the SPI on the pin header for two reasons:
> - It's an Evaluation Kit board, I believe exposing SPI helps new
> customers to try/understand it.
That's not how this works. Anyone connecting something to the
SPI header will need to update the DT to reflect whatever they
have connected, if that is something that should be controlled
with spidev then they should add the compatible for that thing
to the driver. If that is something that has a regular driver
then the regular driver will be used.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists