diff options
author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2019-11-15 15:55:51 +0300 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2019-11-21 16:28:32 +0300 |
commit | 4e50573f39229d5e9c985fa3b4923a8b29619ade (patch) | |
tree | 967ccd75140761e19073b2051c4cac5aecd90d78 /lib/show_mem.c | |
parent | 3f86a7e090d1dfb974a9dc9d44049f9bff01e6a5 (diff) | |
download | linux-4e50573f39229d5e9c985fa3b4923a8b29619ade.tar.xz |
gpio: mpc8xxx: Don't overwrite default irq_set_type callback
The per-SoC devtype structures can contain their own callbacks that
overwrite mpc8xxx_gpio_devtype_default.
The clear intention is that mpc8xxx_irq_set_type is used in case the SoC
does not specify a more specific callback. But what happens is that if
the SoC doesn't specify one, its .irq_set_type is de-facto NULL, and
this overwrites mpc8xxx_irq_set_type to a no-op. This means that the
following SoCs are affected:
- fsl,mpc8572-gpio
- fsl,ls1028a-gpio
- fsl,ls1088a-gpio
On these boards, the irq_set_type does exactly nothing, and the GPIO
controller keeps its GPICR register in the hardware-default state. On
the LS1028A, that is ACTIVE_BOTH, which means 2 interrupts are raised
even if the IRQ client requests LEVEL_HIGH. Another implication is that
the IRQs are not checked (e.g. level-triggered interrupts are not
rejected, although they are not supported).
Fixes: 82e39b0d8566 ("gpio: mpc8xxx: handle differences between incarnations at a single place")
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Link: https://lore.kernel.org/r/20191115125551.31061-1-olteanv@gmail.com
Tested-by: Michael Walle <michael@walle.cc>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'lib/show_mem.c')
0 files changed, 0 insertions, 0 deletions