Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933974Ab1FWRkm (ORCPT ); Thu, 23 Jun 2011 13:40:42 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:53517 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932583Ab1FWRkj (ORCPT ); Thu, 23 Jun 2011 13:40:39 -0400 From: "Rafael J. Wysocki" To: Alan Stern Subject: Re: [Update][PATCH 7/8] PM / Domains: System-wide transitions support for generic domains (v3) Date: Thu, 23 Jun 2011 19:41:09 +0200 User-Agent: KMail/1.13.6 (Linux/3.0.0-rc4+; KDE/4.6.0; x86_64; ; ) Cc: Kevin Hilman , Linux PM mailing list , "Greg Kroah-Hartman" , Magnus Damm , Paul Walmsley , LKML , linux-sh@vger.kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106231941.09429.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2699 Lines: 61 On Thursday, June 23, 2011, Alan Stern wrote: > On Thu, 23 Jun 2011, Rafael J. Wysocki wrote: > > > > It might be worthwhile to include a little warning about the difference > > > between suspend and hibernate. > > > > Well, there already is one: > > > > "* The driver's idea of the device state may not agree with the device's > > physical state. This can happen during resume from hibernation." > > > > (in Documentation/power/runtime_pm.txt). Also, the new text in the patch > > https://lkml.org/lkml/2011/6/23/200 I've just sent says literally: > > > > "If that is the case and none of the situations listed above takes place, it > > may be more efficient to leave the devices that had been suspended before > > the system sleep began in the suspended state." > > > > where the "situations listed above" include it. > > > > Do you think that's not sufficient? > > The preceding text in your new patch says: > > +On some systems, however, system sleep is not entered through a global firmware > +or hardware operation. Instead, all hardware components are put into low-power > +states directly by the kernel in a coordinated way. Then, the system sleep > +state effectively follows from the states the hardware components end up in > +and the system is woken up from that state by a hardware interrupt or a similar > +mechanism entirely under the kernel's control. As a result, the kernel never > +gives control away and the states of all devices during resume are precisely > +known to it. > > It should say "system suspend" rather than "system sleep". It says "system sleep" to distinguish between the state of the system ("system sleep") and the operation leading to that state ("system suspend"). That terminology is used all over the document, so I don't think it's a good idea to change it just for this specific paragraph. I agree that "suspend" should be used where it talks about starting, stopping etc. > Then to drive the point home, the following sentence chould say > something like this: > > If that is the case and none of the situations listed above takes place > (in particular, if the system is waking up from suspend and not from > hibernation), it may be more efficient to leave the devices that had > been suspended before the system suspend began in the suspended state. That's fine by me, except that I'd simply say "(in particular, if the system is not waking up from hibernation)". Thanks, Rafael -- 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/