From: Sricharan R <sricharan@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux@armlinux.org.uk, andy.gross@linaro.org,
david.brown@linaro.org, rjw@rjwysocki.net,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-pm@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v6 15/15] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu
Date: Tue, 6 Feb 2018 10:14:29 +0530 [thread overview]
Message-ID: <d21cf85e-def9-66d8-aed1-cd1407c36fdb@codeaurora.org> (raw)
In-Reply-To: <20180206042729.GH28462@vireshk-i7>
Hi Viresh,
On 2/6/2018 9:57 AM, Viresh Kumar wrote:
> On 06-02-18, 09:38, Sricharan R wrote:
>> In Certain QCOM SoCs like ipq8064, apq8064, msm8960, msm8974
>> that has KRAIT processors the voltage/current value of each OPP
>> varies based on the silicon variant in use.
>> operating-points-v2-krait-cpu specifies the phandle to nvmem efuse cells
>> and the operating-points-v2 table for each opp. The qcom-cpufreq driver
>> reads the efuse value from the SoC to provide the required information
>> that is used to determine the voltage and current value for each OPP of
>> operating-points-v2 table when it is parsed by the OPP framework.
>>
>> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
>> ---
>> .../devicetree/bindings/cpufreq/krait-cpufreq.txt | 363 +++++++++++++++++++++
>> 1 file changed, 363 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/cpufreq/krait-cpufreq.txt
>
> You can add my Ack if Rob also finds everything to be fine here.
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks !!
Regards,
Sricharan
--
"QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2018-02-06 4:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 4:08 [PATCH v6 00/15] [v6] Krait clocks + Krait CPUfreq Sricharan R
2018-02-06 4:08 ` [PATCH v6 02/15] clk: mux: Split out register accessors for reuse Sricharan R
2018-02-06 4:08 ` [PATCH v6 03/15] clk: qcom: Add support for High-Frequency PLLs (HFPLLs) Sricharan R
2018-02-06 4:08 ` [PATCH v6 04/15] clk: qcom: Add HFPLL driver Sricharan R
2018-02-06 4:08 ` [PATCH v6 05/15] dt-bindings: clock: Document qcom,hfpll Sricharan R
2018-02-06 4:08 ` [PATCH v6 06/15] clk: qcom: Add MSM8960/APQ8064's HFPLLs Sricharan R
2018-02-06 4:08 ` [PATCH v6 07/15] clk: qcom: Add IPQ806X's HFPLLs Sricharan R
2018-02-06 4:08 ` [PATCH v6 08/15] clk: qcom: Add support for Krait clocks Sricharan R
2018-02-06 4:08 ` [PATCH v6 09/15] clk: qcom: Add KPSS ACC/GCC driver Sricharan R
2018-02-06 4:08 ` [PATCH v6 10/15] dt-bindings: arm: Document qcom,kpss-gcc Sricharan R
[not found] ` <1517890108-8140-1-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-02-06 4:08 ` [PATCH v6 01/15] ARM: Add Krait L2 register accessor functions Sricharan R
2018-02-06 4:08 ` [PATCH v6 11/15] clk: qcom: Add Krait clock controller driver Sricharan R
2018-02-06 4:08 ` [PATCH v6 12/15] dt-bindings: clock: Document qcom,krait-cc Sricharan R
2018-02-06 4:08 ` [PATCH v6 13/15] clk: qcom: Add safe switch hook for krait mux clocks Sricharan R
2018-02-06 4:08 ` [PATCH v6 14/15] cpufreq: Add module to register cpufreq on Krait CPUs Sricharan R
2018-02-06 4:26 ` Viresh Kumar
2018-02-06 4:43 ` Sricharan R
2018-02-06 4:08 ` [PATCH v6 15/15] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu Sricharan R
2018-02-06 4:27 ` Viresh Kumar
2018-02-06 4:44 ` Sricharan R [this message]
2018-02-09 2:54 ` Rob Herring
2018-02-09 5:31 ` Sricharan R
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=d21cf85e-def9-66d8-aed1-cd1407c36fdb@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).