diff options
author | Russell King <[email protected]> | 2019-04-10 12:51:13 -0700 |
---|---|---|
committer | Linus Walleij <[email protected]> | 2019-04-11 15:16:26 +0200 |
commit | 044e499acd1587e01bdd3434b3e5a1869ea26fdd (patch) | |
tree | 24b2ebb421875b8fe430477899576911416b38f0 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | e6818d29ea1591b3e37d9cf635dc9dbca1a398ae (diff) |
gpio: gpio-omap: Remove conditional pm_runtime handling for GPIO interrupts
Commit b764a5863fd8 ("gpio: omap: Remove custom PM calls and use cpu_pm
instead") moved interrupt using GPIO banks to idle with cpu_pm in order
to drop the use of pm_runtime_irq_safe() in a later patch. The GPIO
banks with no interrupts claimed are still being idled based on PM
runtime calls. However this caused a regression for am437x suspend for
rtc+ddr idle mode where the device cannot enter idle state as reported
by Keerthy <[email protected]>.
To fix the issue, we must not fail the pm_runtime callbacks. For GPIO
interrupts, we already have irq_chip_pm_get increment the PM runtime
use count as pointed out by Grygorii Strashko <[email protected]>.
So all we need to do is remove the conditional handling in the
runtime_suspend and resume functions and let the CPU PM notifier idle
the GPIO banks.
Cc: Aaro Koskinen <[email protected]>
Cc: Grygorii Strashko <[email protected]>
Cc: Keerthy <[email protected]>
Cc: Peter Ujfalusi <[email protected]>
Cc: Tero Kristo <[email protected]>
Fixes: b764a5863fd8 ("gpio: omap: Remove custom PM calls and use cpu_pm instead")
Reported-by: Keerthy <[email protected]>
Signed-off-by: Russell King <[email protected]>
[[email protected]: updated patch description, dropped runtime count changes]
Signed-off-by: Tony Lindgren <[email protected]>
Tested-by: Keerthy <[email protected]>
Reviewed-by: Keerthy <[email protected]>
Signed-off-by: Linus Walleij <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions