From: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
To: Rob Herring <robh@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH 2/3] regulator: dt-bindings: qcom,smd-rpm: Add PM8909
Date: Mon, 27 Jun 2022 16:07:39 +0200 [thread overview]
Message-ID: <Yrm5q/2giqUDd0oa@kernkonzept.com> (raw)
In-Reply-To: <1656091594.427255.146351.nullmailer@robh.at.kernel.org>
On Fri, Jun 24, 2022 at 11:26:34AM -0600, Rob Herring wrote:
> On Thu, 23 Jun 2022 11:46:13 +0200, Stephan Gerhold wrote:
> > Document the "qcom,rpm-pm8909-regulators" compatible for describing
> > the regulators available in the PM8909 PMIC (controlled via the RPM
> > firmware).
> >
> > PM8909 is very similar to the existing PM8916 but lacks 3 of the
> > regulators (s3, s4 and l16).
> >
> > Signed-off-by: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
> > ---
> > .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.yaml | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
>
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
>
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
>
> Full log is available here: https://patchwork.ozlabs.org/patch/
>
>
> pm8994-regulators: 'vdd_lvs1_2' does not match any of the regexes: '.*-supply$', '^((s|l|lvs|5vs)[0-9]*)|(boost-bypass)|(bob)$', 'pinctrl-[0-9]+'
> arch/arm64/boot/dts/qcom/msm8992-lg-bullhead-rev-101.dtb
> arch/arm64/boot/dts/qcom/msm8992-lg-bullhead-rev-10.dtb
> arch/arm64/boot/dts/qcom/msm8992-xiaomi-libra.dtb
>
Thanks for the (automated) report, Rob! :)
The failure is unrelated to my patch. It seems to be a simple typo in
the device tree (not a mistake in the DT schema) so I posted a quick fix
in a separate patch:
https://lore.kernel.org/linux-arm-msm/20220627135938.2901871-1-stephan.gerhold@kernkonzept.com/
It should land separately through the Qualcomm tree so no need to wait
for it to be applied. :)
Thanks,
Stephan
next prev parent reply other threads:[~2022-06-27 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 9:46 [PATCH 0/3] regulator: qcom_smd: Add PM8909 and fix pm8916_pldo range Stephan Gerhold
2022-06-23 9:46 ` [PATCH 1/3] regulator: qcom_smd: Fix " Stephan Gerhold
2022-06-23 9:46 ` [PATCH 2/3] regulator: dt-bindings: qcom,smd-rpm: Add PM8909 Stephan Gerhold
2022-06-23 13:28 ` Krzysztof Kozlowski
2022-06-24 17:26 ` Rob Herring
2022-06-27 14:07 ` Stephan Gerhold [this message]
2022-06-23 9:46 ` [PATCH 3/3] regulator: qcom_smd: Add PM8909 RPM regulators Stephan Gerhold
2022-06-23 13:26 ` Krzysztof Kozlowski
2022-06-23 13:27 ` Krzysztof Kozlowski
2022-06-30 13:32 ` [PATCH 0/3] regulator: qcom_smd: Add PM8909 and fix pm8916_pldo range Mark Brown
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=Yrm5q/2giqUDd0oa@kernkonzept.com \
--to=stephan.gerhold@kernkonzept.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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