The patch titled
usb: power-management.txt - disconnect clarification
has been removed from the -mm tree. Its filename was
usb-power-managementtxt-disconnect-clarification.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
Subject: usb: power-management.txt - disconnect clarification
From: Tilman Schmidt <tilman@xxxxxxx>
Add a paragraph to Documentation/usb/power-management.txt about the
interaction between suspend and disconnect.
Signed-off-by: Tilman Schmidt <tilman@xxxxxxx>
Cc: Greg KH <greg@xxxxxxxxx>
Cc: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/usb/power-management.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff -puN Documentation/usb/power-management.txt~usb-power-managementtxt-disconnect-clarification Documentation/usb/power-management.txt
--- a/Documentation/usb/power-management.txt~usb-power-managementtxt-disconnect-clarification
+++ a/Documentation/usb/power-management.txt
@@ -278,6 +278,12 @@ optional. The methods' jobs are quite s
(although the interfaces will be in the same altsettings as
before the suspend).
+If the device is disconnected or powered down while it is suspended,
+the disconnect method will be called instead of the resume or
+reset_resume method. This will also happen if the system is resumed
+from hibernation, as the device could have been disconnected without
+the system being able to detect it.
+
The reset_resume method is used by the USB Persist facility (see
Documentation/usb/persist.txt) and it can also be used under certain
circumstances when CONFIG_USB_PERSIST is not enabled. Currently, if a
_
Patches currently in -mm which might be from tilman@xxxxxxx are
usb-power-managementtxt-disconnect-clarification.patch
gigaset-clean-up-urb-status-usage.patch
gigaset-code-cleanups.patch
bas_gigaset-suspend-support-v2.patch
usb_gigaset-suspend-support-v3.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
