From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Mon, 8 Sep 2014 10:34:00 -0700
Subject: How to understand "using interfaces layered over USB" in this
	article?
In-Reply-To: <CA+5jrf=c+d-Go6iGCyAPBU5QZx6CXAJM7bGf1H91Z_xoCZcJxw@mail.gmail.com>
References: <CA+5jrf=c+d-Go6iGCyAPBU5QZx6CXAJM7bGf1H91Z_xoCZcJxw@mail.gmail.com>
Message-ID: <20140908173400.GC11444@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, Sep 08, 2014 at 11:31:32AM +0800, lx wrote:
> hi all:
> ? ? ? I read this article, but I can't understand this??section?
> ############################################################
> 
> Most USB device drivers should pass these tables to the USB subsystem as
> well as to the module management subsystem.  Not all, though: some driver
> frameworks connect using interfaces layered over USB, and so they won't
> need such a "struct usb_driver".
> 
> ############################################################
> From:?https://www.kernel.org/doc/Documentation/usb/hotplug.txt
> 
> How to understand "using interfaces layered over USB"?

Think SCSI, HID, Serial, or any other type of usb device that is just
using the USB connection as a physical transport of a specific type of
data.

Does that help?

greg k-h