Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 10 Aug 2002 07:00:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 10 Aug 2002 07:00:52 -0400 Received: from mailout10.sul.t-online.com ([194.25.134.21]:4247 "EHLO mailout10.sul.t-online.com") by vger.kernel.org with ESMTP id convert rfc822-to-8bit; Sat, 10 Aug 2002 07:00:51 -0400 Content-Type: text/plain; charset=US-ASCII From: Oliver Neukum To: Greg KH , linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [linux-usb-devel] [RFC] USB driver conversion to use "struct device_driver" Date: Sat, 10 Aug 2002 11:57:28 +0200 User-Agent: KMail/1.4.1 Cc: Patrick Mochel References: <20020810001005.GA29490@kroah.com> In-Reply-To: <20020810001005.GA29490@kroah.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: <200208101157.28759.oliver@neukum.name> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1067 Lines: 27 Am Samstag, 10. August 2002 02:10 schrieb Greg KH: > Hi all, > The USB subsystem only binds drivers to USB "interfaces". A USB device > may have many "interfaces", so a single device may have many drivers > attached to it, handling different portions of it (think of a USB > speaker, which has a audio driver for the audio stream, and a HID driver > for the speaker buttons.) Because of this I had to create a "empty" > device driver that I attach to the USB device structure. This ensures > it shows up properly in the driverfs tree, and that no USB drivers try > to bind to it. Hi, the probe/disconnect changes are an improvement. But what do we call a device? IMHO the device in terms of driverfs is the interface, thus the usb_device should be seen as a bus, which interfaces are attached to. 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/