From: Lan Tianyu <tianyu.lan@intel.com>
To: viresh kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"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>,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH V2] Cpufreq: Make governor data on nonboot cpus across system suspend/resume
Date: Fri, 22 Nov 2013 16:19:23 +0800 [thread overview]
Message-ID: <528F138B.1090107@intel.com> (raw)
In-Reply-To: <528F0C9E.8020409@linaro.org>
On 2013年11月22日 15:49, viresh kumar wrote:
> On Sunday 17 November 2013 09:43 AM, viresh kumar wrote:
>> On 16 November 2013 21:06, Lan Tianyu <tianyu.lan@intel.com> wrote:
>
>> But I don't really like the solution here. You are handling frozen for EXIT in
>> cpufreq-core and for INIT in governor. That doesn't look like the right
>> approach. There are out of tree governors too (I know we don't care about them
>> :)), and those also need to adapt with some policy made at cpufreq-core level.
>>
>> I told you that I had another solution for this problem, pretty similar to
>> yours. It looked like this:
>
> Hi Lan,
>
Hi Viresh:
> There is some confusion going on here :)
>
I think you also are in the Cc list and replied the mail.:)
https://lkml.org/lkml/2013/11/21/273
> There were few problems in the approach in your patch, which I have mentioned
> above, and Rafael agreed to them..
I only saw the out-of-tree governor issue your mentioned but where they
are? How upstream kernel cares them?
>
>> But after the PM notifiers patch I even don't want this to go.. I will make sure
>> that that patch goes in, in one form or another :)
>
> And I was still trying to get a better solution in place of these changes. And
> was going on the suggestions you gave about calling cpufreq callbacks from
> dpm_{suspend|resume}_noirq() calls.. And I am on my way to get things fixed that
> way. And so we don't actually need this patch anymore (I just saw that you have
> sent another version of it, probably because Rafael asked? Don't know what
> happened there :))..
>
> So, I will try to get something working soon for you and Nishanth..
>
--
Best regards
Tianyu Lan
next prev parent reply other threads:[~2013-11-22 8:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 6:01 [PATCH 1/1] Cpufreq: Make governor data on nonboot cpus across system syspend/resume Lan Tianyu
2013-11-15 8:15 ` [Update PATCH 1/1] Cpufreq: Make governor data on nonboot cpus across system suspend/resume Lan Tianyu
2013-11-15 10:22 ` Viresh Kumar
2013-11-16 4:33 ` Lan Tianyu
2013-11-15 10:54 ` Viresh Kumar
2013-11-16 5:24 ` viresh kumar
2013-11-16 0:38 ` Rafael J. Wysocki
2013-11-16 3:59 ` Lan Tianyu
2013-11-16 14:41 ` Rafael J. Wysocki
2013-11-16 14:57 ` Viresh Kumar
2013-11-16 15:10 ` Rafael J. Wysocki
2013-11-16 15:09 ` Rafael J. Wysocki
2013-11-16 15:23 ` Lan Tianyu
2013-11-16 15:36 ` [PATCH V2] " Lan Tianyu
2013-11-17 4:13 ` viresh kumar
2013-11-17 14:44 ` Rafael J. Wysocki
2013-11-17 16:23 ` Viresh Kumar
2013-11-22 7:49 ` viresh kumar
2013-11-22 8:19 ` Lan Tianyu [this message]
2013-11-22 8:39 ` Viresh Kumar
2013-11-21 14:43 ` Rafael J. Wysocki
2013-11-21 15:54 ` Viresh Kumar
2013-11-21 21:43 ` Rafael J. Wysocki
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=528F138B.1090107@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=nm@ti.com \
--cc=rjw@rjwysocki.net \
--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