From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Date: Fri, 05 Mar 2010 21:08:09 +0000 Subject: Re: Problems with remote-wakeup settings Message-Id: <201003052208.09486.oliver@neukum.org> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Alan Stern Cc: "Rafael J. Wysocki" , Linux-pm mailing list , linux-input@vger.kernel.org, linux-hotplug@vger.kernel.org, USB list , Kernel development list Am Freitag, 5. M=E4rz 2010 21:59:31 schrieben Sie: > > I guess it's better if drivers don't set should_wakeup if unsure, but o= f course > > that's impossible to enforce. >=20 > That's the real question. Ideally, drivers won't touch should_wakeup. =20 > How do we get there from here? Enable it only for devices specifically designed for wakeup, that is keyboards, power buttons and WoL, perhaps also mice and modems. Are we far away from that? Regards Oliver From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: Problems with remote-wakeup settings Date: Fri, 5 Mar 2010 22:08:09 +0100 Message-ID: <201003052208.09486.oliver@neukum.org> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from smtp-out002.kontent.com ([81.88.40.216]:38048 "EHLO smtp-out002.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754500Ab0CEVIe convert rfc822-to-8bit (ORCPT ); Fri, 5 Mar 2010 16:08:34 -0500 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Alan Stern Cc: "Rafael J. Wysocki" , Linux-pm mailing list , linux-input@vger.kernel.org, linux-hotplug@vger.kernel.org, USB list , Kernel development list Am Freitag, 5. M=E4rz 2010 21:59:31 schrieben Sie: > > I guess it's better if drivers don't set should_wakeup if unsure, b= ut of course > > that's impossible to enforce. >=20 > That's the real question. Ideally, drivers won't touch should_wakeup= =2E =20 > How do we get there from here? Enable it only for devices specifically designed for wakeup, that is keyboards, power buttons and WoL, perhaps also mice and modems. Are we far away from that? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-input" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755155Ab0CEVIg (ORCPT ); Fri, 5 Mar 2010 16:08:36 -0500 Received: from smtp-out002.kontent.com ([81.88.40.216]:38048 "EHLO smtp-out002.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754500Ab0CEVIe convert rfc822-to-8bit (ORCPT ); Fri, 5 Mar 2010 16:08:34 -0500 From: Oliver Neukum To: Alan Stern Subject: Re: Problems with remote-wakeup settings Date: Fri, 5 Mar 2010 22:08:09 +0100 User-Agent: KMail/1.12.4 (Linux/2.6.33-0.1-default; KDE/4.3.5; x86_64; ; ) Cc: "Rafael J. Wysocki" , "Linux-pm mailing list" , linux-input@vger.kernel.org, linux-hotplug@vger.kernel.org, USB list , Kernel development list References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Message-Id: <201003052208.09486.oliver@neukum.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Freitag, 5. März 2010 21:59:31 schrieben Sie: > > I guess it's better if drivers don't set should_wakeup if unsure, but of course > > that's impossible to enforce. > > That's the real question. Ideally, drivers won't touch should_wakeup. > How do we get there from here? Enable it only for devices specifically designed for wakeup, that is keyboards, power buttons and WoL, perhaps also mice and modems. Are we far away from that? Regards Oliver