[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2c07fbb-fd80-48a4-b0da-2f8db057198a@kernel.org>
Date: Wed, 7 Jan 2026 15:11:55 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Barnabás Czémán <barnabas.czeman@...nlining.org>,
Lee Jones <lee@...nel.org>, Daniel Thompson <danielt@...nel.org>,
Jingoo Han <jingoohan1@...il.com>, Pavel Machek <pavel@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Bjorn Andersson <andersson@...nel.org>,
Kiran Gunda <quic_kgunda@...cinc.com>, Helge Deller <deller@....de>,
Luca Weiss <luca@...aweiss.eu>, Konrad Dybcio <konradybcio@...nel.org>,
Eugene Lepshy <fekz115@...il.com>, Gianluca Boiano <morf3089@...il.com>,
Alejandro Tafalla <atafalla@...on.com>
Cc: dri-devel@...ts.freedesktop.org, linux-leds@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Daniel Thompson <daniel.thompson@...aro.org>, linux-arm-msm@...r.kernel.org,
linux-fbdev@...r.kernel.org, Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Subject: Re: [PATCH 1/5] dt-bindings: backlight: qcom-wled: Document ovp
values for PMI8950
On 07/01/2026 14:31, Barnabás Czémán wrote:
> Document ovp values supported by wled found in PMI8950.
>
> Signed-off-by: Barnabás Czémán <barnabas.czeman@...nlining.org>
> ---
> .../bindings/leds/backlight/qcom-wled.yaml | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml b/Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml
> index a8490781011d..306fb6642617 100644
> --- a/Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml
> +++ b/Documentation/devicetree/bindings/leds/backlight/qcom-wled.yaml
> @@ -98,8 +98,6 @@ properties:
> description: |
> Over-voltage protection limit. This property is for WLED4 only.
> $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [ 18100, 19600, 29600, 31100 ]
minimum and maximum should stay here. Or alternatively enum with all the
values, but I think first options is enough.
Best regards,
Krzysztof
Powered by blists - more mailing lists