[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <99e23453-04a3-489a-b50d-c4c8eec9c326@sirena.org.uk>
Date: Mon, 31 Mar 2025 15:09:14 +0100
From: Mark Brown <broonie@...nel.org>
To: Jon Hunter <jonathanh@...dia.com>
Cc: Thierry Reding <thierry.reding@...il.com>, Vishwaroop A <va@...dia.com>,
krzk+dt@...nel.org, robh@...nel.org, conor+dt@...nel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV
controller
On Mon, Mar 31, 2025 at 02:11:35PM +0100, Jon Hunter wrote:
> On 31/03/2025 13:44, Mark Brown wrote:
> > Why would you need to use a compatible string for anything? I'd expect
> > the overlay to add the entire new device, compatible and all.
> We need a compatible string for the SPI device in device-tree. Sorry, but I
> am not sure how we can add a SPI device without one.
> Can you confirm what you mean by 'overlay'? To me an overlay, is purely a
> device-tree overlay and even if we have a device-tree overlay, we are still
> missing the kernel driver part that matches the compatible string.
I would expect the overlay to be a device tree overlay and to add the
entire definition of the device, not just patch the compatible in an
existing half constructed device. I would expect the driver portion of
supporting the device to happen as normal, if spidev makes sense for
whatever devices these are then then that could be upstreamed without
adding them to any board.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists