[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42a3fcf1-961b-40de-a9be-e05d0cbb52ee@kernel.org>
Date: Wed, 2 Jul 2025 17:07:07 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jean-François Lessard <jefflessard3@...il.com>,
Andy Shevchenko <andy@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, devicetree@...r.kernel.org,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
Andreas Färber <afaerber@...e.de>,
Boris Gjenero <boris.gjenero@...il.com>,
Christian Hewitt <christianshewitt@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Paolo Sabatino <paolo.sabatino@...il.com>
Subject: Re: [PATCH v2 6/8] dt-bindings: auxdisplay: add Titan Micro
Electronics TM16XX
On 02/07/2025 17:02, Krzysztof Kozlowski wrote:
>>
>> if:
>> properties:
>> compatible:
>> contains:
>> enum:
>> - titanmec,tm1618
>> - titanmec,tm1620
>> - titanmec,tm1628
>> - fdhisi,fd620
>> - fdhisi,fd628
>> - winrise,hbs658
>> then:
>> allOf:
>> - $ref: /schemas/spi/spi-peripheral-props.yaml#
>
> Why is this conditional? Are these devices with entirely different
> programming model? Then they usually should not be in the same binding,
> although depends on differences.
Although I looked again at driver and I think I understand - some of
these do not have SPI interface. Then fine, just put it in allOf:
allOf:
- if:
...
then:
$ref: ...
Some other example for that:
https://elixir.bootlin.com/linux/v5.19/source/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml#L152
Best regards,
Krzysztof
Powered by blists - more mailing lists