Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Vishwaroop A <va@nvidia.com>,
	krzk+dt@kernel.org, robh@kernel.org, conor+dt@kernel.org,
	thierry.reding@gmail.com, 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: Tue, 25 Mar 2025 10:36:29 +0000	[thread overview]
Message-ID: <909f0c92-d110-4253-903e-5c81e21e12c9@nvidia.com> (raw)
In-Reply-To: <48f9c8c0-5cac-4812-8d06-501193be731b@sirena.org.uk>

Hi Mark,

On 27/11/2024 17:31, Mark Brown wrote:
> On Wed, Nov 27, 2024 at 05:24:01PM +0000, Jon Hunter wrote:
>> On 27/11/2024 16:09, Mark Brown wrote:
> 
>>> I understand what he's trying to accomplish, it's the same thing as
>>> what everyone who wants to put a raw spidev compatible in their DT is
>>> trying to do.  The way to do this would be something like a DT overlay
>>> that describes whatever is actually connected, or just customise the DT
>>> locally.
> 
>> We could certainly use an overlay, but how do we handle the kernel side? My
>> understanding is that per patch 3/3 we need to reference a compatible string
>> the kernel is aware of. I guess we could use an existing one, but feels like
>> a massive hack. It would be nice if there is something generic we can use
>> for this like 'linux,spidev'.
> 
>> I see that ACPI has something and it does print a warning that this should
>> not be used in production systems.
> 
> You can put 'spidev' in as the compatible and get the warning, we don't
> require specific compatibles if the Linux device ID is good enough.  If
> you genuinely just have bare wires you're probably able to cope with the
> warning.  If something is actually connected you should use the
> compatible for whatever that is, if spidev makes sense for it then
> that'd be OK to add to spidev.


We finally got back to this. Looks like just having 'spidev' as the 
compatible does not work. Apparently, it use to work and yes you would 
get the warning, but that no longer seems to be the case. I see a few 
others have been doing similar things and hacking their device-trees in 
different ways [0].

I completely agree that ideally we would have a proper compatible string 
for this because after all device-tree describes the hardware. One 
use-case that we use is external loop back for verifying SPI by simply 
connecting MOSI to the MISO. Would it be acceptable to have a compatible 
string for external loopback connections?

Thanks
Jon

[0] 
https://stackoverflow.com/questions/53634892/linux-spidev-why-it-shouldnt-be-directly-in-devicetree

-- 
nvpublic


  reply	other threads:[~2025-03-25 10:36 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 [this message]
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
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=909f0c92-d110-4253-903e-5c81e21e12c9@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