From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Thomas Abraham <thomas.ab@samsung.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
t.figa@samsung.com, l.majewski@samsung.com,
viresh.kumar@linaro.org, nm@ti.com,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v6 0/2] cpufreq: opp: Add device tree based lookup of boost mode frequency
Date: Fri, 30 May 2014 16:47:15 +0200 [thread overview]
Message-ID: <1430270.VsBiDfiUL9@vostro.rjw.lan> (raw)
In-Reply-To: <5683009.PqtetcWKuO@vostro.rjw.lan>
On Friday, May 30, 2014 02:19:06 PM Rafael J. Wysocki wrote:
> On Friday, May 30, 2014 02:31:15 PM Thomas Abraham wrote:
> > Changes since v5:
> > - Fixes for checkpatch warnings with --strict option as suggested by
> > Nishanth Menon.
> >
> > Changes since v4:
> > - Code improvements suggested by Viresh Kumar.
> >
> > Changes since v3:
> > - Minor changes as suggested in the last version.
> >
> > Changes since v2:
> > - Reworked based on the "PM / OPP: move cpufreq specific helpers out of OPP
> > layer" patch series posted by Nishanth Menon.
> >
> > 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.
> >
> > This series has been acked by authors and maintainers of the code
> > portions changed in this series. The new DT binding introduced in this
> > patch needs an ack from device tree binding maintainers as well.
> >
> > 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.
>
> Both patches queued up for 3.16 in the linux-pm tree.
But please address the Mark's comments or I'll drop them.
Rafael
next prev parent reply other threads:[~2014-05-30 14:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 9:01 [PATCH v6 0/2] cpufreq: opp: Add device tree based lookup of boost mode frequency Thomas Abraham
2014-05-30 9:01 ` [PATCH v6 1/2] cpufreq / OPP: Allow boost frequency to be looked up from device tree Thomas Abraham
2014-05-30 9:01 ` [PATCH v6 2/2] Documentation: devicetree: Add boost-frequency binding to list boost mode frequency Thomas Abraham
2014-05-30 13:08 ` Mark Rutland
2014-05-30 18:05 ` Thomas Abraham
2014-05-30 18:15 ` Tomasz Figa
2014-05-30 18:33 ` Thomas Abraham
2014-05-30 18:35 ` Tomasz Figa
2014-05-30 18:38 ` Sudeep Holla
2014-05-30 18:41 ` Tomasz Figa
2014-05-30 18:48 ` Sudeep Holla
2014-05-30 18:55 ` Mark Rutland
2014-05-30 19:50 ` Nishanth Menon
2014-05-30 20:02 ` Tomasz Figa
2014-05-30 20:13 ` Nishanth Menon
2014-05-30 20:19 ` Tomasz Figa
2014-05-30 20:33 ` Nishanth Menon
2014-05-30 20:43 ` Tomasz Figa
2014-05-30 21:01 ` Nishanth Menon
2014-05-30 20:45 ` Rob Herring
2014-05-30 20:59 ` Nishanth Menon
2014-05-30 12:19 ` [PATCH v6 0/2] cpufreq: opp: Add device tree based lookup of " Rafael J. Wysocki
2014-05-30 14:47 ` Rafael J. Wysocki [this message]
2014-05-30 18:07 ` Thomas Abraham
2014-05-30 21:17 ` Rafael J. Wysocki
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=1430270.VsBiDfiUL9@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--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=mark.rutland@arm.com \
--cc=nm@ti.com \
--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