aboutsummaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2011-09-26 11:38:50 -0400
committerRafael J. Wysocki <rjw@sisk.pl>2011-10-16 17:28:51 -0400
commit8f88893c05f2f677f18f2ce5591b4bed5d4a7535 (patch)
tree4368e42a2c35ee018f7cd91b8fa6643f6ff2b852 /drivers
parent37cce26b32142f09a8967f6d238178af654b20de (diff)
PM: Update the policy on default wakeup settings
This patch (as1485) documents a change to the kernel's default wakeup policy. Devices that forward wakeup requests between buses should be enabled for wakeup by default. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/base/power/wakeup.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/base/power/wakeup.c b/drivers/base/power/wakeup.c
index 84f7c7d5a098..14ee07e9cc43 100644
--- a/drivers/base/power/wakeup.c
+++ b/drivers/base/power/wakeup.c
@@ -276,7 +276,9 @@ EXPORT_SYMBOL_GPL(device_set_wakeup_capable);
276 * 276 *
277 * By default, most devices should leave wakeup disabled. The exceptions are 277 * By default, most devices should leave wakeup disabled. The exceptions are
278 * devices that everyone expects to be wakeup sources: keyboards, power buttons, 278 * devices that everyone expects to be wakeup sources: keyboards, power buttons,
279 * possibly network interfaces, etc. 279 * possibly network interfaces, etc. Also, devices that don't generate their
280 * own wakeup requests but merely forward requests from one bus to another
281 * (like PCI bridges) should have wakeup enabled by default.
280 */ 282 */
281int device_init_wakeup(struct device *dev, bool enable) 283int device_init_wakeup(struct device *dev, bool enable)
282{ 284{