summaryrefslogtreecommitdiffstats
path: root/drivers/irqchip/irq-zevio.c
diff options
context:
space:
mode:
authorGeert Uytterhoeven2018-02-12 14:55:12 +0100
committerMarc Zyngier2018-03-14 12:11:21 +0100
commit734e036a9e1052da0b4b22bc320f6b30964e346d (patch)
tree081e3ec62c65791e8e3c23a223a4f2c20f79bd87 /drivers/irqchip/irq-zevio.c
parentirqchip/renesas-intc-irqpin: Use wakeup_path i.s.o. explicit clock handling (diff)
downloadkernel-qcow2-linux-734e036a9e1052da0b4b22bc320f6b30964e346d.tar.gz
kernel-qcow2-linux-734e036a9e1052da0b4b22bc320f6b30964e346d.tar.xz
kernel-qcow2-linux-734e036a9e1052da0b4b22bc320f6b30964e346d.zip
irqchip/renesas-irqc: Use wakeup_path i.s.o. explicit clock handling
Since commit 6f46aedb9c85873b ("irqchip: renesas-irqc: Add wake-up support"), when an IRQ is used for wakeup, the INTC block's module clock is manually kept running during system suspend, to make sure the device stays active. However, this explicit clock handling is merely a workaround for a failure to properly communicate wakeup information to the device core. Instead, set the device's power.wakeup_path field, to indicate this device is part of the wakeup path. Depending on the PM Domain's active_wakeup configuration, the genpd core code will keep the device enabled (and the clock running) during system suspend when needed. This allows for the removal of all explicit clock handling code from the driver. Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'drivers/irqchip/irq-zevio.c')
0 files changed, 0 insertions, 0 deletions