From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
Lee Jones <lee@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: request_irq() usage in wm8350_register_irq().
Date: Wed, 21 Jan 2026 12:36:59 +0100 [thread overview]
Message-ID: <20260121113659.CCJtYuQS@linutronix.de> (raw)
In-Reply-To: <fbd0ffc0-d308-4064-893b-3c1b51a13a35@opensource.cirrus.com>
On 2026-01-21 11:22:32 [+0000], Richard Fitzgerald wrote:
> Or because request_threaded_irq() supplies a default handler, so
> handler!=NULL when it calls __setup_irq().
>
>
> int request_threaded_irq(unsigned int irq, irq_handler_t handler,
> irq_handler_t thread_fn, unsigned long irqflags,
> const char *devname, void *dev_id)
> {
>
> ...
>
> if (!handler) {
> if (!thread_fn)
> return -EINVAL;
> handler = irq_default_primary_handler;
> }
>
> ...
>
>
> retval = __setup_irq(irq, desc, action);
>
> ...
> }
->
| } else if (new->handler == irq_default_primary_handler &&
| !(desc->irq_data.chip->flags & IRQCHIP_ONESHOT_SAFE)) {
…
| pr_err("Threaded irq requested with handler=NULL and !ONESHOT for %s (irq %d)\n",
| new->name, irq);
| ret = -EINVAL;
Sebastian
next prev parent reply other threads:[~2026-01-21 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:16 Sebastian Andrzej Siewior
2026-01-21 11:22 ` Richard Fitzgerald
2026-01-21 11:36 ` Sebastian Andrzej Siewior [this message]
2026-01-21 11:53 ` Richard Fitzgerald
2026-01-21 11:57 ` Sebastian Andrzej Siewior
2026-01-21 12:43 ` Andy Shevchenko
2026-01-21 13:12 ` Mark Brown
2026-01-21 13:18 ` Sebastian Andrzej Siewior
2026-01-21 13:37 ` Mark Brown
2026-01-21 13:45 ` Sebastian Andrzej Siewior
2026-01-21 15:03 ` Mark Brown
2026-01-21 13:20 ` Andy Shevchenko
2026-01-21 12:49 ` Richard Fitzgerald
2026-01-21 13:28 ` Charles Keepax
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=20260121113659.CCJtYuQS@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.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
Powered by JetHome