public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lan Tianyu <tianyu.lan@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Cpufreq: Remove fossil comment of cpufreq_set_policy
Date: Wed, 11 Sep 2013 11:28:41 +0800	[thread overview]
Message-ID: <522FE369.3030106@intel.com> (raw)
In-Reply-To: <CAKohponpX9AedBrsASojK7fKS-rRN-AQwJT42=mrOJcNpGqE+w@mail.gmail.com>

On 2013年09月10日 23:31, Viresh Kumar wrote:
> On 10 September 2013 20:14,  <tianyu.lan@intel.com> wrote:
>> From: Lan Tianyu <tianyu.lan@intel.com>
>>
>> The cpufreq_set_policy() has been removed by commit 632786c. So remove
>> related comment.
>> ---
>>  drivers/cpufreq/cpufreq.c | 4 ----
>>  1 file changed, 4 deletions(-)
> 
> I have got another patch that takes care of this while fixing other issues..
> Yet to be posted though.. but I have queued it up for 3.13..
> 
> https://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=commit;h=85267596078e3160b3b03de39d95c8e4b5bdf554
> 
Ok. I get it. Please ignore it. I just find another such comment related
with cpufreq_set_policy(). Please have a look.


From 668e1b6fd94b5c0e56a651b4c60cbbc7a6868b46 Mon Sep 17 00:00:00 2001
From: Lan Tianyu <tianyu.lan@intel.com>
Date: Wed, 11 Sep 2013 11:31:15 +0800
Subject: [PATCH] Cpufreq/governor: Remove fossil comment

cpufreq_set_policy() has been changed to origin __cpufreq_set_policy()
and policy->lock has been converted to rewrite lock by commit 5a01f2.
So remove it.

Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
---
 drivers/cpufreq/cpufreq_userspace.c | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/drivers/cpufreq/cpufreq_userspace.c
b/drivers/cpufreq/cpufreq_userspace.c
index 0307809..4dbf1db 100644
--- a/drivers/cpufreq/cpufreq_userspace.c
+++ b/drivers/cpufreq/cpufreq_userspace.c
@@ -38,18 +38,7 @@ static int cpufreq_set(struct cpufreq_policy *policy,
unsigned int freq)
        if (!per_cpu(cpu_is_managed, policy->cpu))
                goto err;

-       /*
-        * We're safe from concurrent calls to ->target() here
-        * as we hold the userspace_mutex lock. If we were calling
-        * cpufreq_driver_target, a deadlock situation might occur:
-        * A: cpufreq_set (lock userspace_mutex) ->
-        *      cpufreq_driver_target(lock policy->lock)
-        * B: cpufreq_set_policy(lock policy->lock) ->
-        *      __cpufreq_governor ->
-        *         cpufreq_governor_userspace (lock userspace_mutex)
-        */
        ret = __cpufreq_driver_target(policy, freq, CPUFREQ_RELATION_L);
-
  err:
        mutex_unlock(&userspace_mutex);
        return ret;
--
1.8.4.rc0.1.g8f6a3e5.dirty

-- 
Best regards
Tianyu Lan

  reply	other threads:[~2013-09-11  3:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 14:44 [PATCH 1/1] Cpufreq: Remove fossil comment of cpufreq_set_policy tianyu.lan
2013-09-10 15:31 ` Viresh Kumar
2013-09-11  3:28   ` Lan Tianyu [this message]
2013-09-11 10:08     ` Viresh Kumar
2013-09-11 12:39       ` Lan Tianyu

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=522FE369.3030106@intel.com \
    --to=tianyu.lan@intel.com \
    --cc=cpufreq@vger.kernel.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