]> git.baikalelectronics.ru Git - kernel.git/commit
irqchip/renesas-intc-irqpin: Use wakeup_path i.s.o. explicit clock handling
authorGeert Uytterhoeven <geert+renesas@glider.be>
Mon, 12 Feb 2018 13:55:11 +0000 (14:55 +0100)
committerMarc Zyngier <marc.zyngier@arm.com>
Wed, 14 Mar 2018 11:11:15 +0000 (11:11 +0000)
commitb39abaf695b90beb39c114e9dced414e6aae960f
tree475b7ee90154d50886b5851d5a89e56f394a3879
parentf4dfb1d676d6a4fda593ab74403866ab8d9388a5
irqchip/renesas-intc-irqpin: Use wakeup_path i.s.o. explicit clock handling

Since commit 3363ec3a02d7dc10 ("irqchip: renesas-intc-irqpin: Add
minimal runtime PM support"), when an IRQ is used for wakeup, the INTC
block's module clock (if exists) 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-intc-irqpin.c