From 6003da563d69f5b5fb2b3ce6bff983337c957503 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Sat, 20 Sep 2008 14:41:47 -0700 Subject: [PATCH] --- yaml --- r: 115760 b: refs/heads/master c: 81ab5b8ee6b8cd5fe8cfdf0eea84eea0aa7b4da9 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/usb/power-management.txt | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/[refs] b/[refs] index 42edeb035397..178a5f7f5c1a 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 7384a922b5a716b4e9dbcdce738f2b2104892008 +refs/heads/master: 81ab5b8ee6b8cd5fe8cfdf0eea84eea0aa7b4da9 diff --git a/trunk/Documentation/usb/power-management.txt b/trunk/Documentation/usb/power-management.txt index 9d31140e3f5b..e48ea1d51010 100644 --- a/trunk/Documentation/usb/power-management.txt +++ b/trunk/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