From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: suspend blockers & Android integration Date: Fri, 4 Jun 2010 10:34:23 +0200 Message-ID: <20100604083423.GD15181@elte.hu> References: <20100603193045.GA7188@elte.hu> <20100603231153.GA11302@elte.hu> <20100603232302.GA16184@elte.hu> <20100604071354.GA14451@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Arve Hj?nnev?g Cc: tytso@mit.edu, Brian Swetland , Neil Brown , Thomas Gleixner , "Rafael J. Wysocki" , Alan Stern , Felipe Balbi , Peter Zijlstra , LKML , Florian Mickler , Linux OMAP Mailing List , Linux PM , Alan Cox , James Bottomley , Linus Torvalds , Peter Zijlstra , Kevin Hilman , "H. Peter Anvin" , Arjan van de Ven List-Id: linux-omap@vger.kernel.org * Arve Hj?nnev?g wrote: > > [...] > > > > Why do you need to track input wakeups? It's rather fragile and rather > > unnecessary [...] > > Because we have keys that should always turn the screen on, but the problem > is not specific to input events. If we enabled a wakeup event it usually > means we need this event to always work, not just when the system is fully > awake or fully suspended. Hm, i cannot follow that generic claim. Could you please point out the problem to me via a specific example? Which task does what, what undesirable thing happens where, etc. Thanks, Ingo