diff options
author | Stefan Agner <stefan.agner@toradex.com> | 2016-11-23 16:14:23 -0800 |
---|---|---|
committer | Stefan Agner <stefan.agner@toradex.com> | 2016-11-23 16:35:17 -0800 |
commit | 5b2250b30d5c1178b552d7609a7853805b094e64 (patch) | |
tree | b187bebc7a4109343ae6bb4013ba3ca7304bbe2c | |
parent | 84f84c490be146cb6078a0d31816a0a8e50022c6 (diff) |
gpio: mxc: clear interrupt mask/status optionally
Add a kernel parameter ("gpio-mxc.noclearirq") to disable
unconditional interrupt mask/clearing. This is useful when a
second CPU (the Cortex-M4) is accessing the same GPIO bank.
Using the same GPIO bank from the Cortex-A7 and M4 sounds risky,
but it seems to work quite well. Most registers are write only
(e.g. interrupt status register can be cleared with a single
write), which makes them safe for concurrent access. However,
sharing a single GPIO bank between two cores does not allow to
use the Resource Domain Controller. Hence for secure applications
assigning a dedicated GPIO bank is still preferable.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
-rw-r--r-- | drivers/gpio/gpio-mxc.c | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/drivers/gpio/gpio-mxc.c b/drivers/gpio/gpio-mxc.c index 9f7446a7ac64..53ee7a8dcc5a 100644 --- a/drivers/gpio/gpio-mxc.c +++ b/drivers/gpio/gpio-mxc.c @@ -35,6 +35,10 @@ #include <linux/module.h> #include <asm-generic/bug.h> +static bool noclearirq = false; +module_param(noclearirq, bool, 0); +MODULE_PARM_DESC(noclearirq, "do not clear IRQ mask/status on probe"); + enum mxc_gpio_hwtype { IMX1_GPIO, /* runs on i.mx1 */ IMX21_GPIO, /* runs on i.mx21 and i.mx27 */ @@ -425,8 +429,10 @@ static int mxc_gpio_probe(struct platform_device *pdev) return port->irq; /* disable the interrupt and clear the status */ - writel(0, port->base + GPIO_IMR); - writel(~0, port->base + GPIO_ISR); + if (!noclearirq) { + writel(0, port->base + GPIO_IMR); + writel(~0, port->base + GPIO_ISR); + } if (mxc_gpio_hwtype == IMX21_GPIO) { /* |