[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100805143302.GA21938@srcf.ucam.org>
Date: Thu, 5 Aug 2010 15:33:02 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: david@...g.hm
Cc: Arve Hjønnevåg <arve@...roid.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Arjan van de Ven <arjan@...radead.org>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
pavel@....cz, florian@...kler.org, stern@...land.harvard.edu,
swetland@...gle.com, peterz@...radead.org, tglx@...utronix.de,
alan@...rguk.ukuu.org.uk
Subject: Re: Attempted summary of suspend-blockers LKML thread
On Thu, Aug 05, 2010 at 07:22:53AM -0700, david@...g.hm wrote:
> I'm not sure it's possible to completely eliminate the race, even with
> wakelocks there is some time between the time you last check if the
> wakelock is set and when the hardware finishes responding to your
> commands to go to sleep (Unless you can set a level-based interrupt that
> will wake you up as soon as you finish going to sleep)
It's typically the case that you can - we've even seen that on x86 with
ACPI GPEs.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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