From: sricharan@codeaurora.org (Sricharan R)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 15/15] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu
Date: Tue, 6 Mar 2018 10:45:04 +0530 [thread overview]
Message-ID: <a8d40af2-8a9e-8868-93fa-dbdec20a437e@codeaurora.org> (raw)
In-Reply-To: <20180305221936.yu2mlcjodlcumedx@rob-hp-laptop>
On 3/6/2018 3:49 AM, Rob Herring wrote:
> On Tue, Feb 27, 2018 at 07:37:02PM +0530, 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
>
> Reviewed-by: Rob Herring <robh@kernel.org>
Thanks Rob !!
Will post with all tags and the Makefile corrected.
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-03-06 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 14:06 [PATCH v8 00/15] Krait clocks + Krait CPUfreq Sricharan R
2018-02-27 14:06 ` [PATCH v8 01/15] ARM: Add Krait L2 register accessor functions Sricharan R
2018-02-27 14:06 ` [PATCH v8 02/15] clk: mux: Split out register accessors for reuse Sricharan R
2018-02-27 14:06 ` [PATCH v8 03/15] clk: qcom: Add support for High-Frequency PLLs (HFPLLs) Sricharan R
2018-02-27 14:06 ` [PATCH v8 04/15] clk: qcom: Add HFPLL driver Sricharan R
2018-02-27 14:06 ` [PATCH v8 05/15] dt-bindings: clock: Document qcom,hfpll Sricharan R
2018-02-27 14:06 ` [PATCH v8 06/15] clk: qcom: Add MSM8960/APQ8064's HFPLLs Sricharan R
2018-02-27 14:06 ` [PATCH v8 07/15] clk: qcom: Add IPQ806X's HFPLLs Sricharan R
2018-02-27 14:06 ` [PATCH v8 08/15] clk: qcom: Add support for Krait clocks Sricharan R
2018-02-27 14:06 ` [PATCH v8 09/15] clk: qcom: Add KPSS ACC/GCC driver Sricharan R
2018-02-27 14:06 ` [PATCH v8 10/15] dt-bindings: arm: Document qcom,kpss-gcc Sricharan R
2018-02-27 14:06 ` [PATCH v8 11/15] clk: qcom: Add Krait clock controller driver Sricharan R
2018-02-27 14:06 ` [PATCH v8 12/15] dt-bindings: clock: Document qcom,krait-cc Sricharan R
2018-02-27 14:07 ` [PATCH v8 13/15] clk: qcom: Add safe switch hook for krait mux clocks Sricharan R
2018-02-27 14:07 ` [PATCH v8 14/15] cpufreq: Add module to register cpufreq on Krait CPUs Sricharan R
2018-02-27 14:58 ` Gregory CLEMENT
2018-02-28 5:34 ` Sricharan R
2018-02-27 14:07 ` [PATCH v8 15/15] dt-bindings: cpufreq: Document operating-points-v2-krait-cpu Sricharan R
2018-03-05 22:19 ` Rob Herring
2018-03-06 5:15 ` Sricharan R [this message]
2018-03-01 13:28 ` [PATCH v8 00/15] Krait clocks + Krait CPUfreq Linus Walleij
2018-03-02 14:12 ` 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=a8d40af2-8a9e-8868-93fa-dbdec20a437e@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).