* [PATCH] PM: adjust comment regarding default wakeup policy
@ 2010-05-21 19:16 Alan Stern
2010-05-24 18:58 ` Rafael J. Wysocki
0 siblings, 1 reply; 3+ messages in thread
From: Alan Stern @ 2010-05-21 19:16 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux-pm mailing list
This patch (as1381) updates a comment describing the kernel's policy
toward enabling wakeup by default.
It also makes device_set_wakeup_capable() actually do something when
CONFIG_PM isn't enabled. It's not clear this is necessary; however if
it isn't then device_init_wakeup() and device_can_wakeup() should also
be do-nothing routines. Furthermore, I don't expect this change to
have any noticeable effect -- but if it does then clearly the old
behavior was wrong.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
CC: David Brownell <david-b@pacbell.net>
---
Index: usb-2.6/include/linux/pm_wakeup.h
===================================================================
--- usb-2.6.orig/include/linux/pm_wakeup.h
+++ usb-2.6/include/linux/pm_wakeup.h
@@ -27,8 +27,11 @@
#ifdef CONFIG_PM
-/* changes to device_may_wakeup take effect on the next pm state change.
- * by default, devices should wakeup if they can.
+/* Changes to device_may_wakeup take effect on the next pm state change.
+ *
+ * By default, most devices should leave wakeup disabled. The exceptions
+ * are devices that everyone expects to be wakeup sources: keyboards,
+ * power buttons, possibly network interfaces, etc.
*/
static inline void device_init_wakeup(struct device *dev, int val)
{
@@ -57,13 +60,16 @@ static inline int device_may_wakeup(stru
#else /* !CONFIG_PM */
-/* For some reason the next two routines work even without CONFIG_PM */
+/* For some reason the following routines work even without CONFIG_PM */
static inline void device_init_wakeup(struct device *dev, int val)
{
dev->power.can_wakeup = !!val;
}
-static inline void device_set_wakeup_capable(struct device *dev, int val) { }
+static inline void device_set_wakeup_capable(struct device *dev, int val)
+{
+ dev->power.can_wakeup = !!val;
+}
static inline int device_can_wakeup(struct device *dev)
{
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] PM: adjust comment regarding default wakeup policy
2010-05-21 19:16 [PATCH] PM: adjust comment regarding default wakeup policy Alan Stern
@ 2010-05-24 18:58 ` Rafael J. Wysocki
2010-05-24 20:09 ` Alan Stern
0 siblings, 1 reply; 3+ messages in thread
From: Rafael J. Wysocki @ 2010-05-24 18:58 UTC (permalink / raw)
To: Alan Stern; +Cc: Linux-pm mailing list
On Friday 21 May 2010, Alan Stern wrote:
> This patch (as1381) updates a comment describing the kernel's policy
> toward enabling wakeup by default.
>
> It also makes device_set_wakeup_capable() actually do something when
> CONFIG_PM isn't enabled. It's not clear this is necessary; however if
> it isn't then device_init_wakeup() and device_can_wakeup() should also
> be do-nothing routines. Furthermore, I don't expect this change to
> have any noticeable effect -- but if it does then clearly the old
> behavior was wrong.
>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> CC: David Brownell <david-b@pacbell.net>
OK by me.
Do you want me to push that in this merge window?
Rafael
> ---
>
> Index: usb-2.6/include/linux/pm_wakeup.h
> ===================================================================
> --- usb-2.6.orig/include/linux/pm_wakeup.h
> +++ usb-2.6/include/linux/pm_wakeup.h
> @@ -27,8 +27,11 @@
>
> #ifdef CONFIG_PM
>
> -/* changes to device_may_wakeup take effect on the next pm state change.
> - * by default, devices should wakeup if they can.
> +/* Changes to device_may_wakeup take effect on the next pm state change.
> + *
> + * By default, most devices should leave wakeup disabled. The exceptions
> + * are devices that everyone expects to be wakeup sources: keyboards,
> + * power buttons, possibly network interfaces, etc.
> */
> static inline void device_init_wakeup(struct device *dev, int val)
> {
> @@ -57,13 +60,16 @@ static inline int device_may_wakeup(stru
>
> #else /* !CONFIG_PM */
>
> -/* For some reason the next two routines work even without CONFIG_PM */
> +/* For some reason the following routines work even without CONFIG_PM */
> static inline void device_init_wakeup(struct device *dev, int val)
> {
> dev->power.can_wakeup = !!val;
> }
>
> -static inline void device_set_wakeup_capable(struct device *dev, int val) { }
> +static inline void device_set_wakeup_capable(struct device *dev, int val)
> +{
> + dev->power.can_wakeup = !!val;
> +}
>
> static inline int device_can_wakeup(struct device *dev)
> {
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] PM: adjust comment regarding default wakeup policy
2010-05-24 18:58 ` Rafael J. Wysocki
@ 2010-05-24 20:09 ` Alan Stern
0 siblings, 0 replies; 3+ messages in thread
From: Alan Stern @ 2010-05-24 20:09 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: Linux-pm mailing list
On Mon, 24 May 2010, Rafael J. Wysocki wrote:
> On Friday 21 May 2010, Alan Stern wrote:
> > This patch (as1381) updates a comment describing the kernel's policy
> > toward enabling wakeup by default.
> >
> > It also makes device_set_wakeup_capable() actually do something when
> > CONFIG_PM isn't enabled. It's not clear this is necessary; however if
> > it isn't then device_init_wakeup() and device_can_wakeup() should also
> > be do-nothing routines. Furthermore, I don't expect this change to
> > have any noticeable effect -- but if it does then clearly the old
> > behavior was wrong.
> >
> > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > CC: David Brownell <david-b@pacbell.net>
>
> OK by me.
>
> Do you want me to push that in this merge window?
No, it can wait for the window after this one.
Alan Stern
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-05-24 20:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-21 19:16 [PATCH] PM: adjust comment regarding default wakeup policy Alan Stern
2010-05-24 18:58 ` Rafael J. Wysocki
2010-05-24 20:09 ` Alan Stern
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox