From: Rob Herring <robh@kernel.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: andersson@kernel.org, linux-pwm@vger.kernel.org, pavel@ucw.cz,
linux-arm-msm@vger.kernel.org, u.kleine-koenig@pengutronix.de,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, linux-leds@vger.kernel.org,
lee@kernel.org, agross@kernel.org
Subject: Re: [PATCH 2/7] dt-bindings: leds: leds-qcom-lpg: Add support for LUT through NVMEM devices
Date: Wed, 21 Jun 2023 13:36:57 -0600 [thread overview]
Message-ID: <168737621786.3403563.13933135215667889399.robh@kernel.org> (raw)
In-Reply-To: <20230621185949.2068-3-quic_amelende@quicinc.com>
On Wed, 21 Jun 2023 11:59:46 -0700, Anjelique Melendez wrote:
> Update leds-qcom-lpg bindings to support LUT patterns through NVMEM
> devices.
>
> Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
> ---
> .../bindings/leds/leds-qcom-lpg.yaml | 85 +++++++++++++++++++
> 1 file changed, 85 insertions(+)
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/leds/leds-qcom-lpg.example.dtb: /example-4/led-controller: failed to match any schema with compatible: ['qcom,pmi632-lpg']
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230621185949.2068-3-quic_amelende@quicinc.com
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.
next prev parent reply other threads:[~2023-06-21 19:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 18:59 [PATCH 0/7] Add support for LUT PPG Anjelique Melendez
2023-06-21 18:59 ` [PATCH 1/7] dt-bindings: soc: qcom: Add qcom-pbs bindings Anjelique Melendez
2023-06-21 19:36 ` Rob Herring
2023-06-24 9:38 ` Krzysztof Kozlowski
2023-06-26 13:58 ` Rob Herring
2023-06-29 1:19 ` Anjelique Melendez
2023-06-29 8:45 ` Dmitry Baryshkov
2023-06-29 21:53 ` Anjelique Melendez
2023-06-29 23:58 ` Dmitry Baryshkov
2023-07-01 11:03 ` Krzysztof Kozlowski
2023-07-11 3:52 ` Anjelique Melendez
2023-07-11 5:58 ` Krzysztof Kozlowski
2023-07-11 20:12 ` Anjelique Melendez
2023-07-12 14:22 ` Krzysztof Kozlowski
2023-07-12 14:35 ` Dmitry Baryshkov
2023-07-12 20:11 ` Krzysztof Kozlowski
2023-07-14 20:32 ` Anjelique Melendez
2023-07-17 7:36 ` Krzysztof Kozlowski
2023-06-21 18:59 ` [PATCH 2/7] dt-bindings: leds: leds-qcom-lpg: Add support for LUT through NVMEM devices Anjelique Melendez
2023-06-21 19:36 ` Rob Herring [this message]
2023-06-24 9:42 ` Krzysztof Kozlowski
2023-06-29 0:12 ` Anjelique Melendez
2023-07-01 11:01 ` Krzysztof Kozlowski
2023-06-21 18:59 ` [PATCH 3/7] soc: qcom: add QCOM PBS driver Anjelique Melendez
2023-06-24 9:55 ` Krzysztof Kozlowski
2023-06-24 10:01 ` Krzysztof Kozlowski
2023-06-29 0:48 ` Anjelique Melendez
2023-06-21 18:59 ` [PATCH 4/7] leds: rgb: leds-qcom-lpg: Add support for LUT pattern through single SDAM Anjelique Melendez
2023-06-21 18:59 ` [PATCH 5/7] leds: rgb: leds-qcom-lpg: Update PMI632 lpg_data to support PPG Anjelique Melendez
2023-06-21 18:59 ` [PATCH 6/7] leds: rgb: leds-qcom-lpg: Support two-nvmem PPG Scheme Anjelique Melendez
2023-06-21 18:59 ` [PATCH 7/7] leds: rgb: Update PM8350C lpg_data to support " Anjelique Melendez
2023-06-26 8:28 ` [PATCH 0/7] Add support for LUT PPG Luca Weiss
2023-07-25 19:33 ` Anjelique Melendez
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=168737621786.3403563.13933135215667889399.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=quic_amelende@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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