From: Linus Walleij <linusw@kernel.org>
To: Martin Larsson <martin.larsson@actia.se>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Roth <mail@mroth.net>,
Francesco Lavra <flavra@baylibre.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Maria Garcia <mariagarcia7293@gmail.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Subject: Re: [PATCH] gpio: pca953x: mask interrupts in irq shutdown
Date: Tue, 27 Jan 2026 10:29:24 +0100 [thread overview]
Message-ID: <CAD++jLmOjdiDfLPqAA+6SmK2mfddh6O2YoPD10gkBbo=dCOf9Q@mail.gmail.com> (raw)
In-Reply-To: <20260121125631.2758346-1-martin.larsson@actia.se>
Add a few recent developers to CC, this is a very widely used GPIO chip.
Emanuele was dealing with IRQ storms and may want to look at this.
On Wed, Jan 21, 2026 at 2:12 PM Martin Larsson <martin.larsson@actia.se> wrote:
> In the existing implementation irq_shutdown does not mask the interrupts
> in hardware. This can cause spurious interrupts from the IO expander.
> Add masking to irq_shutdown to prevent spurious interrupts.
>
> Signed-off-by: Martin Larsson <martin.larsson@actia.se>
> ---
> drivers/gpio/gpio-pca953x.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
> index 8727ae54bc57..f93a3dbb2daa 100644
> --- a/drivers/gpio/gpio-pca953x.c
> +++ b/drivers/gpio/gpio-pca953x.c
> @@ -914,6 +914,8 @@ static void pca953x_irq_shutdown(struct irq_data *d)
> clear_bit(hwirq, chip->irq_trig_fall);
> clear_bit(hwirq, chip->irq_trig_level_low);
> clear_bit(hwirq, chip->irq_trig_level_high);
> +
> + pca953x_irq_mask(d);
It makes sense to me.
Reviewed-by: Linus Walleij <linusw@kernel.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2026-01-27 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 12:57 Martin Larsson
2026-01-27 9:29 ` Linus Walleij [this message]
2026-01-27 9:47 ` Emanuele Ghidoli
2026-01-27 9:35 ` Bartosz Golaszewski
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='CAD++jLmOjdiDfLPqAA+6SmK2mfddh6O2YoPD10gkBbo=dCOf9Q@mail.gmail.com' \
--to=linusw@kernel.org \
--cc=brgl@kernel.org \
--cc=emanuele.ghidoli@toradex.com \
--cc=flavra@baylibre.com \
--cc=hvilleneuve@dimonoff.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@mroth.net \
--cc=mariagarcia7293@gmail.com \
--cc=martin.larsson@actia.se \
/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
all inboxes | Powered by JetHome®