kernel-fxtec-pro1x/drivers/usb
Mark Kuo 2f0d9d7e76 CHROMIUM: usb: gadget: f_accessory: add .raw_request callback
After this upstream commit: 3c86726cfe,
.raw_request is mandatory in hid_ll_driver structure, hence add an empty
raw_request() function.

BUG=chrome-os-partner:49140
TEST=none

Change-Id: Idd0bbe6960aad2c557376e4a24827d7e1df8e023
Signed-off-by: Mark Kuo <mkuo@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/321038
Commit-Ready: Andrew Bresticker <abrestic@chromium.org>
Tested-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
2018-08-28 17:10:42 +05:30
..
atm
c67x00
chipidea Merge 4.18-rc7 into usb-next 2018-07-30 10:04:58 +02:00
class Merge 4.18-rc7 into usb-next 2018-07-30 10:04:58 +02:00
common
core USB/PHY patches for 4.19-rc1 2018-08-18 10:21:49 -07:00
dwc2 usb: changes for v4.19 2018-07-30 10:21:14 +02:00
dwc3 usb: changes for v4.19 2018-07-30 10:21:14 +02:00
early
gadget CHROMIUM: usb: gadget: f_accessory: add .raw_request callback 2018-08-28 17:10:42 +05:30
host ARM: SoC driver updates 2018-08-23 13:52:46 -07:00
image
isp1760
misc
mon
mtu3
musb
phy
renesas_usbhs usb: renesas_usbhs: Kconfig: convert to SPDX identifiers 2018-07-30 15:27:14 +02:00
roles
serial USB: serial: pl2303: add a new device id for ATEN 2018-08-02 10:37:04 +02:00
storage
typec Merge 4.18-rc7 into usb-next 2018-07-30 10:04:58 +02:00
usbip
wusbcore
Kconfig
Makefile
README
usb-skeleton.c

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.