Commit 81ab5b8e authored by Geoff Levand's avatar Geoff Levand Committed by Greg Kroah-Hartman

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: default avatarGeoff Levand <geoff@infradead.org>
Acked-by: default avatarAlan Stern <stern@rowland.harvard.edu>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent 7384a922
...@@ -350,12 +350,12 @@ without holding the mutex. ...@@ -350,12 +350,12 @@ without holding the mutex.
There also are a couple of utility routines drivers can use: 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_enable() sets pm_usage_cnt to 0 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_set_interface(), which will attempt an autosuspend. 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 The conventional usage pattern is that a driver calls
usb_autopm_get_interface() in its open routine and usb_autopm_get_interface() in its open routine and
usb_autopm_put_interface() in its close or release routine. But usb_autopm_put_interface() in its close or release routine. But
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment