summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeoff Levand <geoff@infradead.org>2008-09-20 23:41:47 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2008-10-17 23:40:56 +0200
commit81ab5b8ee6b8cd5fe8cfdf0eea84eea0aa7b4da9 (patch)
treecbd43949a8e768c1284c6c525d925a4bca73cb96
parentUSB Serial: Sierra: debug message fix (diff)
downloadlinux-81ab5b8ee6b8cd5fe8cfdf0eea84eea0aa7b4da9.tar.xz
linux-81ab5b8ee6b8cd5fe8cfdf0eea84eea0aa7b4da9.zip
USB: Fix doc for usb_autopm_enable
Correct errors in the descriptions for usb_autopm_enable and usb_autopm_disable in the USB PM doc. Signed-off-by: Geoff Levand <geoff@infradead.org> Acked-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-rw-r--r--Documentation/usb/power-management.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/usb/power-management.txt b/Documentation/usb/power-management.txt
index 9d31140e3f5b..e48ea1d51010 100644
--- a/Documentation/usb/power-management.txt
+++ b/Documentation/usb/power-management.txt
@@ -350,12 +350,12 @@ without holding the mutex.
There also are a couple of utility routines drivers can use:
- usb_autopm_enable() sets pm_usage_cnt to 1 and then calls
- usb_autopm_set_interface(), which will attempt an autoresume.
-
- usb_autopm_disable() sets pm_usage_cnt to 0 and then calls
+ usb_autopm_enable() sets pm_usage_cnt to 0 and then calls
usb_autopm_set_interface(), which will attempt an autosuspend.
+ usb_autopm_disable() sets pm_usage_cnt to 1 and then calls
+ usb_autopm_set_interface(), which will attempt an autoresume.
+
The conventional usage pattern is that a driver calls
usb_autopm_get_interface() in its open routine and
usb_autopm_put_interface() in its close or release routine. But