linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linuxppc-dev@ozlabs.org,
	"ego@linux.vnet.ibm.com" <ego@linux.vnet.ibm.com>,
	Anton Blanchard <anton@samba.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v3 1/5] powernv: cpufreq driver for powernv platform
Date: Fri, 21 Mar 2014 17:10:11 +0530	[thread overview]
Message-ID: <532C251B.1020306@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAKohpo=JqHOPF_pdcAsvRgc1vENmS=Sg9pS8ZXPGhfMFnA8ZUA@mail.gmail.com>

On 03/21/2014 04:24 PM, Viresh Kumar wrote:
> On 21 March 2014 16:13, Gautham R Shenoy <ego@linux.vnet.ibm.com> wrote:
>> On Fri, Mar 21, 2014 at 02:11:32PM +0530, Viresh Kumar wrote:
> 
>>>> +               pr_debug("PState id %d freq %d MHz\n", id, freq);
>>>> +               powernv_freqs[i].driver_data = i;
>>>
[...] 
>>>> +static int powernv_cpufreq_cpu_init(struct cpufreq_policy *policy)
>>>> +{
>>>> +       int base, i;
>>>> +
>>>> +#ifdef CONFIG_SMP
>>>
>>> What will break if you don't have this ifdef here? Without that as well
>>> below code should work?
> 
> Missed this one?
> 

Nothing will break, its just that the code size will be a tiny bit
lesser on UP configs, that's all :-) Anyway, I think removing the ifdef
improves the readability (and doesn't add any noticeable overhead on UP
kernels), so let's get rid of it.

Regards,
Srivatsa S. Bhat

>>>> +       base = cpu_first_thread_sibling(policy->cpu);
>>>> +
>>>> +       for (i = 0; i < threads_per_core; i++)
>>>> +               cpumask_set_cpu(base + i, policy->cpus);
>>>> +#endif
>>>> +       policy->cpuinfo.transition_latency = 25000;
>>>> +
>>>> +       policy->cur = powernv_freqs[0].frequency;
>>>> +       cpufreq_frequency_table_get_attr(powernv_freqs, policy->cpu);
>>>

  reply	other threads:[~2014-03-21 11:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 12:10 [PATCH v3 0/5] powernv: Enable Dynamic Frequency Gautham R. Shenoy
2014-03-20 12:10 ` [PATCH v3 1/5] powernv: cpufreq driver for powernv platform Gautham R. Shenoy
2014-03-21  8:41   ` Viresh Kumar
2014-03-21 10:43     ` Gautham R Shenoy
2014-03-21 10:54       ` Viresh Kumar
2014-03-21 11:40         ` Srivatsa S. Bhat [this message]
2014-03-21 13:23         ` Gautham R Shenoy
2014-03-21 13:34           ` Viresh Kumar
2014-03-21 14:54         ` Gautham R Shenoy
2014-03-22  3:43           ` Viresh Kumar
2014-03-21 14:48       ` Vaidyanathan Srinivasan
2014-03-22  3:43         ` Viresh Kumar
2014-03-21 11:45     ` Srivatsa S. Bhat
2014-03-21 11:47       ` Viresh Kumar
2014-03-20 12:10 ` [PATCH v3 2/5] powernv, cpufreq:Add per-core locking to serialize frequency transitions Gautham R. Shenoy
2014-03-21  6:24   ` Gautham R Shenoy
2014-03-21  8:42   ` Viresh Kumar
2014-03-21  9:56     ` Srivatsa S. Bhat
2014-03-20 12:10 ` [PATCH v3 3/5] powernv:cpufreq: Create pstate_id_to_freq() helper Gautham R. Shenoy
2014-03-21  6:24   ` Gautham R Shenoy
2014-03-20 12:10 ` [PATCH v3 4/5] powernv:cpufreq: Export nominal frequency via sysfs Gautham R. Shenoy
2014-03-21  8:47   ` Viresh Kumar
2014-03-21  9:55     ` Gautham R Shenoy
2014-03-21  9:57       ` Viresh Kumar
2014-03-20 12:11 ` [PATCH v3 5/5] powernv:cpufreq: Implement the driver->get() method Gautham R. Shenoy
2014-03-21  6:25   ` Gautham R Shenoy
2014-03-21  9:31   ` Viresh Kumar
2014-03-21 11:04     ` Gautham R Shenoy
2014-03-21 11:45       ` Viresh Kumar
2014-03-21 12:01         ` David Laight
2014-03-21 12:31           ` Gautham R Shenoy
2014-03-21 12:34           ` Viresh Kumar
2014-03-21 15:01             ` David Laight
2014-03-21 13:04         ` Gautham R Shenoy
2014-03-21 13:12           ` Viresh Kumar
2014-03-21 14:25             ` Gautham R Shenoy
2014-03-21 22:56       ` Benjamin Herrenschmidt
2014-03-22  7:53         ` Gautham R Shenoy
2014-03-21  7:46 ` [PATCH v3 0/5] powernv: Enable Dynamic Frequency Viresh Kumar
2014-03-21  8:19   ` Gautham R Shenoy

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=532C251B.1020306@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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).