From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Arve_Hj=F8nnev=E5g?= Subject: Re: [RFC][PATCH 00/11] Android PM extensions Date: Sat, 31 Jan 2009 17:04:37 -0800 Message-ID: References: <200901311939.30837.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <200901311939.30837.rjw@sisk.pl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: "Rafael J. Wysocki" Cc: Brian Swetland , linux-pm@lists.linux-foundation.org, Nigel Cunningham List-Id: linux-pm@vger.kernel.org On Sat, Jan 31, 2009 at 10:39 AM, Rafael J. Wysocki wrote: > However, I think that what we are used to call a sleep (or suspend) state= is > really a power off state for cell phone people. No, our power off state is the same as on the desktop. We do use the power key to enter and exit sleep, but you can configure a desktop system to do this as well. > Sleep states (suspend to RAM, hibernation) are the states of the whole sy= stem > in which no instructions are executed by the processor(s). The difference > between a sleep state and the power off state is that in a sleep state we= have > some application context saved (in memory or in a storage device) and > (in principle) after the system goes back to the working state, the > applications can continue doing do whatever they had been doing before the > system was put into the sleep state. On many arm processors there is also a big difference in what events can take you out of the power-off state versus the sleep-state. On some systems only the power button or the charger can turn the system back on after power-off while a number of external and internal interrupts can take the cpu out of the deep-sleep-state. > Well, I think that sleep states are not really useful in cell phones. Us= eful > is the ability to put all devices into low power states separately and as > needed (eg. after a period of inactivity). IOW, the system as a whole is > in the working state, but some parts of the hardware may be in low power = states > (even all of the I/O devices may be in low power states). That may very = well > look "asleep" from the user point of view, but it is not a sleep state. That may be true for single-core phones, but for dual core phones we get significant power savings by doing a full suspend on the core that runs Linux. On the system we currently have, we can enter the same hardware state from idle as we can from suspend. But, on an idle system with the radio is off, there are enough periodic timers to double the average power draw. On a previous system the power draw from idle was not even close to the power draw from suspend. -- = Arve Hj=F8nnev=E5g