From: Rob Herring <robh@kernel.org>
To: Nam Tran <trannamatk@gmail.com>
Cc: lee@kernel.org, gregkh@linuxfoundation.org, pavel@kernel.org,
rdunlap@infradead.org, christophe.jaillet@wanadoo.fr,
krzk+dt@kernel.org, conor+dt@kernel.org, corbet@lwn.net,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v19 1/3] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver
Date: Thu, 4 Dec 2025 12:49:44 -0600 [thread overview]
Message-ID: <20251204184944.GA1972172-robh@kernel.org> (raw)
In-Reply-To: <20251203164033.363984-1-trannamatk@gmail.com>
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@kernel.org>
> > > Signed-off-by: Nam Tran <trannamatk@gmail.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@c263000: 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@c263000: 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@c265000: 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@c265000: 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@c263000: 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@c263000: 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@c265000: 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@c265000: 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
next prev parent reply other threads:[~2025-12-04 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 15:39 [PATCH v19 0/3] leds: add new LED driver for TI LP5812 Nam Tran
2025-11-30 15:39 ` [PATCH v19 1/3] dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver Nam Tran
2025-11-30 16:16 ` Rob Herring (Arm)
2025-12-03 16:40 ` Nam Tran
2025-12-04 18:49 ` Rob Herring [this message]
2025-11-30 15:39 ` [PATCH v19 2/3] leds: add basic support for " Nam Tran
2025-11-30 15:39 ` [PATCH v19 3/3] docs: leds: Document TI LP5812 LED driver Nam Tran
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=20251204184944.GA1972172-robh@kernel.org \
--to=robh@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rdunlap@infradead.org \
--cc=trannamatk@gmail.com \
/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).