From: Jon Hunter <jonathanh@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Vishwaroop A <va@nvidia.com>,
krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV controller
Date: Mon, 31 Mar 2025 14:11:35 +0100 [thread overview]
Message-ID: <c81d7e8b-bcce-46a8-8938-c1ead71a988d@nvidia.com> (raw)
In-Reply-To: <3b0f4fee-d46b-4086-9d63-f4093b52748e@sirena.org.uk>
On 31/03/2025 13:44, Mark Brown wrote:
> 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.
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 could be completely missing your point here, but it is not obvious to
me what you are suggesting?
Jon
--
nvpublic
next prev parent reply other threads:[~2025-03-31 13:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 13:45 [PATCH 0/3] Add spidev nodes for SPI controllers Vishwaroop A
2024-11-26 13:45 ` [PATCH 1/3] arm64: tegra: " Vishwaroop A
2024-11-26 13:45 ` [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV controller Vishwaroop A
2024-11-26 13:56 ` Mark Brown
2024-11-27 15:54 ` Jon Hunter
2024-11-27 16:09 ` Mark Brown
2024-11-27 17:24 ` Jon Hunter
2024-11-27 17:31 ` Mark Brown
2025-03-25 10:36 ` Jon Hunter
2025-03-25 12:10 ` Mark Brown
2025-03-25 12:45 ` Thierry Reding
2025-03-25 13:05 ` Thierry Reding
2025-03-25 15:55 ` Mark Brown
2025-03-25 16:38 ` Thierry Reding
2025-03-25 17:05 ` Mark Brown
2025-03-26 12:16 ` Jon Hunter
2025-03-27 15:33 ` Mark Brown
2025-03-31 12:34 ` Jon Hunter
2025-03-31 12:44 ` Mark Brown
2025-03-31 13:11 ` Jon Hunter [this message]
2025-03-31 14:09 ` Mark Brown
2025-03-25 13:57 ` Mark Brown
2024-11-26 13:45 ` [PATCH 3/3] spi: spidev: add "tegra-spidev" name string Vishwaroop A
2024-11-26 14:02 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c81d7e8b-bcce-46a8-8938-c1ead71a988d@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=va@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox