From: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: Shawn Guo <shawn.guo@linaro.org>, Kevin Hilman <khilman@ti.com>,
Nishanth Menon <nm@ti.com>,
linux-pm@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
cpufreq@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Richard Zhao <richard.zhao@freescale.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] cpufreq: Add a generic cpufreq-cpu0 driver
Date: Sat, 21 Jul 2012 10:34:29 +0530 [thread overview]
Message-ID: <CAMQu2gy4p+rL-sDAsGCnqSn_2eXwSqf---OS0BSXuDoacjd6_g@mail.gmail.com> (raw)
In-Reply-To: <CAJOA=zMQKLTumW7Nx68+yxHC5Yk4QyiL2mf1+TSZfVOAtnXDWA@mail.gmail.com>
On Fri, Jul 20, 2012 at 9:20 PM, Turquette, Mike <mturquette@ti.com> wrote:
> On Fri, Jul 20, 2012 at 5:33 AM, Shawn Guo <shawn.guo@linaro.org> wrote:
>> On Fri, Jul 20, 2012 at 12:22:14PM +0530, Shilimkar, Santosh wrote:
>>> This *_CPU0 doesn't seems to be appropriate since this infrastructure will be
>>> used on SMP systems where CPUs shares clock/voltage rails. May be you can
>>> get rid of that unless there is a strong need.
>>>
>> All the resource handlers, clk, regulator, opp, DT node, are retrieved
>> from CPU0 device even for SMP. I hope the naming of the driver could
>> tell:
>>
>> - The driver supports UP
>> - The driver supports SMP where CPUs shares clock/voltage rails by
>> managing CPU0 (resource)
>> - The driver does not support SMP where individual CPU can scale
>> clock/voltage independently.
>>
>
> How about cpufreq-single-thread.c and CONFIG_CPUFREQ_SINGLE_THREAD?
> That makes sense for both UP and SMP.
>
Indeed. This sounds more appropriate and also reflects what actually happens
with a UP or shared clock SMP case.
Regards
Santosh
next prev parent reply other threads:[~2012-07-21 5:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 15:54 [PATCH 0/3] Add a generic cpufreq-cpu0 driver Shawn Guo
2012-07-19 15:54 ` [PATCH 1/3] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Shawn Guo
2012-07-20 6:36 ` Shilimkar, Santosh
2012-07-20 7:56 ` Shawn Guo
2012-07-20 8:27 ` Shilimkar, Santosh
2012-07-19 15:54 ` [PATCH 2/3] PM / OPP: Initialize OPP table from device tree Shawn Guo
2012-07-20 6:00 ` Menon, Nishanth
2012-07-20 8:46 ` Shawn Guo
2012-07-20 9:04 ` Menon, Nishanth
2012-07-19 15:54 ` [PATCH 3/3] cpufreq: Add a generic cpufreq-cpu0 driver Shawn Guo
2012-07-20 6:52 ` Shilimkar, Santosh
[not found] ` <CAMQu2gw32LogXJJa+K5ZjmCZzBNK3FY2wYwZXU8fsftsVzEO2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-20 12:33 ` Shawn Guo
2012-07-20 15:50 ` Turquette, Mike
2012-07-21 5:04 ` Shilimkar, Santosh [this message]
2012-07-21 6:38 ` Shawn Guo
2012-07-27 2:04 ` Richard Zhao
2012-07-30 4:57 ` Shawn Guo
2012-07-20 12:51 ` Richard Zhao
2012-07-20 13:15 ` Shawn Guo
[not found] ` <1342713281-31114-4-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-07-26 13:11 ` Mark Brown
[not found] ` <20120726131121.GB7306-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-07-27 2:13 ` Richard Zhao
2012-07-27 10:08 ` Mark Brown
2012-07-30 6:52 ` Shawn Guo
2012-07-30 8:20 ` Shawn Guo
2012-07-30 18:55 ` Mark Brown
2012-07-30 18:53 ` Mark Brown
2012-07-31 4:20 ` Shawn Guo
2012-07-31 13:40 ` Mark Brown
2012-07-27 6:33 ` Richard Zhao
2012-07-30 8:17 ` Shawn Guo
2012-07-30 8:50 ` Richard Zhao
2012-07-30 9:24 ` Shawn Guo
2012-07-19 18:39 ` [PATCH 0/3] " Rafael J. Wysocki
2012-07-20 0:29 ` Shawn Guo
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=CAMQu2gy4p+rL-sDAsGCnqSn_2eXwSqf---OS0BSXuDoacjd6_g@mail.gmail.com \
--to=santosh.shilimkar@ti.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@ti.com \
--cc=nm@ti.com \
--cc=richard.zhao@freescale.com \
--cc=rjw@sisk.pl \
--cc=shawn.guo@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).