summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/device_sysfs.c
diff options
context:
space:
mode:
authorChen Yu <yu.c.chen@intel.com>2015-10-24 19:02:46 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2015-10-26 04:39:26 +0100
commit8c01275e0cdf1959aa25c322fd5870c097733195 (patch)
tree3b667a834110739761d3f78d9ab7ce3640c7d3a9 /drivers/acpi/device_sysfs.c
parentACPI: Using correct irq when waiting for events (diff)
downloadlinux-8c01275e0cdf1959aa25c322fd5870c097733195.tar.xz
linux-8c01275e0cdf1959aa25c322fd5870c097733195.zip
ACPI / PM: Fix incorrect wakeup IRQ setting during suspend-to-idle
For an ACPI compatible system, the SCI (ACPI System Control Interrupt) is used to wake the system up from suspend-to-idle. Once the CPU is woken up by the SCI, the interrupt handler will first check if the current IRQ has been configured for system wakeup, so irq_pm_check_wakeup() is invoked to validate the IRQ number. However, during suspend-to-idle, enable_irq_wake() is called for acpi_gbl_FADT.sci_interrupt, although the IRQ number that the SCI handler has been installed for should be passed to it instead. Thus, if acpi_gbl_FADT.sci_interrupt happens to be different from that number, ACPI interrupts will not be able to wake up the system from sleep. Fix this problem by passing the IRQ number returned by acpi_gsi_to_irq() to enable_irq_wake() instead of acpi_gbl_FADT.sci_interrupt. Cc: 3.18+ <stable@vger.kernel.org> # 3.18+ Acked-by: Lv Zheng <lv.zheng@intel.com> Signed-off-by: Chen Yu <yu.c.chen@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/acpi/device_sysfs.c')
0 files changed, 0 insertions, 0 deletions