From: Amit Kucheria <amit.kucheria@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, Borislav Petkov <bp@alien8.de>,
Steve Bannister <Steve.Bannister@arm.com>,
Lists linaro-dev <linaro-dev@lists.linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org,
Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
Subject: Re: [PATCH 0/4] CPUFreq: Implement per policy instances of governors
Date: Wed, 6 Feb 2013 15:38:49 +0530 [thread overview]
Message-ID: <CAP245DUMnSMSoXo2JoMu1CgNROQ2YT7kd7e9svWoZ_EG2QLi+Q@mail.gmail.com> (raw)
In-Reply-To: <CAKohpokFCAqdoeBoMJ3Jzh05x8wUg4kfo+XirxUjw=2_4_0wJA@mail.gmail.com>
On Wed, Feb 6, 2013 at 3:28 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 5 February 2013 21:51, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>> commit 15b5548c9ccfb8088270f7574710d9d67edfe33b
>> Author: Viresh Kumar <viresh.kumar@linaro.org>
>> Date: Tue Feb 5 21:29:05 2013 +0530
>>
>> cpufreq: Make governors directory sysfs location based on
>> have_multiple_policies
>>
>> Until now directory for governors tunables was getting created in
>> cpu/cpufreq/<gov-name>. With the introduction of following patch:
>> "cpufreq: governor: Implement per policy instances of governors"
>>
>> this directory would be created in
>> cpu/cpu<num>/cpufreq/<gov-name>. This might
>> break userspace of existing platforms. Lets do this change only
>> for platforms
>> which need support for multiple policies and thus above mentioned patch.
>>
>> From now on, such platforms would be require to do following from
>> their init()
>> routines:
>>
>> policy->have_multiple_policies = true;
>>
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>> ---
>> drivers/cpufreq/cpufreq_governor.c | 2 +-
>> include/linux/cpufreq.h | 14 ++++++++++++++
>> 2 files changed, 15 insertions(+), 1 deletion(-)
>
> Hi Rafael,
>
> Because this patch was quite big (317 insertions(+), 238 deletions(-)), i was
> planning a detailed self review to capture any mistakes and luckily i found
> one for above patch :)
>
> diff --git a/drivers/cpufreq/cpufreq_governor.c
> b/drivers/cpufreq/cpufreq_governor.c
> index 41ee86f..fe037c0 100644
> --- a/drivers/cpufreq/cpufreq_governor.c
> +++ b/drivers/cpufreq/cpufreq_governor.c
> @@ -342,7 +342,8 @@ int cpufreq_governor_dbs(struct cpufreq_policy *policy,
> mutex_lock(&dbs_data->mutex);
> mutex_destroy(&cpu_cdbs->timer_mutex);
>
> - sysfs_remove_group(&policy->kobj, dbs_data->cdata->attr_group);
> + sysfs_remove_group(get_governor_parent_kobj(policy),
> + dbs_data->cdata->attr_group);
> if (dbs_data->cdata->governor == GOV_CONSERVATIVE)
> cpufreq_unregister_notifier(cs_ops->notifier_block,
> CPUFREQ_TRANSITION_NOTIFIER);
>
> I have pushed the complete patchset here:
>
> http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/cpufreq-updates
>
Viresh, perhaps you should ask Stephen Rothwell to pull in your tree
to get some more testing before Rafael pulls it in for 3.10?
next prev parent reply other threads:[~2013-02-06 10:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 11:38 [PATCH 0/4] CPUFreq: Implement per policy instances of governors Viresh Kumar
[not found] ` <cover.1359976493.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-04 11:38 ` [PATCH 1/4] cpufreq: Don't check cpu_online(policy->cpu) Viresh Kumar
2013-02-04 11:38 ` [PATCH 2/4] cpufreq: stats: Get rid of CPUFREQ_STATDEVICE_ATTR Viresh Kumar
2013-02-04 11:38 ` [PATCH 3/4] cpufreq: Add per policy governor-init/exit infrastructure Viresh Kumar
2013-02-04 11:38 ` [PATCH 4/4] cpufreq: governor: Implement per policy instances of governors Viresh Kumar
2013-02-10 21:14 ` Francesco Lavra
2013-02-11 4:16 ` Viresh Kumar
2013-02-11 4:39 ` Viresh Kumar
2013-02-04 12:17 ` [PATCH 0/4] CPUFreq: " Rafael J. Wysocki
2013-02-04 12:24 ` Viresh Kumar
2013-02-04 12:32 ` Borislav Petkov
2013-02-04 12:54 ` Viresh Kumar
2013-02-04 13:04 ` Borislav Petkov
2013-02-04 13:25 ` Viresh Kumar
2013-02-04 13:36 ` Borislav Petkov
2013-02-04 13:58 ` Viresh Kumar
2013-02-04 14:09 ` Borislav Petkov
2013-02-04 14:21 ` Viresh Kumar
2013-02-04 15:05 ` Borislav Petkov
2013-02-04 15:37 ` Viresh Kumar
2013-02-04 16:50 ` Borislav Petkov
2013-02-05 7:20 ` Viresh Kumar
2013-02-05 9:15 ` Borislav Petkov
[not found] ` <20130205091532.GA4827-fF5Pk5pvG8Y@public.gmane.org>
2013-02-05 9:47 ` Viresh Kumar
2013-02-05 10:27 ` Borislav Petkov
2013-02-05 10:43 ` Viresh Kumar
2013-02-05 11:04 ` Borislav Petkov
2013-02-05 11:12 ` Viresh Kumar
2013-02-05 11:19 ` Borislav Petkov
2013-02-05 11:26 ` Viresh Kumar
2013-02-05 11:32 ` Borislav Petkov
2013-02-05 12:24 ` Viresh Kumar
2013-02-05 13:22 ` Borislav Petkov
2013-02-05 13:55 ` Viresh Kumar
2013-02-05 9:36 ` Viresh Kumar
[not found] ` <CAKohpokejWugM+wP5xcqp0F9AggLxuEf9Ox5fDViMxJh1c+kEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 11:29 ` Charles Garcia-Tobin
2013-02-05 11:39 ` Borislav Petkov
2013-02-05 18:38 ` Charles Garcia-Tobin
2013-02-05 18:44 ` Borislav Petkov
2013-02-05 16:21 ` Viresh Kumar
2013-02-06 9:58 ` Viresh Kumar
2013-02-06 10:08 ` Amit Kucheria [this message]
2013-02-06 10:15 ` Viresh Kumar
2013-02-06 10:38 ` 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=CAP245DUMnSMSoXo2JoMu1CgNROQ2YT7kd7e9svWoZ_EG2QLi+Q@mail.gmail.com \
--to=amit.kucheria@linaro.org \
--cc=Charles.Garcia-Tobin@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=bp@alien8.de \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--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).