From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 10/10] cpufreq-dt: Add support for operating-points-v2 bindings
Date: Thu, 09 Jul 2015 18:44:28 +0200 [thread overview]
Message-ID: <4945455.PmBrA0DySW@amdc1976> (raw)
In-Reply-To: <3095426.xc9msIINgb@amdc1976>
On Thursday, July 09, 2015 06:13:54 PM Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Monday, June 15, 2015 05:27:36 PM Viresh Kumar wrote:
> > Support for parsing operating-points-v2 bindings is in place now, lets
> > modify cpufreq-dt driver to use them.
>
> I believe that following patches:
>
> * [PATCH v2 1/7] opp: add dev_pm_opp_get_turbo_mode_setting() helper
> (http://lkml.org/lkml/2015/7/9/420)
>
> * [PATCH v2 2/7] cpufreq: opp: fix handling of turbo modes
> (http://lkml.org/lkml/2015/7/9/421)
>
> should be integrated into this patch series before patch #10 (the current
> one) can be applied.
>
> [ Please see http://lkml.org/lkml/2015/7/9/419 for more details. ]
On the 2nd thought here is the issue description, so people don't
have to search for it:
With the current code the turbo-mode opp-s are not distinguished in
any way in the cpufreq subsystem and once somebody defines them in
their DTS file they are treated as normal modes. I.e. if you define
opp-s using opp-v2 bindings in your DTS file (for use by cpufreq-dt
driver) and some are marked as turbo modes then the freq_table (build
by cpufreq core) will contain turbo mode frequencies and cpufreq-dt
driver will use them as normal frequencies. This is certainly not
a desired behavior.
To fix it I added opp core helper to check whether opp is a turbo
mode and during build of freq_table turbo mode frequencies are
marked with special flag (CPUFREQ_BOOST_FREQ). Such frequencies
are ignored by cpufreq core unless 'boost' mode is enabled.
'boost' mode support needs to be explicitly supported & enabled in
a specific cpufreq driver. For the moment it is only available for
Exynos4x12 cpufreq driver but my patchset (converting Exynos4x12
platforms to use cpufreq-dt driver) makes it available for use in
cpufreq-dt (to be enabled from your platform support when needed).
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2015-07-09 16:44 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 11:57 [PATCH 00/10] OPP: Add code to support operating-points-v2 bindings Viresh Kumar
2015-06-15 11:57 ` [PATCH 01/10] opp: Relocate few routines Viresh Kumar
2015-07-02 1:25 ` Stephen Boyd
2015-07-24 17:08 ` Bartlomiej Zolnierkiewicz
2015-06-15 11:57 ` [PATCH 02/10] OPP: Create _remove_device_opp() for freeing dev_opp Viresh Kumar
2015-07-02 1:25 ` Stephen Boyd
2015-07-24 17:13 ` Bartlomiej Zolnierkiewicz
2015-06-15 11:57 ` [PATCH 03/10] OPP: Allocate dev_opp from _add_device_opp() Viresh Kumar
2015-07-02 1:02 ` Stephen Boyd
2015-07-02 6:24 ` Viresh Kumar
2015-07-02 23:46 ` Stephen Boyd
2015-07-03 6:45 ` Viresh Kumar
2015-07-06 22:31 ` Stephen Boyd
2015-07-24 17:25 ` Bartlomiej Zolnierkiewicz
2015-06-15 11:57 ` [PATCH 04/10] OPP: Break _opp_add_dynamic() into smaller functions Viresh Kumar
2015-07-24 17:42 ` Bartlomiej Zolnierkiewicz
2015-06-15 11:57 ` [PATCH 05/10] opp: Add support to parse "operating-points-v2" bindings Viresh Kumar
2015-07-02 1:13 ` Stephen Boyd
2015-07-02 6:38 ` Viresh Kumar
2015-07-02 16:07 ` Stephen Boyd
2015-07-03 6:08 ` Viresh Kumar
2015-07-08 13:41 ` Bartlomiej Zolnierkiewicz
2015-07-09 5:18 ` Viresh Kumar
2015-07-24 18:02 ` Bartlomiej Zolnierkiewicz
2015-07-27 3:14 ` Viresh Kumar
2015-07-27 3:02 ` Viresh Kumar
2015-07-28 23:03 ` Stephen Boyd
2015-07-29 6:53 ` Viresh Kumar
2015-07-30 10:17 ` Viresh Kumar
2015-06-15 11:57 ` [PATCH 06/10] OPP: Add clock-latency-ns support Viresh Kumar
2015-07-02 1:27 ` Stephen Boyd
2015-06-15 11:57 ` [PATCH 07/10] opp: Add OPP sharing information to OPP library Viresh Kumar
2015-07-17 22:51 ` Stephen Boyd
2015-07-18 6:33 ` Viresh Kumar
2015-07-20 17:46 ` Stephen Boyd
2015-07-21 2:18 ` Viresh Kumar
2015-07-27 3:20 ` Viresh Kumar
2015-06-15 11:57 ` [PATCH 08/10] OPP: Add support for opp-suspend Viresh Kumar
2015-07-17 19:22 ` Stephen Boyd
2015-07-18 6:32 ` Viresh Kumar
2015-06-15 11:57 ` [PATCH 09/10] opp: Add helpers for initializing CPU OPPs Viresh Kumar
2015-06-15 11:57 ` [PATCH 10/10] cpufreq-dt: Add support for operating-points-v2 bindings Viresh Kumar
2015-07-09 16:13 ` Bartlomiej Zolnierkiewicz
2015-07-09 16:44 ` Bartlomiej Zolnierkiewicz [this message]
2015-07-15 2:59 ` Viresh Kumar
2015-06-30 16:44 ` [PATCH 00/10] OPP: Add code to support " Viresh Kumar
2015-07-17 2:36 ` Viresh Kumar
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=4945455.PmBrA0DySW@amdc1976 \
--to=b.zolnierkie@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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).