Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751690AbXBJRwR (ORCPT ); Sat, 10 Feb 2007 12:52:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751697AbXBJRwR (ORCPT ); Sat, 10 Feb 2007 12:52:17 -0500 Received: from iabervon.org ([66.92.72.58]:1194 "EHLO iabervon.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751687AbXBJRwR (ORCPT ); Sat, 10 Feb 2007 12:52:17 -0500 Date: Sat, 10 Feb 2007 12:52:15 -0500 (EST) From: Daniel Barkalow To: "Rafael J. Wysocki" cc: nigel@nigel.suspend2.net, Robert Hancock , linux-kernel , Jeff Garzik , Pavel Machek , pm list Subject: Re: [PATCH] Re: NAK new drivers without proper power management? In-Reply-To: <200702101130.44471.rjw@sisk.pl> Message-ID: References: <200702101034.04410.rjw@sisk.pl> <1171101723.3821.22.camel@nigel.suspend2.net> <200702101130.44471.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1666 Lines: 35 On Sat, 10 Feb 2007, Rafael J. Wysocki wrote: > On Saturday, 10 February 2007 11:02, Nigel Cunningham wrote: > > > Well, the original desire was to stop new drivers getting in without > > proper power management. > > I know, but I agree with the argument that having a driver without the > suspend/resume support is better than not having the driver at all. How about if "proper power management" is defined to include the driver explicitly preventing suspend? It seems to me like the current problem is that driver writers don't think about power management at all, and the result is that, after suspend/resume, the system doesn't come back. It would be better if driver writers had to think about power management just enough to realize that it's not going to work, and make this information available to the system. At that point, it's relatively easy for the system to do something useful about it. > Also, I think there are quite some drivers already in the tree that don't > support suspend/resume explicitly and honestly we should start from adding the > suspend/resume routines to these drivers _before_ we ban new drivers like that. It'd be relatively quick to modify all the current drivers that don't explicitly support suspend/resume to explicitly not support it. (Or to explicitly support it trivially; /dev/null obviously doesn't need anything.) -Daniel *This .sig left intentionally blank* - 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/