From: Jonghwan Choi <jhbird.choi@samsung.com>
To: "'Viresh Kumar'" <viresh.kumar@linaro.org>
Cc: "'Nishanth Menon'" <nm@ti.com>,
"'Linux PM list'" <linux-pm@vger.kernel.org>,
"'open list'" <linux-kernel@vger.kernel.org>,
"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
"'Len Brown'" <len.brown@intel.com>,
"'Amit Daniel Kachhap'" <amit.daniel@samsung.com>
Subject: RE: [PATCH 1/3] PM / OPP: Add support for descending order for cpufreq table
Date: Fri, 09 May 2014 10:09:37 +0900 [thread overview]
Message-ID: <000e01cf6b23$58fda900$0af8fb00$@samsung.com> (raw)
In-Reply-To: <CAKohponiuHYjLve5ywLSGtDPPFN9a54gzZUicn1m702B2Ct3Pw@mail.gmail.com>
On 8 May 2014 2:56 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> Not necessarily. People may need a multiplier as well or some other
> configuration and so this stuff was left for drivers to implement.
-> In exynos cpufreq driver, if we want to support more frequency, then
we have to describe frequency information in dts file and have to change exynos cpufreq
driver file also(For adding divider value).
But if dev_pm_opp has a divider value for DVFS,when we want to support more frequency
we have only to change the dts file.
I think that it is easy to maintain cpufreq driver and very convenient.
(Can be applied to devfreq)
This is a example (exynos4210 doesn't support DT.)
--- a/drivers/base/power/opp.c
+++ b/drivers/base/power/opp.c
@@ -64,6 +64,7 @@ struct dev_pm_opp {
bool available;
unsigned long rate;
unsigned long u_volt;
+ unsigned int ctl[2];
struct device_opp *dev_opp;
struct rcu_head head;
diff --git a/arch/arm/boot/dts/exynos4210.dtsi b/arch/arm/boot/dts/exynos4210.dtsi
index cacf614..007a411 100644
--- a/arch/arm/boot/dts/exynos4210.dtsi
+++ b/arch/arm/boot/dts/exynos4210.dtsi
@@ -81,6 +81,24 @@
interrupts = <2 2>, <3 2>;
};
+ cpufreq@160000 {
+ compatible = "samsung,exynos7842-cpufreq";
+ reg = <0x160000 0x1000>;
+ interrupts = <0 57 0>;
+ operating-points = <
+ /* KHz uV clkdiv0 clkdiv1 */
+ 1500000 1100000 0x11111 0x11111
+ 1400000 1075000 0x22223 0x22222
+ 1300000 1050000 0x33333 0x33333
+ 1200000 1025000 0x44444 0x44444
+ 1100000 1000000 0x55555 0x55555
+ 1000000 975000 0x66666 0x66666
+ 900000 950000 0x77777 0x77777
+ 800000 925000 0x88888 0x88888
+ >;
+ };
+
+
pinctrl_0: pinctrl@11400000 {
compatible = "samsung,exynos4210-pinctrl";
reg = <0x11400000 0x1000>;
Thanks
Best Regards.
next prev parent reply other threads:[~2014-05-09 1:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 6:28 [PATCH 1/3] PM / OPP: Add support for descending order for cpufreq table Jonghwan Choi
2014-04-30 8:25 ` Viresh Kumar
2014-05-03 0:16 ` Jonghwan Choi
2014-05-05 5:54 ` Viresh Kumar
2014-05-05 13:38 ` Nishanth Menon
2014-05-05 14:14 ` Viresh Kumar
2014-05-05 14:23 ` Nishanth Menon
2014-05-05 14:38 ` Viresh Kumar
2014-05-05 14:46 ` Nishanth Menon
2014-05-06 23:43 ` Jonghwan Choi
2014-05-07 1:00 ` Nishanth Menon
2014-05-07 6:04 ` Viresh Kumar
2014-05-08 1:22 ` Jonghwan Choi
2014-05-08 1:55 ` Nishanth Menon
2014-05-08 2:07 ` Jonghwan Choi
2014-05-08 5:55 ` Viresh Kumar
2014-05-09 1:09 ` Jonghwan Choi [this message]
2014-05-09 6:00 ` Viresh Kumar
2014-05-09 11:59 ` jonghwan Choi
2014-05-09 13:23 ` Nishanth Menon
2014-05-11 11:38 ` jonghwan Choi
2014-05-12 6:18 ` Viresh Kumar
2014-05-08 5:50 ` Viresh Kumar
2014-05-06 17:25 ` Sudeep Holla
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='000e01cf6b23$58fda900$0af8fb00$@samsung.com' \
--to=jhbird.choi@samsung.com \
--cc=amit.daniel@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--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).