From: Rob Herring <robh@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
krzysztof.kozlowski+dt@linaro.org, rafael@kernel.org,
johan@kernel.org, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, viresh.kumar@linaro.org,
robh+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: cpufreq: cpufreq-qcom-hw: Add cpufreq clock provider
Date: Thu, 20 Oct 2022 20:54:00 -0500 [thread overview]
Message-ID: <166631723974.2154081.10911150649507151378.robh@kernel.org> (raw)
In-Reply-To: <20221019135925.366162-3-manivannan.sadhasivam@linaro.org>
On Wed, 19 Oct 2022 19:29:23 +0530, Manivannan Sadhasivam wrote:
> Qualcomm platforms making use of CPUFreq HW Engine (EPSS/OSM) supply clocks
> to the CPU cores. Document the same in the binding to reflect the actual
> implementation.
>
> CPUFreq HW will become the clock provider and CPU cores will become the
> clock consumers.
>
> The clock index for each CPU core is based on the frequency domain index.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> .../devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-10-21 1:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 13:59 [PATCH 0/4] qcom-cpufreq-hw: Add CPU clock provider support Manivannan Sadhasivam
2022-10-19 13:59 ` [PATCH 1/4] cpufreq: qcom-hw: Remove un-necessary cpumask_empty() check Manivannan Sadhasivam
2022-10-19 13:59 ` [PATCH 2/4] dt-bindings: cpufreq: cpufreq-qcom-hw: Add cpufreq clock provider Manivannan Sadhasivam
2022-10-21 1:54 ` Rob Herring [this message]
2022-10-19 13:59 ` [PATCH 3/4] cpufreq: qcom-hw: Add CPU clock provider support Manivannan Sadhasivam
2022-10-20 5:39 ` Dmitry Baryshkov
2022-10-21 9:31 ` Manivannan Sadhasivam
2022-10-24 3:06 ` Bjorn Andersson
2022-10-24 4:01 ` Manivannan Sadhasivam
2022-10-19 13:59 ` [PATCH 4/4] arm64: dts: qcom: sm8450: Supply clock from cpufreq node to CPUs Manivannan Sadhasivam
2022-10-20 5:22 ` [PATCH 0/4] qcom-cpufreq-hw: Add CPU clock provider support Viresh Kumar
2022-10-21 8:02 ` Manivannan Sadhasivam
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=166631723974.2154081.10911150649507151378.robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®