From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-msm@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: cpufreq: cpufreq-qcom-hw: Document SM8350 CPUfreq compatible
Date: Thu, 18 Feb 2021 10:11:58 -0600 [thread overview]
Message-ID: <20210218161158.GC5254@yoga> (raw)
In-Reply-To: <20210216111251.1838149-1-vkoul@kernel.org>
On Tue 16 Feb 05:12 CST 2021, Vinod Koul wrote:
> Add the CPUfreq compatible for SM8350 SoC along with note for using the
> specific compatible for SoCs
>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> ---
> Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
> index 9299028ee712..3eb3cee59d79 100644
> --- a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
> +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt
> @@ -8,7 +8,9 @@ Properties:
> - compatible
> Usage: required
> Value type: <string>
> - Definition: must be "qcom,cpufreq-hw" or "qcom,cpufreq-epss".
> + Definition: must be "qcom,cpufreq-hw" or "qcom,cpufreq-epss"
> + along with SoC specific compatible:
> + "qcom,sm8350-cpufreq-epss", "qcom,cpufreq-epss"
Can you please extend this to add all the platforms that we currently
support?
PS. Didn't we have someone working on converting this to yaml?
Regards,
Bjorn
>
> - clocks
> Usage: required
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-02-18 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 11:12 [PATCH] dt-bindings: cpufreq: cpufreq-qcom-hw: Document SM8350 CPUfreq compatible Vinod Koul
2021-02-17 4:49 ` Viresh Kumar
2021-02-18 12:44 ` Vinod Koul
2021-02-18 15:48 ` Viresh Kumar
2021-03-05 21:57 ` Rob Herring
2021-03-08 4:56 ` Vinod Koul
2021-02-18 16:11 ` Bjorn Andersson [this message]
2021-02-19 17:59 ` Vinod Koul
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=20210218161158.GC5254@yoga \
--to=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).