diff options
author | Strashko, Grygorii <grygorii.strashko@ti.com> | 2016-12-09 00:33:10 +0100 |
---|---|---|
committer | Jason Cooper <jason@lakedaemon.net> | 2016-12-31 19:41:45 +0100 |
commit | 2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1 (patch) | |
tree | 3cfc3afc1b2ab7947e20af088cfbf5735b24fd2e /drivers/irqchip/irq-gic-v3-its-pci-msi.c | |
parent | Linux 4.10-rc1 (diff) | |
download | linux-2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1.tar.xz linux-2f884e6e688a0deb69e6c9552e51aef8b7e3f5f1.zip |
irqchip/keystone: Fix "scheduling while atomic" on rt
The below call chain generates "scheduling while atomic" backtrace and
causes system crash when Keystone 2 IRQ chip driver is used with RT-kernel:
gic_handle_irq()
|-__handle_domain_irq()
|-generic_handle_irq()
|-keystone_irq_handler()
|-regmap_read()
|-regmap_lock_spinlock()
|-rt_spin_lock()
The reason is that Keystone driver dispatches IRQ using chained IRQ handler
and accesses I/O memory through syscon->regmap(mmio) which is implemented
as fast_io regmap and uses regular spinlocks for synchronization, but
spinlocks transformed to rt_mutexes on RT.
Hence, convert Keystone 2 IRQ driver to use generic irq handler instead of
chained IRQ handler. This way it will be compatible with RT kernel where it
will be forced thread IRQ handler while in non-RT kernel it still will be
executed in HW IRQ context.
Cc: Suman Anna <s-anna@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Tested-by: Suman Anna <s-anna@ti.com>
Link: https://lkml.kernel.org/r/20161208233310.10329-1-grygorii.strashko@ti.com
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'drivers/irqchip/irq-gic-v3-its-pci-msi.c')
0 files changed, 0 insertions, 0 deletions