From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Belay Subject: Re: [RFC] A New Power Management API Date: Fri, 15 Apr 2005 14:20:25 -0400 Message-ID: <1113589226.3451.46.camel@localhost.localdomain> References: <1113533193.3451.40.camel@localhost.localdomain> <9268368b0504150616652c268b@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============48060229438941082==" Return-path: In-Reply-To: <9268368b0504150616652c268b@mail.gmail.com> 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: Daniel Petrini Cc: Linux-pm mailing list List-Id: linux-pm@vger.kernel.org --===============48060229438941082== Content-Type: text/plain Content-Transfer-Encoding: 7bit On Fri, 2005-04-15 at 09:16 -0400, Daniel Petrini wrote: > Hi, > > Suggestion: as discussed in early weeks, why don't adopt names taking > into consideration that Linux can run in systems other than desktops > and servers? > > #define PM_SYSTEM_STATE_SUSPEND_RAM 0x00000010 > #define PM_SYSTEM_STATE_SUSPEND_DISK 0x00000020 > > PM_SYSTEM_STATE_SUSPEND_DISK an be something like > PM_SYSTEM_STATE_DEEP_SUSPEND and so on... > > So you can have better acceptance of people working in other areas. > > My two cents. > Regards, > > Daniel Petrini My idea here was to provide some optional flags that describe characteristics of a given system-specific state. They may need to be revised, but the intention was to provide meaningful information to drivers without architecture specific code. Architecture-specific drivers will likely ignore these and pay more attention to the state number. Thanks, Adam --===============48060229438941082== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============48060229438941082==--