From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: OpPoint summary Date: Sun, 17 Sep 2006 14:56:55 +0200 Message-ID: <20060917125655.GJ2741@elf.ucw.cz> References: <20060911195546.GB11901@elf.ucw.cz> <4505CCDA.8020501@gmail.com> <20060911210026.GG11901@elf.ucw.cz> <4505DDA6.8080603@gmail.com> <20060911225617.GB13474@elf.ucw.cz> <20060912001701.GC14234@linux.intel.com> <20060912033700.GD27397@kroah.com> <20060914055529.GA18031@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: David Singleton Cc: Greg KH , linux-pm@lists.osdl.org, kernel list List-Id: linux-pm@vger.kernel.org Hi! > I've incorporated Pavels suggestions and only put suspend states > in the /sys/power/state file. The control file for frequency and Ok... > voltage operating > point transitions is now in > /sys/power/operating_points/current_point. How do you handle SMP? If I want full speed on CPU0 and 100MHz on cpu 1? > --- linux-2.6.17.orig/kernel/power/main.c > +++ linux-2.6.17/kernel/power/main.c > @@ -16,6 +16,7 @@ > #include > #include > #include > +#include > > #include "power.h" > > @@ -49,7 +50,7 @@ void pm_set_ops(struct pm_ops * ops) > * the platform can enter the requested state. > */ > > -static int suspend_prepare(suspend_state_t state) > +static int suspend_prepare(struct oppoint * state) ...so why this change? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html