[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b0f4fee-d46b-4086-9d63-f4093b52748e@sirena.org.uk>
Date: Mon, 31 Mar 2025 13:44:36 +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 01:34:21PM +0100, Jon Hunter wrote:
> On 27/03/2025 15:33, Mark Brown wrote:
> > On Wed, Mar 26, 2025 at 12:16:53PM +0000, Jon Hunter wrote:
> > > That's definitely what we do today, modify the kernel directly to achieve
> > > what we need. I am trying to avoid carrying too many out of tree patches for
> > > stuff like this and have something in the kernel that works by default. This
> > > is even more important for 3rd party Linux distros that will not accept
> > > non-upstream code.
> > Overlays should work well for that case too!
> If you mean device-tree overlays, I don't see how that will work today.
> Unless we are to use one of the existing compatible strings, but that feels
> wrong because we are not using any of those devices and like I mentioned,
> just using 'spidev' alone in device-tree does not work with the latest
> kernels.
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists