From: Hans Ulli Kroll <ulli.kroll@googlemail.com>
To: Russell King <rmk+kernel@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-tegra@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Alexandre Courbot <gnurou@gmail.com>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
Jason Cooper <jason@lakedaemon.net>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH 4/9] ARM: gemini: fix race in installing GPIO chained IRQ handler
Date: Wed, 17 Jun 2015 19:23:14 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1506171923010.27619@T520.local> (raw)
In-Reply-To: <E1Z4z07-0002SO-Gv@rmk-PC.arm.linux.org.uk>
On Tue, 16 Jun 2015, Russell King wrote:
> The gemini code was installing its chained interrupt handler (which
> enables the interrupt) before it was setting its data, which is bad if
> the IRQ was previously pending. Avoid this problem by converting it to
> irq_set_chained_handler_and_data().
>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
> Depends on patch 1.
>
> arch/arm/mach-gemini/gpio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-gemini/gpio.c b/arch/arm/mach-gemini/gpio.c
> index f8cb5710d6ee..3292f2e6ed6f 100644
> --- a/arch/arm/mach-gemini/gpio.c
> +++ b/arch/arm/mach-gemini/gpio.c
> @@ -223,8 +223,8 @@ void __init gemini_gpio_init(void)
> set_irq_flags(j, IRQF_VALID);
> }
>
> - irq_set_chained_handler(IRQ_GPIO(i), gpio_irq_handler);
> - irq_set_handler_data(IRQ_GPIO(i), (void *)i);
> + irq_set_chained_handler_and_data(IRQ_GPIO(i), gpio_irq_handler,
> + (void *)i);
> }
>
> BUG_ON(gpiochip_add(&gemini_gpio_chip));
> --
> 2.1.0
>
>
Acked-by: Hans Ulli Kroll <ulli.kroll@googlemail.com>
prev parent reply other threads:[~2015-06-17 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 22:06 [PATCH 4/9] ARM: gemini: fix race in installing GPIO chained IRQ handler Russell King
2015-06-17 17:23 ` Hans Ulli Kroll [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1506171923010.27619@T520.local \
--to=ulli.kroll@googlemail.com \
--cc=gnurou@gmail.com \
--cc=jason@lakedaemon.net \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox