[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260129161215.03f71a7f@jic23-huawei>
Date: Thu, 29 Jan 2026 16:12:15 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: linux-kernel@...r.kernel.org, "Thomas Gleixner" <tglx@...nel.org>, Andy
Shevchenko <andriy.shevchenko@...el.com>, Marcus Folkesson
<marcus.folkesson@...il.com>, Lars-Peter Clausen <lars@...afoo.de>, Michael
Hennerich <Michael.Hennerich@...log.com>, Puranjay Mohan
<puranjay@...nel.org>, David Lechner <dlechner@...libre.com>, Nuno
Sá <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
Marcelo Schmitt <marcelo.schmitt@...log.com>, Kent Gustavsson
<kent@...oris.se>, Gustavo Silva <gustavograzs@...il.com>, Nishant Malpani
<nish.malpani25@...il.com>, linux-iio@...r.kernel.org
Subject: Re: [PATCH v2 17/20] iio: Replace IRQF_ONESHOT with IRQF_NO_THREAD
On Wed, 28 Jan 2026 10:55:37 +0100
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> Passing IRQF_ONESHOT ensures that the interrupt source is masked until
> the secondary (threaded) handler is done. If only a primary handler is
> used then the flag makes no sense because the interrupt can not fire
> (again) while its handler is running.
> The flag also disallows force-threading of the primary handler and the
> irq-core will warn about this.
>
> The intention here was probably not allowing forced-threading for
> handlers such as iio_trigger_generic_data_rdy_poll() will intends to
> invoke hard-interrupt handlers.
>
> Replace IRQF_ONESHOT with IRQF_NO_THREAD.
>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...el.com>
> Reviewed-by: Marcus Folkesson <marcus.folkesson@...il.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Applied
Thanks.
Powered by blists - more mailing lists