WSL2-Linux-Kernel/drivers/usb
Steinar H. Gunderson f7d34b445a USB: Add support for usbfs zerocopy.
Add a new interface for userspace to preallocate memory that can be
used with usbfs. This gives two primary benefits:

 - Zerocopy; data no longer needs to be copied between the userspace
   and the kernel, but can instead be read directly by the driver from
   userspace's buffers. This works for all kinds of transfers (even if
   nonsensical for control and interrupt transfers); isochronous also
   no longer need to memset() the buffer to zero to avoid leaking kernel data.

 - Once the buffers are allocated, USB transfers can no longer fail due to
   memory fragmentation; previously, long-running programs could run into
   problems finding a large enough contiguous memory chunk, especially on
   embedded systems or at high rates.

Memory is allocated by using mmap() against the usbfs file descriptor,
and similarly deallocated by munmap(). Once memory has been allocated,
using it as pointers to a bulk or isochronous operation means you will
automatically get zerocopy behavior. Note that this also means you cannot
modify outgoing data until the transfer is complete. The same holds for
data on the same cache lines as incoming data; DMA modifying them at the
same time could lead to your changes being overwritten.

There's a new capability USBDEVFS_CAP_MMAP that userspace can query to see
if the running kernel supports this functionality, if just trying mmap() is
not acceptable.

Largely based on a patch by Markus Rechberger with some updates. The original
patch can be found at:

  http://sundtek.de/support/devio_mmap_v0.4.diff

Signed-off-by: Steinar H. Gunderson <sesse@google.com>
Signed-off-by: Markus Rechberger <mrechberger@gmail.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-02-14 17:11:48 -08:00
..
atm USB: cxacru: fix an bounds check warning 2016-02-03 13:52:10 -08:00
c67x00
chipidea usb: chipidea: debug: use list_for_each_entry 2016-01-24 20:55:33 -08:00
class cdc-acm: implement put_char() and flush_chars() 2016-02-14 17:06:43 -08:00
common usb: define USB_SPEED_SUPER_PLUS speed for SuperSpeedPlus USB3.1 devices 2016-01-24 20:16:52 -08:00
core USB: Add support for usbfs zerocopy. 2016-02-14 17:11:48 -08:00
dwc2 usb: add HAS_IOMEM dependency to USB_DWC2 2016-02-14 17:09:56 -08:00
dwc3 usb: dwc3: gadget: set the OTG flag in dwc3 gadget driver. 2016-02-03 23:58:20 +02:00
early
gadget usb: add HAS_IOMEM dependency to USB_PXA27X 2016-02-14 17:09:56 -08:00
host usb: add HAS_IOMEM dependency to USB_ISP1362_HCD 2016-02-14 17:09:56 -08:00
image
isp1760
misc usb: add HAS_IOMEM dependency to USB_APPLEDISPLAY 2016-02-14 17:09:56 -08:00
mon usb: core: rename mutex usb_bus_list_lock to usb_bus_idr_lock 2016-02-06 21:55:57 -08:00
musb usb: add HAS_IOMEM dependency to USB_MUSB_HDRC 2016-02-14 17:09:56 -08:00
phy usb: phy: mxs: declare variable with initialized value 2016-02-03 19:57:41 +02:00
renesas_usbhs usb: renesas_usbhs: constify usbhs_pkt_handle structures 2016-01-24 19:45:09 -08:00
serial USB: option: fix Cinterion AHxx enumeration 2016-01-25 13:32:53 +01:00
storage usb: storage: ene_ub6250: Remove unnecessary cast in kfree 2016-02-03 13:48:12 -08:00
usbip usb: usbip: Fix possible deadlocks reported by lockdep 2016-02-03 13:52:10 -08:00
wusbcore USB: core, wusbcore: use bus_to_hcd 2016-01-24 21:00:33 -08:00
Kconfig
Makefile
README
usb-skeleton.c

README

To understand all the Linux-USB framework, you'll use these resources:

    * This source code.  This is necessarily an evolving work, and
      includes kerneldoc that should help you get a current overview.
      ("make pdfdocs", and then look at "usb.pdf" for host side and
      "gadget.pdf" for peripheral side.)  Also, Documentation/usb has
      more information.

    * The USB 2.0 specification (from www.usb.org), with supplements
      such as those for USB OTG and the various device classes.
      The USB specification has a good overview chapter, and USB
      peripherals conform to the widely known "Chapter 9".

    * Chip specifications for USB controllers.  Examples include
      host controllers (on PCs, servers, and more); peripheral
      controllers (in devices with Linux firmware, like printers or
      cell phones); and hard-wired peripherals like Ethernet adapters.

    * Specifications for other protocols implemented by USB peripheral
      functions.  Some are vendor-specific; others are vendor-neutral
      but just standardized outside of the www.usb.org team.

Here is a list of what each subdirectory here is, and what is contained in
them.

core/		- This is for the core USB host code, including the
		  usbfs files and the hub class driver ("hub_wq").

host/		- This is for USB host controller drivers.  This
		  includes UHCI, OHCI, EHCI, and others that might
		  be used with more specialized "embedded" systems.

gadget/		- This is for USB peripheral controller drivers and
		  the various gadget drivers which talk to them.


Individual USB driver directories.  A new driver should be added to the
first subdirectory in the list below that it fits into.

image/		- This is for still image drivers, like scanners or
		  digital cameras.
../input/	- This is for any driver that uses the input subsystem,
		  like keyboard, mice, touchscreens, tablets, etc.
../media/	- This is for multimedia drivers, like video cameras,
		  radios, and any other drivers that talk to the v4l
		  subsystem.
../net/		- This is for network drivers.
serial/		- This is for USB to serial drivers.
storage/	- This is for USB mass-storage drivers.
class/		- This is for all USB device drivers that do not fit
		  into any of the above categories, and work for a range
		  of USB Class specified devices. 
misc/		- This is for all USB device drivers that do not fit
		  into any of the above categories.