Report interrupt that caused system wakeup
Subsystems (5)
A message that is not in the archive (sent off-list or not yet received): [PATCH V11]Report interrupt that caused system wakeup
PATCH v11 1/1 Report interrupt that caused system wakeup
Add a sysfs attribute, /sys/power/pm_wakeup_irq, reporting the IRQ number of the first wakeup interrupt (that is, the first interrupt from an IRQ line armed for system wakeup) seen by the kernel during the most recent system suspend/resume cycle.
This feature will be useful for system wakeup diagnostics of spurious wakeup interrupts.
--- Documentation/ABI/testing/sysfs-power | 12 ++++++++++++ drivers/base/power/wakeup.c | 9 +++++++++ include/linux/suspend.h | 5 +++++ kernel/irq/pm.c | 2 +- kernel/power/main.c | 18 ++++++++++++++++++ 5 files changed, 45 insertions(+), 1 deletion(-)
Documentation/ABI/testing/sysfs-power +12 -0
@@ -256,3 +256,15 @@ Description: Writing a "1" enables this printing while writing a "0" disables it. The default value is "0". Reading from this file will display the current value. + +What: /sys/power/pm_wakeup_irq +Date: April 2015 +Contact: Alexandra Yates <[email protected]> +Description: + The /sys/power/pm_wakeup_irq file reports to user space the IRQ + number of the first wakeup interrupt (that is, the first + interrupt from an IRQ line armed for system wakeup) seen by the + kernel during the most recent system suspend/resume cycle. + + This output is useful for system wakeup diagnostics of spurious + wakeup interrupts.
drivers/base/power/wakeup.c +9 -0
@@ -868,6 +868,15 @@ EXPORT_SYMBOL_GPL(pm_system_wakeup);void pm_wakeup_clear (void ) { pm_abort_suspend = false; + wakeup_irq =0 ; +} + +void pm_system_irq_wakeup (unsigned int irq_number) +{ +if (wakeup_irq ==0 ) { + wakeup_irq = irq_number; +pm_system_wakeup (); + } }/**
include/linux/suspend.h +5 -0
@@ -371,6 +371,9 @@ static inline bool hibernation_available(void) { return false; }extern struct mutex pm_mutex; +/* IRQ number which causes system wakeup */ +extern unsigned int wakeup_irq; +#ifdef CONFIG_PM_SLEEP void save_processor_state (void );void restore_processor_state (void );
@@ -391,6 +394,7 @@ extern bool events_check_enabled;extern bool pm_wakeup_pending (void );extern void pm_system_wakeup (void );extern void pm_wakeup_clear (void ); +extern void pm_system_irq_wakeup (unsigned int );extern bool pm_get_wakeup_count (unsigned int *count,bool block);extern bool pm_save_wakeup_count (unsigned int count);extern void pm_wakep_autosleep_enabled (bool set);
@@ -440,6 +444,7 @@ static inline int unregister_pm_notifier(struct notifier_block *nb)static inline bool pm_wakeup_pending (void ) {return false; }static inline void pm_system_wakeup (void ) {}static inline void pm_wakeup_clear (void ) {} +static inline void pm_system_irq_wakeup (unsigned int ) {}static inline void lock_system_sleep (void ) {}static inline void unlock_system_sleep (void ) {}
kernel/irq/pm.c +1 -1
@@ -21,7 +21,7 @@ bool irq_pm_check_wakeup(struct irq_desc *desc) desc->istate |=IRQS_SUSPENDED |IRQS_PENDING ; desc->depth++;irq_disable (desc); -pm_system_wakeup (); +pm_system_irq_wakeup (irq_desc_get_irq (desc));return true; }return false;
kernel/power/main.c +18 -0
@@ -272,6 +272,23 @@ static inline void pm_print_times_init(void) { pm_print_times_enabled = !!initcall_debug; } + +unsigned int wakeup_irq; +static ssize_t pm_wakeup_irq_show (struct kobject *kobj, +struct kobj_attribute *attr, +char *buf) +{ +return wakeup_irq ?sprintf (buf,"%u\n" , wakeup_irq) : -ENODATA ; +} + +static ssize_t pm_wakeup_irq_store (struct kobject *kobj, +struct kobj_attribute *attr, +const char *buf,size_t n) +{ +return -EINVAL ; +} +power_attr (pm_wakeup_irq); +#else /* !CONFIG_PM_SLEEP_DEBUG */ static inline void pm_print_times_init (void ) {}#endif /* CONFIG_PM_SLEEP_DEBUG */
@@ -604,6 +621,7 @@ static struct attribute * g[] = {#endif #ifdef CONFIG_PM_SLEEP_DEBUG &pm_print_times_attr.attr, + &pm_wakeup_irq_attr.attr,#endif #endif #ifdef CONFIG_FREEZER
Signature · 1 line
1.9.1
Quoted 9 lines · Alexandra Yates
Add a sysfs attribute,
/sys/power/pm_wakeup_irq, reporting the IRQ number of the first wakeup interrupt (that is, the first interrupt from an IRQ line armed for system wakeup) seen by the kernel during the most recent system suspend/resume cycle.This feature will be useful for system wakeup diagnostics of spurious wakeup interrupts.
Signed-off-by Alexandra Yates <[email protected]>
I've applied this, but I needed to fix it up due to build problems.
I'd rather not to that again for any of your future patches.
Thanks,
Rafael
Hi Rafael,
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Alexandra Yates
Add a sysfs attribute,
/sys/power/pm_wakeup_irq, reporting the IRQ number of the first wakeup interrupt (that is, the first interrupt from an IRQ line armed for system wakeup) seen by the kernel during the most recent system suspend/resume cycle.
Quoted 7 lines
Quoted 4 lines
This feature will be useful for system wakeup diagnostics of spurious wakeup interrupts.
Signed-off-by Alexandra Yates <[email protected]>I've applied this, but I needed to fix it up due to build problems.
I'd rather not to that again for any of your future patches.
I'm sorry you encountered this issue. But, I built the patch before I sent it against linux-pm with release 2.5 and the latest as of yesterday.
I'm wondering if I'm using the wrong tree/branch? I would appreciate you help me understand what went wrong so that this doesn't happen again for future patches.
Quoted 8 lines
Thanks,
Rafael--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Thank you, <Alexandra>
Quoted 16 lines · Alexandra Yates
Hi Rafael,
Quoted 6 lines · Rafael J. Wysocki
Quoted 5 lines · Alexandra Yates
Add a sysfs attribute,
/sys/power/pm_wakeup_irq, reporting the IRQ number of the first wakeup interrupt (that is, the first interrupt from an IRQ line armed for system wakeup) seen by the kernel during the most recent system suspend/resume cycle.Quoted 7 lines
Quoted 4 lines
This feature will be useful for system wakeup diagnostics of spurious wakeup interrupts.
Signed-off-by Alexandra Yates <[email protected]>I've applied this, but I needed to fix it up due to build problems.
I'd rather not to that again for any of your future patches.
Quoted 8 lines
I'm sorry you encountered this issue. But, I built the patch before I sent it
against linux-pm with release 2.5 and the latest as of yesterday.I'm wondering if I'm using the wrong tree/branch? I would appreciate you help me
understand what went wrong so that this doesn't happen again for future patches.
The global wakeup_irq variable was defined under a CONFIG option and used outside of it, so build would break when that option was not set. Also, the name of the variable conflicted with another one defined already elsewhere.
Moreover, a static inline stub in the header file was missing the argument name (which is why it is a good idea to always use arg names and not just data types in function headers).
Thanks,
Rafael