From: Sricharan R <sricharan@codeaurora.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: viresh.kumar@linaro.org, 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,
linux@arm.linux.org.uk
Subject: Re: [PATCH v8 14/15] cpufreq: Add module to register cpufreq on Krait CPUs
Date: Wed, 28 Feb 2018 11:04:26 +0530 [thread overview]
Message-ID: <95e134a6-7992-e16f-dc55-df7af96b31b9@codeaurora.org> (raw)
In-Reply-To: <87zi3ujx7c.fsf@bootlin.com>
Hi Gregory,
On 2/27/2018 8:28 PM, Gregory CLEMENT wrote:
> Hi Sricharan,
>
> On mar., févr. 27 2018, Sricharan R <sricharan@codeaurora.org> wrote:
>
>> From: Stephen Boyd <sboyd@codeaurora.org>
>>
>> Register a cpufreq-generic device whenever we detect that a
>> "qcom,krait" compatible CPU is present in DT.
>>
>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>> [Sricharan: updated to use dev_pm_opp_set_prop_name and
>> nvmem apis]
>> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>> ---
>> drivers/cpufreq/Kconfig.arm | 10 ++
>> drivers/cpufreq/Makefile | 3 +
>> drivers/cpufreq/cpufreq-dt-platdev.c | 5 +
>> drivers/cpufreq/qcom-cpufreq.c | 183 +++++++++++++++++++++++++++++++++++
>> 4 files changed, 201 insertions(+)
>> create mode 100644 drivers/cpufreq/qcom-cpufreq.c
>>
>> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
>> index 3a88e33..826f9e7 100644
>> --- a/drivers/cpufreq/Kconfig.arm
>> +++ b/drivers/cpufreq/Kconfig.arm
>> @@ -133,6 +133,16 @@ config ARM_OMAP2PLUS_CPUFREQ
>> depends on ARCH_OMAP2PLUS
>> default ARCH_OMAP2PLUS
>>
>> +config ARM_QCOM_CPUFREQ
>> + bool "CPUfreq driver for the QCOM SoCs with KRAIT processors"
>> + depends on ARCH_QCOM
>> + select PM_OPP
>> + help
>> + This enables the CPUFreq driver for Qualcomm SoCs with
>> + KRAIT processors.
>> +
>> + If in doubt, say N.
>> +
>> config ARM_S3C_CPUFREQ
>> bool
>> help
>> diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile
>> index c60c1e1..21894f6 100644
>> --- a/drivers/cpufreq/Makefile
>> +++ b/drivers/cpufreq/Makefile
>> @@ -65,6 +65,9 @@ obj-$(CONFIG_MACH_MVEBU_V7) += mvebu-cpufreq.o
>> obj-$(CONFIG_ARM_OMAP2PLUS_CPUFREQ) += omap-cpufreq.o
>> obj-$(CONFIG_ARM_PXA2xx_CPUFREQ) += pxa2xx-cpufreq.o
>> obj-$(CONFIG_PXA3xx) += pxa3xx-cpufreq.o
>> +obj-$(CONFIG_ARM_QCOM_CPUFREQ) += qcom-cpufreq.o
>
> These 2 following lines don't seem related to the commit log:
>> +obj-$(CONFIG_ARM_S3C24XX_CPUFREQ) += s3c24xx-cpufreq.o
>> +obj-$(CONFIG_ARM_S3C24XX_CPUFREQ_DEBUGFS) += s3c24xx-cpufreq-debugfs.o
>
oops. Will remove. Rebase mistake. 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-28 5:34 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 [this message]
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
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=95e134a6-7992-e16f-dc55-df7af96b31b9@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--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@arm.linux.org.uk \
--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).