[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171211083905.GF25177@vireshk-i7>
Date: Mon, 11 Dec 2017 14:09:05 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sricharan R <sricharan@...eaurora.org>
Cc: mturquette@...libre.com, sboyd@...eaurora.org,
devicetree@...r.kernel.org, linux-pm@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 11/12] cpufreq: Add module to register cpufreq on
Krait CPUs
On 08-12-17, 15:12, Sricharan R wrote:
> From: Stephen Boyd <sboyd@...eaurora.org>
>
> Register a cpufreq-generic device whenever we detect that a
> "qcom,krait" compatible CPU is present in DT.
>
> Cc: <devicetree@...r.kernel.org>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> ---
> .../devicetree/bindings/arm/msm/qcom,pvs.txt | 38 ++++
> drivers/cpufreq/Kconfig.arm | 9 +
> drivers/cpufreq/Makefile | 1 +
> drivers/cpufreq/qcom-cpufreq.c | 204 +++++++++++++++++++++
> 4 files changed, 252 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/msm/qcom,pvs.txt
> create mode 100644 drivers/cpufreq/qcom-cpufreq.c
This must be done differently as we have enhanced OPP core to support such
hardware. Look at: dev_pm_opp_set_prop_name() and the binding around it
(opp-microvolt-<name>). Talk to Stephen, he was part of all those discussions.
--
viresh
Powered by blists - more mailing lists