linux_dsm_epyc7002/drivers/usb
Alan Stern 55c527187c [PATCH] USB: Consider power budget when choosing configuration
This patch (as609) changes the way we keep track of power budgeting for
USB hubs and devices, and it updates the choose_configuration routine to
take this information into account.  (This is something we should have
been doing all along.)  A new field in struct usb_device holds the amount
of bus current available from the upstream port, and the usb_hub structure
keeps track of the current available for each downstream port.

Two new rules for configuration selection are added:

	Don't select a self-powered configuration when only bus power
	is available.

	Don't select a configuration requiring more bus power than is
	available.

However the first rule is #if-ed out, because I found that the internal
hub in my HP USB keyboard claims that its only configuration is
self-powered.  The rule would prevent the configuration from being chosen,
leaving the hub & keyboard unconfigured.  Since similar descriptor errors
may turn out to be fairly common, it seemed wise not to include a rule
that would break automatic configuration unnecessarily for such devices.

The second rule may also trigger unnecessarily, although this should be
less common.  More likely it will annoy people by sometimes failing to
accept configurations that should never have been chosen in the first
place.

The patch also changes usbcore's reaction when no configuration is
suitable.  Instead of raising an error and rejecting the device, now
the core will simply leave the device unconfigured.  People can always
work around such problems by installing configurations manually through
sysfs.

Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-04 13:48:34 -08:00
..
atm [PATCH] USB: small cleanups 2006-01-04 13:48:34 -08:00
class [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
core [PATCH] USB: Consider power budget when choosing configuration 2006-01-04 13:48:34 -08:00
gadget [PATCH] USB: One potential problem in gadget/serial.c 2006-01-04 13:48:34 -08:00
host [PATCH] USB: Remove USB private semaphore 2006-01-04 13:48:34 -08:00
image [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
input [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
media [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
misc [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
mon [PATCH] USB: convert usbmon to use usb notifiers 2005-10-28 16:47:46 -07:00
net [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
serial [PATCH] USB: small cleanups 2006-01-04 13:48:34 -08:00
storage [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00
Kconfig [PATCH] USB: add S3C24XX USB Host driver support 2005-07-29 13:12:53 -07:00
Makefile [PATCH] USB: drivers/usb/storage/libusual 2006-01-04 13:48:31 -08:00
README Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
usb-skeleton.c [PATCH] USB: remove .owner field from struct usb_driver 2006-01-04 13:48:34 -08:00

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.