linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	sboyd@codeaurora.org, prarit@redhat.com, skannan@codeaurora.org,
	Srivatsa Bhat <srivatsa@mit.edu>
Subject: [PATCH V6 10/14] cpufreq: Remove cpufreq_update_policy()
Date: Sat, 23 May 2015 10:04:50 +0530	[thread overview]
Message-ID: <20150523043450.GB4210@linux> (raw)
In-Reply-To: <59ebb79018c6a4d86623614fe3e44a6de8592c6c.1431924457.git.viresh.kumar@linaro.org>

Don't know how two subject lines got in (maybe due to blank line
after/before subject line in my patch). Sorry about that.

On 23-05-15, 09:15, Viresh Kumar wrote:
> cpufreq_update_policy() was kept as a separate routine earlier as it was
> handling migration of sysfs directories, which isn't done anymore. It is
> only updating policy->cpu now and can be removed.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> V5->V6:
> - Merged v4 9/14, into this one after some updates.
> - Keep separate routines to add/remove symlinks.
> 
>  drivers/cpufreq/cpufreq.c | 32 ++++++++++----------------------
>  1 file changed, 10 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 663a934259a4..a791fe6920dc 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -1126,6 +1126,10 @@ static struct cpufreq_policy *cpufreq_policy_restore(unsigned int cpu)
>  	if (likely(policy)) {
>  		/* Policy should be inactive here */
>  		WARN_ON(!policy_is_inactive(policy));
> +
> +		down_write(&policy->rwsem);
> +		policy->cpu = cpu;
> +		up_write(&policy->rwsem);
>  	}
>  
>  	return policy;
> @@ -1210,16 +1214,6 @@ static void cpufreq_policy_free(struct cpufreq_policy *policy)
>  	kfree(policy);
>  }
>  
> -static void update_policy_cpu(struct cpufreq_policy *policy, unsigned int cpu)
> -{
> -	if (WARN_ON(cpu == policy->cpu))
> -		return;
> -
> -	down_write(&policy->rwsem);
> -	policy->cpu = cpu;
> -	up_write(&policy->rwsem);
> -}
> -
>  /**
>   * cpufreq_add_dev - add a CPU device
>   *
> @@ -1278,15 +1272,6 @@ static int cpufreq_add_dev(struct device *dev, struct subsys_interface *sif)
>  			goto nomem_out;
>  	}
>  
> -	/*
> -	 * In the resume path, since we restore a saved policy, the assignment
> -	 * to policy->cpu is like an update of the existing policy, rather than
> -	 * the creation of a brand new one. So we need to perform this update
> -	 * by invoking update_policy_cpu().
> -	 */
> -	if (recover_policy && cpu != policy->cpu)
> -		update_policy_cpu(policy, cpu);
> -
>  	cpumask_copy(policy->cpus, cpumask_of(cpu));
>  
>  	/* call driver. From then on the cpufreq must be able
> @@ -1467,11 +1452,14 @@ static int __cpufreq_remove_dev_prepare(struct device *dev,
>  	if (cpu != policy->cpu)
>  		return 0;
>  
> -	if (cpus > 1)
> +	if (cpus > 1) {
>  		/* Nominate new CPU */
> -		update_policy_cpu(policy, cpumask_any_but(policy->cpus, cpu));
> -	else if (cpufreq_driver->stop_cpu)
> +		down_write(&policy->rwsem);
> +		policy->cpu = cpumask_any_but(policy->cpus, cpu);
> +		up_write(&policy->rwsem);
> +	} else if (cpufreq_driver->stop_cpu) {
>  		cpufreq_driver->stop_cpu(policy);
> +	}
>  
>  	return 0;
>  }
> -- 
> 2.4.0

-- 
viresh

  reply	other threads:[~2015-05-23  4:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  5:13 [PATCH V5 00/14] cpufreq: Don't loose cpufreq history on CPU hotplug Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 01/14] cpufreq: Create for_each_{in}active_policy() Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 02/14] cpufreq: Don't clear cpufreq_cpu_data and policy list for inactive policies Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 03/14] cpufreq: Get rid of cpufreq_cpu_data_fallback Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 04/14] cpufreq: Don't traverse all active policies to find policy for a cpu Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 05/14] cpufreq: Manage governor usage history with 'policy->last_governor' Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 06/14] cpufreq: Mark policy->governor = NULL for inactive policies Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 07/14] cpufreq: Don't allow updating inactive policies from sysfs Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 08/14] cpufreq: Track cpu managing sysfs kobjects separately Viresh Kumar
2015-05-22 23:29   ` Rafael J. Wysocki
2015-05-18  5:13 ` [PATCH V5 09/14] cpufreq: add/remove sysfs links via cpufreq_add_remove_dev_symlink() Viresh Kumar
2015-05-22 23:28   ` Rafael J. Wysocki
2015-05-23  3:41     ` Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 10/14] cpufreq: Stop migrating sysfs files on hotplug Viresh Kumar
2015-05-23  3:45   ` (unknown), Viresh Kumar
2015-05-23  4:34     ` Viresh Kumar [this message]
2015-05-18  5:13 ` [PATCH V5 11/14] cpufreq: Remove cpufreq_update_policy() Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 12/14] cpufreq: Initialize policy->kobj while allocating policy Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 13/14] cpufreq: Call cpufreq_policy_put_kobj() from cpufreq_policy_free() Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 14/14] cpufreq: Restart governor as soon as possible Viresh Kumar
2015-05-19  0:34 ` [PATCH V5 00/14] cpufreq: Don't loose cpufreq history on CPU hotplug Rafael J. Wysocki
2015-05-19  2:27   ` 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=20150523043450.GB4210@linux \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=skannan@codeaurora.org \
    --cc=srivatsa@mit.edu \
    /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).