[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f1f8125f-1139-4fc5-b0c7-a3123758c9de@sirena.org.uk>
Date: Wed, 21 Jan 2026 15:03:58 +0000
From: Mark Brown <broonie@...nel.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Richard Fitzgerald <rf@...nsource.cirrus.com>,
patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org,
Lee Jones <lee@...nel.org>
Subject: Re: request_irq() usage in wm8350_register_irq().
On Wed, Jan 21, 2026 at 02:45:08PM +0100, Sebastian Andrzej Siewior wrote:
> On 2026-01-21 13:37:09 [+0000], Mark Brown wrote:
> > The chip is only accessable via I2C or SPI so the primary interrupt
> > handler is itself always running and reporting child interrupts in
> > threaded context. They can't really deliver a hardirq context
> > interrupt.
> In that case it lacks the needed IRQF_ONEHOST flag and nobody noticed
> that request_irq() fails for a few years now. I add a patch to my
> stackā¦
Thanks.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists