From: Thomas Abraham <ta.omasab@gmail.com>
To: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: rjw@rjwysocki.net, linux-samsung-soc@vger.kernel.org,
kgene.kim@samsung.com, t.figa@samsung.com,
l.majewski@samsung.com, viresh.kumar@linaro.org,
thomas.ab@samsung.com
Subject: [PATCH v2 0/2] Add device tree based lookup of boost mode frequency
Date: Fri, 7 Feb 2014 20:49:00 +0530 [thread overview]
Message-ID: <1391786342-11812-1-git-send-email-thomas.ab@samsung.com> (raw)
Changes since v1:
- Boost mode frequencies are specfied as a set of frequencies instead of
specifying them as OPPs. Thanks to Nishanth, Lukasz and Rob for the
feedback.
Commit 6f19efc0 ("cpufreq: Add boost frequency support in core") adds
support for CPU boost mode for CPUfreq drivers. To use the new boost
mode, CPUfreq drivers have to specify the boost mode frequency and
voltage within the CPUfreq driver, which is the case for Exynos4x12
CPUfreq driver.
But for CPUfreq drivers which obtain the OPPs from cpus node, this
patch series adds support to specify boost mode frequencies in the
cpu device tree node. This requirement came up when Lukasz pointed
out the regression caused by the Exynos CPUfreq driver consolidation
patches.
Thomas Abraham (2):
PM / OPP: Allow boost frequency to be looked up from device tree
Documentation: devicetree: Add boost-frequency binding to list boost mode frequency
.../devicetree/bindings/cpufreq/cpufreq-boost.txt | 11 +++++++
drivers/base/power/opp.c | 34 +++++++++++++++++++-
2 files changed, 44 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-boost.txt
next reply other threads:[~2014-02-07 15:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 15:19 Thomas Abraham [this message]
2014-02-07 15:19 ` [PATCH v2 1/2] PM / OPP: Allow boost frequency to be looked up from device tree Thomas Abraham
2014-02-07 15:29 ` Nishanth Menon
2014-02-07 15:38 ` Thomas Abraham
2014-02-07 15:52 ` Nishanth Menon
2014-02-07 16:01 ` Sudeep Holla
2014-02-08 5:10 ` Thomas Abraham
2014-02-10 7:10 ` Lukasz Majewski
2014-02-10 10:40 ` Sudeep Holla
2014-02-07 15:19 ` [PATCH v2 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency Thomas Abraham
2014-02-07 15:27 ` Nishanth Menon
2014-02-07 15:38 ` Thomas Abraham
2014-02-07 16:15 ` Sudeep Holla
2014-02-07 16:28 ` Sudeep Holla
2014-02-07 16:43 ` Nishanth Menon
2014-02-07 17:31 ` Sudeep Holla
2014-02-07 17:37 ` Nishanth Menon
2014-02-07 17:40 ` Nishanth Menon
2014-02-07 18:02 ` Sudeep Holla
2014-02-07 19:41 ` Nishanth Menon
2014-02-08 6:47 ` Thomas Abraham
2014-02-10 7:53 ` Lukasz Majewski
2014-02-10 11:20 ` Sudeep Holla
2014-02-08 6:47 ` Thomas Abraham
2014-02-10 7:38 ` Lukasz Majewski
2014-02-10 10:51 ` Sudeep Holla
2014-02-10 10:46 ` 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=1391786342-11812-1-git-send-email-thomas.ab@samsung.com \
--to=ta.omasab@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene.kim@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=t.figa@samsung.com \
--cc=thomas.ab@samsung.com \
--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