[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201005272355.13222.rjw@sisk.pl>
Date: Thu, 27 May 2010 23:55:13 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Matthew Garrett <mjg59@...f.ucam.org>,
Thomas Gleixner <tglx@...utronix.de>,
Arve Hjønnevåg <arve@...roid.com>,
Florian Mickler <florian@...kler.org>,
Vitaly Wool <vitalywool@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Paul@...p1.linux-foundation.org, felipe.balbi@...ia.com,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux PM <linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)
On Thursday 27 May 2010, Alan Cox wrote:
> > > If one works so does the other.
> >
> > Not at all. The entire point of opportunistic suspend is that I don't
> > care is currently in TASK_RUNNABLE or has a timer that's due to expire
> > in 100msec - based on policy (through not having any held suspend
> > blockers), I'll go to sleep. That's easily possible on PCs.
>
> Yes I appreciate what suspend blockers are trying to do. Now how does
> that connect with my first sentence ?
I guess what Matthew wanted to say was that you couldn't use ACPI S3 as
a very deep CPU idle state, because of the way wakeup sources are set up
for it, while you could use it for aggressive power management with suspend
blockers as proposed by Arve.
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists