diff options
author | Geert Uytterhoeven <geert+renesas@glider.be> | 2014-09-23 16:21:58 +0400 |
---|---|---|
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2014-09-30 14:42:13 +0400 |
commit | a00d91ea264f974b3d57babce143ba157921629a (patch) | |
tree | 6a379687526afecf02b932d0064896f34ca6e453 /drivers/video/fbdev/atmel_lcdfb.c | |
parent | 5b789da8a7fc357661fc61faaf853e9161cc9700 (diff) | |
download | linux-a00d91ea264f974b3d57babce143ba157921629a.tar.xz |
fbdev: sh_mobile_hdmi: Re-init regs before irq re-enable on resume
When the PM domain containing the HDMI hardware block is powered down,
the HDMI register values (incl. interrupt polarity settings) are lost.
During resume, after powering up the PM domain, interrupts are
re-enabled, and an interrupt storm happens due to incorrect interrupt
polarity settings:
irq 163: nobody cared (try booting with the "irqpoll" option)
...
Disabling IRQ #163
To fix this, re-initialize the interrupt polarity settings, and the
htop1 register block (if present), during resume.
As the .suspend_noirq() and .resume_noirq() callbacks are not called
when using the generic PM domain, the normal .resume() callback is used,
and the device interrupt needs to be disabled/enabled manually.
This fixes resume from s2ram with power down of the A4MP PM domain on
r8a7740/Armadillo.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'drivers/video/fbdev/atmel_lcdfb.c')
0 files changed, 0 insertions, 0 deletions