irqchip/renesas-irqc: Use wakeup_path i.s.o. explicit clock handling
authorGeert Uytterhoeven <geert+renesas@glider.be>
Mon, 12 Feb 2018 13:55:12 +0000 (14:55 +0100)
committerMarc Zyngier <marc.zyngier@arm.com>
Wed, 14 Mar 2018 11:11:21 +0000 (11:11 +0000)
commit734e036a9e1052da0b4b22bc320f6b30964e346d
tree081e3ec62c65791e8e3c23a223a4f2c20f79bd87
parent66bf8252cf0d79ba693183d6b858885a19825d10
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>
drivers/irqchip/irq-renesas-irqc.c