linux.git/drivers/usb/core/driver.c, branch v2.6.37

USB: do not print -ESHUTDOWN message if usb at otg device mode

2010-10-22T17:22:05+00:00

At otg device mode, the otg host resume should do no-op during
system resume, otherwise, the otg device will be treated as a
host for enumeration.

So, the otg host driver returns -ESHUTDOWN if it detects the
current usb mode is device mode. The host driver has to return
-ESHUTDOWN, otherwise, the usb_hc_died will be called.

Signed-off-by: Peter Chen 
Signed-off-by: Greg Kroah-Hartman

USB: remove fake "address-of" expressions

2010-08-10T21:35:45+00:00

Fake "address-of" expressions that evaluate to NULL generally confuse
readers and can provoke compiler warnings.  This patch (as1412)
removes three such fake expressions, using "#ifdef"s in their place.

Signed-off-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

USB: core driver: Fix Coding Styles

2010-08-10T21:35:34+00:00

Fixed coding styles in the core usb driver.

Signed-off-by: Carlos Sánchez Acosta 
Signed-off-by: Alejandro Sánchez Acosta 
Signed-off-by: Greg Kroah-Hartman

USB: obey the sysfs power/wakeup setting

2010-06-30T15:16:06+00:00

This patch (as1403) is a partial reversion of an earlier change
(commit 5f677f1d45b2bf08085bbba7394392dfa586fa8e "USB: fix remote
wakeup settings during system sleep").  After hearing from a user, I
realized that remote wakeup should be enabled during system sleep
whenever userspace allows it, and not only if a driver requests it
too.

Indeed, there could be a device with no driver, that does nothing but
generate a wakeup request when the user presses a button.  Such a
device should be allowed to do its job.

The problem fixed by the earlier patch -- device generating a wakeup
request for no reason, causing system suspend to abort -- was also
addressed by a later patch ("USB: don't enable remote wakeup by
default", accepted but not yet merged into mainline).  The device
won't be able to generate the bogus wakeup requests because it will be
disabled for remote wakeup by default.  Hence this reversion will not
re-introduce any old problems.

Signed-off-by: Alan Stern 
Cc: stable  [.34]
Signed-off-by: Greg Kroah-Hartman

USB: unbind all interfaces before rebinding them

2010-06-04T20:16:20+00:00

This patch (as1387) fixes a bug introduced during the changeover to
the runtime PM framework.  When a driver doesn't support resume or
reset-resume, and consequently its interfaces need to be unbound and
rebound, we have to unbind all the interfaces before trying to rebind
any of them.  Otherwise the driver's probe method for one interface
could try to claim a different interface and fail, because that other
interface hasn't been unbound yet.

This fixes Bugzilla #15788.  The symptom is that some USB sound cards
don't work after hibernation.

Signed-off-by: Alan Stern 
Tested-by: François Valenduc 
Cc: stable  [.34]
Signed-off-by: Greg Kroah-Hartman

USB: fix interface runtime-PM settings

2010-05-20T20:21:45+00:00

This patch (as1379) reworks the logic for handling USB interface
runtime-PM settings -- hopefully it's right this time!  The problem is
that when a driver is unbound or binding fails, runtime PM for the
interface always gets disabled.  But pm_runtime_disable() nests, so it
shouldn't be called unless the interface was previously enabled for
runtime PM.

Signed-off-by: Alan Stern 
Reported-by: Rob Duncan 
Tested-by: Rob Duncan 
Signed-off-by: Greg Kroah-Hartman

USB: use PM core routines to enable/disable autosuspend

2010-05-20T20:21:37+00:00

This patch (as1366) replaces the private routines
usb_enable_autosuspend() and usb_disable_autosuspend() with calls to
the standard pm_runtime_allow() and pm_runtime_forbid() functions in
the runtime PM framework.  They do the same thing.

Signed-off-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

USB: improve runtime remote wakeup settings

2010-05-20T20:21:37+00:00

This patch (as1362) adjusts the way the USB autosuspend routines
handle remote-wakeup settings.  They aren't supposed to use
device_may_wakeup(); that test is intended only for system sleep, not
runtime power management.  Instead the code checks to see if any
interface drivers need remote wakeup; if they do then it is enabled,
provided the device is capable of it.

Signed-off-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

USB: make hcd.h public (drivers dependency)

2010-05-20T20:21:30+00:00

The usbcore headers: hcd.h and hub.h are shared between usbcore,
HCDs and a couple of other drivers (e.g. USBIP modules).
So, it makes sense to move them into a more public location and
to cleanup dependency of those modules on kernel internal headers.
This patch moves hcd.h from drivers/usb/core into include/linux/usb/

Signed-of-by: Eric Lescouet 
Cc: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

USB: put claimed interfaces in the "suspended" state

2010-04-22T22:18:28+00:00

This patch (as1370) fixes a bug in the USB runtime power management
code.  When a driver claims an interface, it doesn't expect to need to
call usb_autopm_get_interface() or usb_autopm_put_interface() for
runtime PM to work.  Runtime PM can be controlled by the driver's
primary interface; the additional interfaces it claims shouldn't
interfere.  As things stand, the claimed interfaces will prevent the
device from autosuspending.

To fix this problem, the patch sets interfaces to the suspended state
when they are claimed.

Also, although in theory this shouldn't matter, the patch changes the
suspend code so that interfaces are suspended in reverse order from
detection and resuming.  This is how the PM core works, and we ought
to use the same approach.

Signed-off-by: Alan Stern 
Debugged-and-tested-by: Dominik Brodowski 
Signed-off-by: Greg Kroah-Hartman