summaryrefslogtreecommitdiff
path: root/certs
diff options
context:
space:
mode:
authorDoug Berger <opendmb@gmail.com>2017-10-24 12:54:47 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-11-21 09:24:17 +0100
commitdabaf70e3ad6ec7d327bfa98916163985a103e4a (patch)
treea206f839a7c8b79061bee3719620f60ff342d66d /certs
parenta8ba76fc043e1a34e98055f6e818c67ddc3c05c2 (diff)
downloadlinux-exynos-dabaf70e3ad6ec7d327bfa98916163985a103e4a.tar.gz
linux-exynos-dabaf70e3ad6ec7d327bfa98916163985a103e4a.tar.bz2
linux-exynos-dabaf70e3ad6ec7d327bfa98916163985a103e4a.zip
gpio: brcmstb: release the bgpio lock during irq handlers
commit 142c168e0e50164e67c9399c28dedd65a307cfe5 upstream. The basic memory-mapped GPIO controller lock must be released before calling the registered GPIO interrupt handlers to allow the interrupt handlers to access the hardware. Examples of why a GPIO interrupt handler might want to access the GPIO hardware include an interrupt that is configured to trigger on rising and falling edges that needs to read the current level of the input to know how to respond, or an interrupt that causes a change in a GPIO output in the same bank. If the lock is not released before enterring the handler the hardware accesses will deadlock when they attempt to grab the lock. Since the lock is only needed to protect the calculation of unmasked pending interrupts create a dedicated function to perform this and hide the complexity. Fixes: 19a7b6940b78 ("gpio: brcmstb: Add interrupt and wakeup source support") Signed-off-by: Doug Berger <opendmb@gmail.com> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com> Acked-by: Gregory Fong <gregory.0xf0@gmail.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions