Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932222AbXAOLK2 (ORCPT ); Mon, 15 Jan 2007 06:10:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932231AbXAOLK2 (ORCPT ); Mon, 15 Jan 2007 06:10:28 -0500 Received: from smtp-out001.kontent.com ([81.88.40.215]:47404 "EHLO smtp-out.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932222AbXAOLK2 (ORCPT ); Mon, 15 Jan 2007 06:10:28 -0500 From: Oliver Neukum To: icxcnika@mar.tar.cc, linux-usb-devel@lists.sourceforge.net, Alan Stern Subject: Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken Date: Mon, 15 Jan 2007 12:10:49 +0100 User-Agent: KMail/1.8 Cc: linux-kernel@vger.kernel.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701151210.49495.oliver@neukum.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 873 Lines: 22 Am Sonntag, 14. Januar 2007 20:47 schrieb icxcnika@mar.tar.cc: > > Can anyone suggest another approach? > > > > Alan Stern > > Just a thought, you could use both a blacklist approach, and a module > paramater, or something in sysfs, to allow specifying devices that won't > be suspend and resume compatible. Upon further thought, a module parameter won't do as the problem will arise without a driver loaded. A sysfs parameter turns the whole affair into a race condition. Will you set the guard parameter before the autosuspend logic strikes? Unfortunately this leaves only the least attractive solution. 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/