Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755659AbaGSR7F (ORCPT ); Sat, 19 Jul 2014 13:59:05 -0400 Received: from netrider.rowland.org ([192.131.102.5]:39484 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755317AbaGSR7D (ORCPT ); Sat, 19 Jul 2014 13:59:03 -0400 Date: Sat, 19 Jul 2014 13:59:01 -0400 (EDT) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Benson Leung cc: Dmitry Torokhov , "Rafael J. Wysocki" , Patrik Fimml , Bastien Nocera , , "linux-input@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: Power-managing devices that are not of interest at some point in time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 19 Jul 2014, Benson Leung wrote: > > This raises an interesting question. Suppose the system gets suspended > > while the lid is closed. At that point, shouldn't wakeup devices be > > enabled, even if they were already inhibited? > > It's possible that this could be a policy decision, ie, whether > power/wakeup is set to enabled for those devices or not. > However, I'd say that there's only one policy that makes sense in that > case : wakeups should be disabled while suspended. > > If we inhibited the device during runtime to prevent stray input > events from being generated, it wouldn't make sense to allow the > device to potentially generate an accidental wakeup while suspended. That doesn't really make sense. If you're afraid of a device generating spurious wakeup events when the lid is closed, you should never enable it for wakeup. After all, one of the first things that people often do after suspending their laptop is close the lid. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/