From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Locke Subject: Re: So, what's the status on the recent patches here? Date: Mon, 11 Sep 2006 11:58:01 -0700 Message-ID: <2ab6a8005d5e786b2c71e75e58bc6017@comcast.net> References: <1ac6c8e2a817eb0e11257b47199872f8@comcast.net> <200609022130.59256.rjw@sisk.pl> <20060903213325.GB9991@elf.ucw.cz> <20060909121720.GD4277@ucw.cz> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: David Singleton Cc: Preece Scott-PREECE , linux-pm@lists.osdl.org, Pavel Machek List-Id: linux-pm@vger.kernel.org On Sep 11, 2006, at 8:11 AM, David Singleton wrote: > On 9/9/06, Pavel Machek wrote: >> On Fri 08-09-06 17:39:52, David Singleton wrote: >>> On 9/3/06, Pavel Machek wrote: >>>>> And those same steps are the same steps required to transition the >>>>> system to a new operating point, whether it's suspend or change >>>>> from 1.4GHz to 600MHz. >>>> >>>> No, processes are not frozen for simple cpu frequency change -- on >>>> non-broken cpus. >>> >>> I didn't say cpu frequency changes freeze processes. I said a = >>> suspend >>> does a prepare to suspend step (which freezes processes) and a cpu = >>> frequency >>> change does a prepare to change frequency step (where it will run = >>> the driver >>> notifier list to get drivers set to scale). >> >> Yep, and switching consoles is also same. It is prepare to switch, do >> a switch, notify people you switched. Shall we use same code? > > No. Since switching console is not dealing with changing the operating > state of the system. It's just switching which device is the console. > >> >>> They both do the same three steps: >>> >>> 1) prepare to transition >>> >>> 2) transition >>> >>> 3) finish transition >>> >>> That's one of my arguements as to why suspend states should be = >>> treated >>> just like frequency states. >> >> Cat and horse is a same animal. They both have 4 legs, one head and a >> tail. >> >> Anyway, as a software suspend maintainer, I do not want you to add >> non-sleeping states to /sys/power/state. I will NAK any attempt to do >> so. Please find more suitable interface. > > You are right. The power/state files for devices are for suspend > states as well. I'll find a different interface for operating states = > and > leave suspend states in /sys/power/state. You are just duplicating work that is already done in powerOP. I still = don't understand why you are redoing all the work Eugeny and I have = done. Nothing in our PowerOP interface prevents you from building on = top achieve your goals. > > David >> >> Pavel >> -- >> Thanks for all the (sleeping) penguins. >> > _______________________________________________ > linux-pm mailing list > linux-pm@lists.osdl.org > https://lists.osdl.org/mailman/listinfo/linux-pm >