aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/crypto/Makefile
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ti.com>2014-04-11 06:49:55 -0400
committerTomi Valkeinen <tomi.valkeinen@ti.com>2014-04-14 07:52:08 -0400
commit0925afc9a4851c2592f1d45a17aeb7e1ffe188b7 (patch)
tree7576e5c2f5a97af7ca972d45123fad18d90a6fc3 /drivers/crypto/Makefile
parent25e475e11d8acff1b7c2febbf1d170e95033ba2e (diff)
OMAPDSS: fix shared irq handlers
DSS uses shared irq handlers for DISPC and DSI, because on OMAP3, the DISPC and DSI share the same irq line. However, the irq handlers presume that the hardware is enabled, which, in theory, may not be the case with shared irq handlers. So if an interrupt happens while the DISPC/DSI is off, the kernel will halt as the irq handler tries to access the DISPC/DSI registers. In practice that should never happen, as both DSI and DISPC are in the same power domain. So if there's an IRQ for one of them, the other is also enabled. However, if CONFIG_DEBUG_SHIRQ is enabled, the kernel will generate a spurious IRQ, which then causes the problem. This patch adds an is_enabled field for both DISPC and DSI, which is used to track if the HW is enabled. For DISPC the code is slightly more complex, as the users of DISPC can register the interrupt handler, and we want to hide the is_enabled handling from the users of DISPC. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'drivers/crypto/Makefile')
0 files changed, 0 insertions, 0 deletions