From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Jean-François Lessard" <jefflessard3@gmail.com>
Cc: "Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
"Boris Gjenero" <boris.gjenero@gmail.com>,
"Christian Hewitt" <christianshewitt@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Paolo Sabatino" <paolo.sabatino@gmail.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH v3 2/4] dt-bindings: auxdisplay: add Titan Micro Electronics TM16xx
Date: Fri, 22 Aug 2025 08:44:26 +0200 [thread overview]
Message-ID: <68ff2e14-19db-4d4c-8390-8fd2ec9e2c48@kernel.org> (raw)
In-Reply-To: <7CD0DD74-EB4A-414B-B22E-E9248ECF8CBC@gmail.com>
On 21/08/2025 17:16, Jean-François Lessard wrote:
>>
>>> + # Controllers with titanmec,tm1650 fallback
>>> + - items:
>>> + - enum:
>>> + - fdhisi,fd650
>>> + - wxicore,aip650
>>> + - const: titanmec,tm1650
>>> + - const: titanmec,tm1650
>>> + # Canonical standalone controllers
>>
>> Drop
>>
>>> + - const: fdhisi,fd620
>>> + - const: fdhisi,fd655
>>> + - const: fdhisi,fd6551
>>> + - const: titanmec,tm1620
>>> + - const: titanmec,tm1638
>>> + - const: winrise,hbs658
>>
>> This is one enum
>>
>
> Well received. I followed the older style and will adopt the modern approach:
>
> properties:
> compatible:
> items:
> - enum:
> - fdhisi,fd628
> - princeton,pt6964
> - wxicore,aip1628
> - wxicore,aip1618
> - fdhisi,fd650
> - wxicore,aip650
> - fdhisi,fd620
> - fdhisi,fd655
> - fdhisi,fd6551
> - titanmec,tm1620
> - titanmec,tm1638
> - winrise,hbs658
> - enum:
> - titanmec,tm1628
> - titanmec,tm1618
> - titanmec,tm1650
> minItems: 1
> maxItems: 2
>
> Fallback relationships will be documented explicitly in the binding’s description.
Sorry, but what? I commented under specific lines. Why are you changing
other things?
>
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + label:
>>> + description: Name of the entire device
>>> + default: display
>>
>> Huh? Why do you need label? Are you sure auxdisplays have labels?
>>
>>
>
> Display integrates with the LED subsystem (/sys/class/leds), where label is
> a standard property per leds/common.yaml. It ensures predictable LED class
> device naming when multiple display instances are present, following established
> LED subsystem conventions rather than general DT naming rules.
You want to say that top level node is like LED? Then probably it misses
common.yaml reference. Although I am still puzzled... you have sub nodes
for actual LEDs, no?
>
> If helpful, I can add a $ref to /schemas/leds/common.yaml#/properties/label
> or include its description explicitly.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-22 6:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 16:31 [PATCH v3 0/4] auxdisplay: Add TM16xx 7-segment LED matrix display controllers driver Jean-François Lessard
2025-08-20 16:31 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add fdhisi, titanmec, princeton, winrise, wxicore Jean-François Lessard
2025-08-20 20:08 ` Conor Dooley
2025-08-21 19:35 ` Jean-François Lessard
2025-08-21 20:13 ` Conor Dooley
2025-08-22 2:35 ` Jean-François Lessard
2025-08-20 16:31 ` [PATCH v3 2/4] dt-bindings: auxdisplay: add Titan Micro Electronics TM16xx Jean-François Lessard
2025-08-21 7:48 ` Krzysztof Kozlowski
2025-08-21 15:16 ` Jean-François Lessard
2025-08-22 6:44 ` Krzysztof Kozlowski [this message]
2025-08-22 13:32 ` Jean-François Lessard
2025-08-20 16:31 ` [PATCH v3 3/4] auxdisplay: Add TM16xx 7-segment LED matrix display controllers driver Jean-François Lessard
2025-08-21 7:43 ` Krzysztof Kozlowski
2025-08-21 16:42 ` Jean-François Lessard
2025-08-21 8:08 ` Andy Shevchenko
2025-08-21 19:04 ` Jean-François Lessard
2025-08-21 20:19 ` Andy Shevchenko
2025-08-22 2:20 ` Jean-François Lessard
2025-08-22 6:08 ` Andy Shevchenko
2025-08-22 13:50 ` Jean-François Lessard
2025-08-27 5:32 ` kernel test robot
2025-08-20 16:31 ` [PATCH v3 4/4] MAINTAINERS: Add entry for TM16xx driver Jean-François Lessard
2025-08-20 19:08 ` Andy Shevchenko
2025-08-20 19:51 ` Conor Dooley
2025-08-20 20:29 ` Andy Shevchenko
2025-08-21 17:40 ` Conor Dooley
2025-08-21 19:33 ` Andy Shevchenko
2025-08-21 19:35 ` Andy Shevchenko
2025-08-21 20:11 ` Conor Dooley
2025-08-21 20:23 ` Andy Shevchenko
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=68ff2e14-19db-4d4c-8390-8fd2ec9e2c48@kernel.org \
--to=krzk@kernel.org \
--cc=afaerber@suse.de \
--cc=andy@kernel.org \
--cc=boris.gjenero@gmail.com \
--cc=christianshewitt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hkallweit1@gmail.com \
--cc=jefflessard3@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=paolo.sabatino@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).