Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753652AbZKPVXS (ORCPT ); Mon, 16 Nov 2009 16:23:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752682AbZKPVXP (ORCPT ); Mon, 16 Nov 2009 16:23:15 -0500 Received: from smtp-out002.kontent.com ([81.88.40.216]:56360 "EHLO smtp-out002.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752665AbZKPVXN (ORCPT ); Mon, 16 Nov 2009 16:23:13 -0500 From: Oliver Neukum To: Alan Stern Subject: Re: [RFC][PATCH 1/10] PM: Add flag for devices capable of generating run-time wake-up events Date: Mon, 16 Nov 2009 22:23:15 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.32-rc6-0.1-default; KDE/4.3.1; x86_64; ; ) Cc: "Rafael J. Wysocki" , pm list , LKML , Linux PCI , ACPI Devel Maling List , Jesse Barnes , Matthew Garrett , Shaohua Li , Bjorn Helgaas References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911162223.15897.oliver@neukum.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 838 Lines: 22 Am Montag, 16. November 2009 22:00:49 schrieb Alan Stern: > > > What if the user wants to override the kernel's setting? Should there > > > be a sysfs attribute controlling the flag? > > > > > > I have no plans for adding anything like that. > > So if the kernel makes a mistake here, the user won't be able to > correct it. If the kernel cannot tell whether a device can generate a request for remote wakeup, how would it know the enable such requests? Now we might come to a device that has a flatly wrong firmware, but has that really been encountered in the wild? Regards Oliver -- 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/