From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: [RFD] Automatic suspend Date: Wed, 18 Feb 2009 23:44:05 +0100 Message-ID: <200902182344.12100.oliver@neukum.org> References: <200902182217.48321.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: Content-Disposition: inline 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: Arve =?iso-8859-1?q?Hj=F8nnev=E5g?= Cc: Kyle Moffett , Uli Luckas , LKML , Nigel Cunningham , Brian Swetland , pm list , Arjan van de Ven List-Id: linux-pm@vger.kernel.org Am Wednesday 18 February 2009 23:35:26 schrieb Arve Hj=F8nnev=E5g: > >> Allowing user space to suspend input devices while they are still open > >> is useful. The user-space code that reads from the input devices does > >> not need to know if the device is suspended or not, and the kernel > >> cannot auto suspend input devices based on inactivity. > > > > Hmm. =A0Why can't it? > = > Because they stop working. It is OK for us to turn off the touchscreen > when the screen is off, but when the screen is on the user will touch > items on the screen and expect them to respond. (We could also turn > off the touchscreen when the keyguard is on, but we don't currently do > this.) This depends on the capabilities of the input device in question. Some USB keyboards can be autosuspended under these conditions because they can do remote wakeup. Regards Oliver