[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251204184944.GA1972172-robh@kernel.org>
Date: Thu, 4 Dec 2025 12:49:44 -0600
From: Rob Herring <robh@...nel.org>
To: Nam Tran <trannamatk@...il.com>
Cc: lee@...nel.org, gregkh@...uxfoundation.org, pavel@...nel.org,
rdunlap@...radead.org, christophe.jaillet@...adoo.fr,
krzk+dt@...nel.org, conor+dt@...nel.org, corbet@....net,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH v19 1/3] dt-bindings: leds: add TI/National Semiconductor
LP5812 LED Driver
On Wed, Dec 03, 2025 at 11:40:33PM +0700, Nam Tran wrote:
> On Sun, 30 Nov 2025, Rob Herring (Arm) wrote:
>
> > On Sun, 30 Nov 2025 22:39:54 +0700, Nam Tran wrote:
> > > The LP5812 is a 4x3 RGB LED driver with an autonomous animation
> > > engine and time-cross-multiplexing (TCM) support for up to 12 LEDs
> > > or 4 RGB LEDs. It supports both analog (256 levels) and PWM (8-bit)
> > > dimming, including exponential PWM for smooth brightness control.
> > >
> > > Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
> > > Signed-off-by: Nam Tran <trannamatk@...il.com>
> > > ---
> > > .../devicetree/bindings/leds/ti,lp5812.yaml | 246 ++++++++++++++++++
> > > MAINTAINERS | 6 +
> > > 2 files changed, 252 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/leds/ti,lp5812.yaml
> > >
> >
> > My bot found errors running 'make dt_binding_check' on your patch:
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> > Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> > Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> >
> > doc reference errors (make refcheckdocs):
> >
> > See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20251130153956.241375-2-trannamatk@gmail.com
>
> Accessing the link results in a 404 error on my side, is it expected?
That's patchwork.kernel.org now.
> > The base for the series is generally the latest rc1. A different dependency
> > should be noted in *this* patch.
> >
> > If you already ran 'make dt_binding_check' and didn't see the above
> > error(s), then make sure 'yamllint' is installed and dt-schema is up to
> > date:
> >
> > pip3 install dtschema --upgrade
> >
> > Please check and re-submit after running the above command yourself. Note
> > that DT_SCHEMA_FILES can be set to your schema file to speed up checking
> > your schema. However, it must be unset to test all examples with your schema.
>
> The LP5812 binding validates correctly. The errors reported by the bot come
> from the unrelated thermal bindings. Is it normal for the bot to report these
> unrelated errors?
You can ignore the bot report, linux-next broke it over the holidays.
Rob
Powered by blists - more mailing lists