public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.name>
To: Greg KH <greg@kroah.com>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Cc: Patrick Mochel <mochel@osdl.org>
Subject: Re: [linux-usb-devel] [RFC] USB driver conversion to use "struct device_driver"
Date: Sat, 10 Aug 2002 11:57:28 +0200	[thread overview]
Message-ID: <200208101157.28759.oliver@neukum.name> (raw)
In-Reply-To: <20020810001005.GA29490@kroah.com>

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


  reply	other threads:[~2002-08-10 11:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-10  0:10 [RFC] USB driver conversion to use "struct device_driver" Greg KH
2002-08-10  9:57 ` Oliver Neukum [this message]
2002-08-10 15:40   ` [linux-usb-devel] " Greg KH
2002-08-10 21:18 ` David Brownell
2002-08-12 16:45   ` Greg KH
2002-08-12 18:30     ` David Brownell
2002-08-12 21:30       ` Greg KH
2002-08-12 23:36         ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200208101157.28759.oliver@neukum.name \
    --to=oliver@neukum.name \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mochel@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox