Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933170Ab3GKO2Q (ORCPT ); Thu, 11 Jul 2013 10:28:16 -0400 Received: from e23smtp01.au.ibm.com ([202.81.31.143]:41778 "EHLO e23smtp01.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933099Ab3GKO2M (ORCPT ); Thu, 11 Jul 2013 10:28:12 -0400 Message-ID: <51DEC024.50603@linux.vnet.ibm.com> Date: Thu, 11 Jul 2013 19:54:36 +0530 From: "Srivatsa S. Bhat" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0 MIME-Version: 1.0 To: Lan Tianyu CC: =?ISO-8859-1?Q?Toralf_F=F6rster?= , "Rafael J. Wysocki" , Viresh Kumar , cpufreq@vger.kernel.org, Linux PM list , "linux-kernel@vger.kernel.org" , "Jarzmik, Robert" , "R, Durgadoss" , Dirk Brandewie , tianyu.lan@intel.com Subject: Re: [PATCH] cpufreq: Fix cpufreq regression after suspend/resume References: <51C08370.4050906@gmx.de> <51CF1E53.6060902@gmx.de> <8029836.CFiJCXmRQ0@vostro.rjw.lan> <51D05DF4.50704@linux.vnet.ibm.com> <51D06556.7080204@gmx.de> <51D07E7F.2030709@linux.vnet.ibm.com> <51DDC8FA.4020609@gmx.de> <51DDE067.2020106@linux.vnet.ibm.com> <51DE4F44.6060506@linux.vnet.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13071114-1618-0000-0000-0000043F815F Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1131 Lines: 26 On 07/11/2013 07:33 PM, Lan Tianyu wrote: > 2013/7/11 Srivatsa S. Bhat : >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/