android_kernel_google_msm/drivers/usb
Pavankumar Kondeti 2a0f397dc8 USB: android: check for platform data presence before accessing it
commit c9cb205f (USB: android: Add a new LUN as CD-ROM in mass-storage)
access platform data without checking for NULL.  This causes a kernel
panic on targets which don't have platform data.

Change-Id: I4542b0dce81604706f90b7f6e851ed47c04a941c
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
2013-02-27 18:16:14 -08:00
..
atm
c67x00
class
core usb: ehci: Avoid phy lockup due to SOFs during port reset 2013-02-27 18:12:54 -08:00
dwc3 usb: dwc3-msm: Add support for LPM on cable disconnect 2013-02-27 18:16:12 -08:00
early
gadget USB: android: check for platform data presence before accessing it 2013-02-27 18:16:14 -08:00
host usb: dwc3-msm: Add support for LPM on cable disconnect 2013-02-27 18:16:12 -08:00
image
misc usb: misc: Send zero-length packets on bulk OUT 2013-02-27 18:13:41 -08:00
mon
musb
otg USB: msm_otg: Add debouncing logic for PMIC id line status handling 2013-02-27 18:15:18 -08:00
renesas_usbhs
serial usb: serial: Add flow control between wwan and tty drivers 2013-02-27 18:13:05 -08:00
storage
wusbcore
Kconfig usb: msm8974: Select USB_ARCH_HAS_XHCI by default 2013-02-27 18:14:55 -08:00
Makefile
README
usb-common.c
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 ("khubd").

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.