diff options
author | 2013-11-26 21:40:09 +0200 | |
---|---|---|
committer | 2013-12-26 00:02:11 +0530 | |
commit | 0d978eb7349941139241a99acf05de6dd49b78d1 (patch) | |
tree | 777d7403c8ca1589790c85ff716848ff10404c91 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | gpio: davinci: add OF support (diff) | |
download | linux-dev-0d978eb7349941139241a99acf05de6dd49b78d1.tar.xz linux-dev-0d978eb7349941139241a99acf05de6dd49b78d1.zip |
gpio: davinci: use chained_irq_enter/chained_irq_exit API
It's unsafe to call IRQ chip callbacks (.irq_mask/irq_unmask/irq_ack)
from chained IRQ handler directly. Because, Davinci GPIO block is used
by different SoCs, which, in turn, have different Main IRQ controllers
(Davinci - aintc, cp-intc; Keystone - arm-gic) which may introduce
diffrent set of IRQ chip callbacks. As result, call of
gpio_irq_handler() on Keysone will simply cause crash the system,
because ARM-GIC implements .irq_eoi() instead of .irq_ack().
Hence, fix it by using Kernel chained_irq_enter/chained_irq_exit APIs as
they are intended to handle exact such cases.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions