linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Lan Tianyu <lantianyu1986@gmail.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	cpufreq@vger.kernel.org,
	"Linux PM list" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jarzmik, Robert" <robert.jarzmik@intel.com>,
	"R, Durgadoss" <durgadoss.r@intel.com>,
	"Dirk Brandewie" <dirk.brandewie@gmail.com>,
	tianyu.lan@intel.com
Subject: Re: [PATCH] cpufreq: Fix cpufreq regression after suspend/resume
Date: Thu, 11 Jul 2013 19:54:36 +0530	[thread overview]
Message-ID: <51DEC024.50603@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOLK0pyJ=MoE20adyg8oUP-bTiwvXobRNX4ayA5eGRH0UGbpgw@mail.gmail.com>

On 07/11/2013 07:33 PM, Lan Tianyu wrote:
> 2013/7/11 Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>:
 
>> I tried to address all these in this patch, but you found yet another serious
>> loop-hole. I guess I'm out of ideas now... if anybody has any thoughts on how
>> to get this right, then I'm all ears. Else, we'll just revert the original
>> commit like Rafael suggested and leave it upto userspace to save and restore
>> the permissions across suspend/resume if it wants ;-(
>>
> 
> How about implement scaling driver's suspend/resume callback()? Although this
> needs to be dealt with case by case. If one's callbacks hasn't been implemented,
> it would have to follow current rule.
> 

Well, I'm now trying a slightly different approach at reorganizing the code,
and so far I think I'll be able to get it right this time. Let's see how it goes.

Regards,
Srivatsa S. Bhat


  reply	other threads:[~2013-07-11 14:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51C08370.4050906@gmx.de>
     [not found] ` <CAKohpok1gThXL925Yz5UgC54vTVQgymBA1cLGER_g-dgZu0JLA@mail.gmail.com>
     [not found]   ` <51CF1E53.6060902@gmx.de>
     [not found]     ` <8029836.CFiJCXmRQ0@vostro.rjw.lan>
     [not found]       ` <51D05DF4.50704@linux.vnet.ibm.com>
     [not found]         ` <51D06556.7080204@gmx.de>
2013-06-30 18:52           ` [PATCH] cpufreq: Fix cpufreq regression after suspend/resume Srivatsa S. Bhat
2013-06-30 22:46             ` Rafael J. Wysocki
2013-07-10 20:50             ` Toralf Förster
2013-07-10 22:29               ` Srivatsa S. Bhat
2013-07-11  5:40                 ` Lan Tianyu
2013-07-11  6:23                   ` Srivatsa S. Bhat
2013-07-11 14:03                     ` Lan Tianyu
2013-07-11 14:24                       ` Srivatsa S. Bhat [this message]
2013-07-11 14:23                     ` Alan Stern
2013-07-11 14:38                       ` Srivatsa S. Bhat
2013-07-13 10:16               ` Paul Bolle
2013-07-13 12:52                 ` Paul Bolle
2013-07-15  6:13                   ` Srivatsa S. Bhat

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=51DEC024.50603@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=durgadoss.r@intel.com \
    --cc=lantianyu1986@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=robert.jarzmik@intel.com \
    --cc=tianyu.lan@intel.com \
    --cc=toralf.foerster@gmx.de \
    --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).