From: Nishanth Menon <nm@ti.com>
To: cpufreq <cpufreq@vger.kernel.org>
Cc: Nishanth Menon <nm@ti.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Shawn Guo <shawn.guo@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: [PATCH 0/2] cpufreq: cpufreq-cpu0: cleanups around DT usage
Date: Mon, 11 Mar 2013 18:05:28 -0500 [thread overview]
Message-ID: <1363043130-30270-1-git-send-email-nm@ti.com> (raw)
The following series arose from trying to use BeagleBoard-XM (OMAP3 variant)
for doing CPU DVFS using cpufreq-cpu0.
This is also an attempt to slowly remove the dependence on omap-cpufreq
driver and be entirely driven off cpufreq-cpu0 driver.
Somewhere in the future, when we have regulators driven off CCF and OMAP
converted to CCF, we could remove the DT regulator requirements as well.
Based on v3.9-rc2 tag
Nishanth Menon (2):
cpufreq: cpufreq-cpu0: support for clock which are not in DT yet.
cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup
.../devicetree/bindings/cpufreq/cpufreq-cpu0.txt | 6 ++++++
drivers/cpufreq/cpufreq-cpu0.c | 12 +++++++++++-
2 files changed, 17 insertions(+), 1 deletion(-)
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-kernel@vger.kernel.org
Cc: cpufreq@vger.kernel.org
Cc: linux-pm@vger.kernel.org
Cc: linux-omap@vger.kernel.org
This series in addition to the following DT changes (temporary):
http://pastebin.com/h5uysj0i
Screen shot of the voltage changes using cpufreq-cpu0 on Xm:
http://goo.gl/vVEjd
OMAP Caveat: AVS+ABB still wont work with just these changes.
More to come as we progress.
--
1.7.9.5
Regards,
Nishanth Menon
next reply other threads:[~2013-03-11 23:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 23:05 Nishanth Menon [this message]
2013-03-11 23:05 ` [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which are not in DT yet Nishanth Menon
2013-03-12 5:03 ` Santosh Shilimkar
2013-03-12 5:03 ` Santosh Shilimkar
2013-03-12 14:24 ` Benoit Cousson
2013-03-12 14:24 ` Benoit Cousson
2013-03-12 14:35 ` Nishanth Menon
2013-03-12 14:35 ` Nishanth Menon
2013-03-12 15:17 ` J, KEERTHY
2013-03-12 15:51 ` Nishanth Menon
2013-03-12 7:36 ` Shawn Guo
2013-03-12 7:36 ` Shawn Guo
2013-03-11 23:05 ` [PATCH 2/2] cpufreq: cpufreq-cpu0: provide compatibility string for DT matchup Nishanth Menon
2013-03-12 5:07 ` Santosh Shilimkar
2013-03-12 5:07 ` Santosh Shilimkar
2013-03-12 14:28 ` Benoit Cousson
2013-03-12 14:28 ` Benoit Cousson
2013-03-12 14:35 ` Santosh Shilimkar
2013-03-12 14:35 ` Santosh Shilimkar
2013-03-12 14:43 ` Nishanth Menon
2013-03-12 14:43 ` Nishanth Menon
2013-03-12 15:31 ` Benoit Cousson
2013-03-12 15:31 ` Benoit Cousson
2013-03-12 7:57 ` Shawn Guo
2013-03-12 7:57 ` Shawn Guo
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=1363043130-30270-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.