From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
ilia.lin@kernel.org, agross@kernel.org, rafael@kernel.org,
viresh.kumar@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, stephan@gerhold.net
Cc: linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: opp: opp-v2-kryo-cpu: Fix example binding checks
Date: Mon, 11 Jul 2022 13:44:05 +0200 [thread overview]
Message-ID: <ceb5130e-a3e7-bfb2-a782-f6773a0af4f6@linaro.org> (raw)
In-Reply-To: <20220708121156.2165250-2-bryan.odonoghue@linaro.org>
On 08/07/2022 14:11, Bryan O'Donoghue wrote:
> Adding missing compat entries to the cpufreq node
> Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml shows up
> a dt_binding_check in this file.
>
> opp-v2-kryo-cpu.example.dtb: /: cpus:cpu@0: 'power-domains' is a required property
> opp-v2-kryo-cpu.example.dtb: /: cpus:cpu@0: 'power-domain-names' is a required property
> opp-v2-kryo-cpu.example.dtb: /: opp-table-0:opp-307200000: 'required-opps' is a required property
>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-11 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 12:11 [PATCH v3 0/3] msm8939 cpufreq preparatory work Bryan O'Donoghue
2022-07-08 12:11 ` [PATCH v3 1/3] dt-bindings: opp: opp-v2-kryo-cpu: Fix example binding checks Bryan O'Donoghue
2022-07-11 11:44 ` Krzysztof Kozlowski [this message]
2022-07-08 12:11 ` [PATCH v3 2/3] dt-bindings: opp: Add missing compat devices Bryan O'Donoghue
2022-07-08 12:11 ` [PATCH v3 3/3] dt-bindings: opp: Add msm8939 to the compatible list Bryan O'Donoghue
2022-07-11 0:48 ` [PATCH v3 0/3] msm8939 cpufreq preparatory work Viresh Kumar
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=ceb5130e-a3e7-bfb2-a782-f6773a0af4f6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).