From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Escala, Edelweise" <Edelweise.Escala@analog.com>
Cc: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: leds: Document LTC3220 18 channel LED Driver
Date: Wed, 7 Jan 2026 11:57:39 +0100 [thread overview]
Message-ID: <2d1893a8-81eb-4d7e-81df-060722c10c7d@kernel.org> (raw)
In-Reply-To: <PH0PR03MB6525F2AB63E24564356ADE51ED84A@PH0PR03MB6525.namprd03.prod.outlook.com>
On 07/01/2026 10:52, Escala, Edelweise wrote:
>>
>>> +
>>> + adi,force-cpo-level:
>>> + $ref: /schemas/types.yaml#/definitions/string
>>> + description: Forces the Charge Pump Output to a specified multiplier.
>>> + enum:
>>> + - "0" # Auto(default) - Automatically selects optimal charge pump mode
>>> + - "1.5"
>>> + - "2"
>>> + - "1"
>>
>> Numbers are not a string, so choose appropriate number format. Also, oddly
>> sorted. I don't understand what this property is for so not sure what to
>> recommend.
>
> It is arranged this way to match the value for the register.
Makes no sense. The order here does not matter for driver and registers
at all.
> I plan to keep it as string and just do
> enum:
> - auto
> - 1.5x
> - 2x
> - 1x
Still wrongly ordered and still I do not understand the purpose of this
property.
Datasheet mentions some sort of impedance. Impedance has units (see
property units in dtschema), but you call it "level". Maybe you want to
achieve some specific current on output? But for current we already have
LED related properties.
Also, "auto" is redundant unless lack of the property has a meaning?
Why exactly this varies between boards?
>
>>
>>> + default: "0"
>>> +
>>> + adi,quick-write:
>>> + type: boolean
>>> + description: If present, LED 1 output becomes a master control that
>>> + simultaneously updates all 18 LED outputs using the hardware's quick-
>> write
>>> + mode. When enabled, led@1 must be defined in the device tree to
>> provide
>>> + the control interface, even if no physical LED is connected to the D1
>>> + output pin. When disabled or not present, LED 1 operates as a normal
>>> + independent LED output.
>>
>> If there is no led@1 physically, you cannot add it to the DT. It seems you
>> described some sort of driver behavior, instead of hardware.
>>
>
> This is also a hardware feature, when enabled a write to the LED 1
> output register simultaneously updates all 18 LED output registers
> to the same value.
You still cannot add fake nodes to DT. Fake means there is no actual LED.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-07 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 5:27 [PATCH 0/2] Add Support for LTC3220 18 Channel " Edelweise Escala
2026-01-06 5:27 ` [PATCH 1/2] dt-bindings: leds: Document LTC3220 18 channel " Edelweise Escala
2026-01-06 8:12 ` Krzysztof Kozlowski
2026-01-07 9:52 ` Escala, Edelweise
2026-01-07 10:57 ` Krzysztof Kozlowski [this message]
2026-01-08 6:02 ` Escala, Edelweise
2026-01-06 5:27 ` [PATCH 2/2] leds: ltc3220: add driver Edelweise Escala
2026-01-06 8:14 ` Krzysztof Kozlowski
2026-01-07 9:52 ` Escala, Edelweise
2026-01-06 12:03 ` Jacek Anaszewski
2026-01-07 9:52 ` Escala, Edelweise
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=2d1893a8-81eb-4d7e-81df-060722c10c7d@kernel.org \
--to=krzk@kernel.org \
--cc=Edelweise.Escala@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@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
all inboxes | Powered by JetHome®