public inbox for linux-spi@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Mark Brown <broonie@kernel.org>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-spi@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: trivial-devices: add toradex,lava-hat-spi
Date: Tue, 21 Apr 2026 12:05:45 +0200	[thread overview]
Message-ID: <9c9795b0-a8ba-453d-9a92-f07b3ca59070@kernel.org> (raw)
In-Reply-To: <20260421095928.GB23508@francesco-nb>

On 21/04/2026 11:59, Francesco Dolcini wrote:
> 
>> Toradex LAVA hat is way too generic. No, single compatible string is not
>> sufficient, please read writing bindings.
>>
>> Please define exact model and variants.
>>
>>>
>>> The need is to be able to test SPI with a mainline Linux kernel, so I am
>>> looking for a solution that works in mainline Linux.
>>
>> incomplete devices do not stop you from that.
> 
> Do this sentence means that I can send a DT file for inclusion in the
> Linux kernel using a compatible documented in incomplete-devices?

No. You will be testing a mainline DTS + load non-mainline overlay. So
your requirements of "mainline Linux" are fully solved. Overlay is
loaded by bootloader for example and thus your kernel is fully mainline.


> 
>> But you don't get exceptions because you want to mainline your DTS. Your
>> need detailed hardware description and precise compatible per each exact
>> hat ("exists in multiple variants").
> 
> Let me get into more details here, before sending a new patch version.
> 
> We have various LAVA HAT devices, the difference is that they provide
> different features and a different layout, based on the actual carrier
> board they are mated with.
> 
> We have an "Aquila LAVA HAT", that can be mated with the "Aquila
> Development Board", and a "Verdin LAVA HAT", that can be mated with a
> "Verdin Dahlia Board".

Of course, because each device is specific so even the hat must be
specific, unless you have a standard connector like Arduino or RPi.

> 
> As an example, you can find the Verdin Dahlia DTS here,
> ti/k3-am625-verdin-wifi-dahlia.dts, that can be mated with the "Verdin
> LAVA HAT".
> 
> The SPI device on both "Aquila LAVA HAT" and "Verdin LAVA HAT", is the
> same, no differences. On the Aquila variant we
> have two instances of it, while on the Verdin we have only one instance
> of it.
> 
> So, would we need a compatible like this? 
> 
> compatible = "toradex,aquila-lava-hat-spi", "toradex,lava-hat-spi";
> 
> or
> 
> compatible = "toradex,verdin-lava-hat-spi", "toradex,lava-hat-spi";

Yes, assuming that verdin/aquila hat works for EVERY verdin/aquila
board, regardless what SoM or SoC you have there.

Verdin is a SoM family according to:
https://www.toradex.com/computer-on-modules/verdin-arm-family

and I doubt you can attach hat to a SoM. There is no connector on SoM
for the hat... so probably you have a board, like Dahlia.

Best regards,
Krzysztof

  reply	other threads:[~2026-04-21 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 11:45 [PATCH v1 0/2] spi: spidev: Add Toradex LAVA HAT Francesco Dolcini
2026-04-20 11:45 ` [PATCH v1 1/2] dt-bindings: trivial-devices: add toradex,lava-hat-spi Francesco Dolcini
2026-04-20 16:02   ` Conor Dooley
2026-04-20 16:10     ` Krzysztof Kozlowski
2026-04-20 16:26       ` Conor Dooley
2026-04-21  8:38       ` Francesco Dolcini
2026-04-21  8:46         ` Krzysztof Kozlowski
2026-04-21  9:59           ` Francesco Dolcini
2026-04-21 10:05             ` Krzysztof Kozlowski [this message]
2026-04-21 10:16               ` Francesco Dolcini
2026-04-20 11:45 ` [PATCH v1 2/2] spi: spidev: Add Toradex LAVA HAT OF compatible Francesco Dolcini

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=9c9795b0-a8ba-453d-9a92-f07b3ca59070@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=francesco@dolcini.it \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robh@kernel.org \
    /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