From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-dev@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
rjw@sisk.pl, Steve.Bannister@arm.com,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
Date: Fri, 1 Feb 2013 14:22:07 +0530 [thread overview]
Message-ID: <510B8237.7030605@ti.com> (raw)
In-Reply-To: <CAKohpomxi91kXR+th2BbruKigmLPmrDQf1s_Mf11C3Bs53aB3A@mail.gmail.com>
On Friday 01 February 2013 01:32 PM, Viresh Kumar wrote:
> On 1 February 2013 13:03, Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
>> I am not talking about just notifiers. This is for external users who
>> has subscribed for notifiers. The point is whether the core CPUFReq
>> gets updated without that flag for all affected CPU.
>
> Yes, its safe. Follow this thread, yesterday i explained this to Tomasz Figa:
>
> http://www.spinics.net/lists/arm-kernel/msg221629.html
>
That part was very clear to me Viresh. Anyway thanks for the link.
From what I read so far, it might just work but I would want to
try it out before acking the approach.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <linaro-dev@lists.linaro.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <cpufreq@vger.kernel.org>,
<rjw@sisk.pl>, <Steve.Bannister@arm.com>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type
Date: Fri, 1 Feb 2013 14:22:07 +0530 [thread overview]
Message-ID: <510B8237.7030605@ti.com> (raw)
In-Reply-To: <CAKohpomxi91kXR+th2BbruKigmLPmrDQf1s_Mf11C3Bs53aB3A@mail.gmail.com>
On Friday 01 February 2013 01:32 PM, Viresh Kumar wrote:
> On 1 February 2013 13:03, Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
>> I am not talking about just notifiers. This is for external users who
>> has subscribed for notifiers. The point is whether the core CPUFReq
>> gets updated without that flag for all affected CPU.
>
> Yes, its safe. Follow this thread, yesterday i explained this to Tomasz Figa:
>
> http://www.spinics.net/lists/arm-kernel/msg221629.html
>
That part was very clear to me Viresh. Anyway thanks for the link.
From what I read so far, it might just work but I would want to
try it out before acking the approach.
Regards,
Santosh
next prev parent reply other threads:[~2013-02-01 8:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 6:40 [PATCH 1/3] cpufreq: TEGRA: Set policy->cpus from driver->init() Viresh Kumar
[not found] ` <1bf82454ab1f16b13212548d7c9605067c8b7a0d.1359700705.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-01 6:40 ` [PATCH 2/3] cpufreq: Set all cpus in policy->cpus for single cluster SoCs Viresh Kumar
2013-02-01 6:40 ` Viresh Kumar
2013-02-01 6:41 ` Viresh Kumar
2013-02-01 6:40 ` [PATCH 3/3] cpufreq: Remove unnecessary use of policy->shared_type Viresh Kumar
2013-02-01 6:40 ` Viresh Kumar
2013-02-01 6:41 ` Viresh Kumar
2013-02-01 6:47 ` Santosh Shilimkar
2013-02-01 6:47 ` Santosh Shilimkar
2013-02-01 7:13 ` Viresh Kumar
2013-02-01 7:33 ` Santosh Shilimkar
2013-02-01 7:33 ` Santosh Shilimkar
2013-02-01 8:02 ` Viresh Kumar
2013-02-01 8:52 ` Santosh Shilimkar [this message]
2013-02-01 8:52 ` Santosh Shilimkar
2013-02-01 9:07 ` Santosh Shilimkar
2013-02-01 9:07 ` Santosh Shilimkar
2013-02-01 6:41 ` [PATCH 1/3] cpufreq: TEGRA: Set policy->cpus from driver->init() Viresh Kumar
2013-02-04 16:36 ` Stephen Warren
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=510B8237.7030605@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=Steve.Bannister@arm.com \
--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=swarren@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.