From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
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:49:11 +0000 [thread overview]
Message-ID: <c4e71b60-0aac-44bc-bdf1-13ec1df3e8da@opensource.cirrus.com> (raw)
In-Reply-To: <20260121115723.oVTfTOS5@linutronix.de>
On 21/01/2026 11:57 am, Sebastian Andrzej Siewior wrote:
> On 2026-01-21 11:53:28 [+0000], Richard Fitzgerald wrote:
>> Ah. I didn't notice that. Confusing error message. It says
>> "handler=NULL" but handler != NULL. More like "handler=default".
>
> The supplied argument was NULL.
> Anyway. Do you happen to have an answer to my original question.
>
> Sebastian
Afraid I'm not familiar with the WM8350.
But I note that call is not registering against a real interrupt pin.
It's registering against a virtual irqchip that is itself a threaded
IRQ handler. Maybe that makes a difference. That top-level virtual IRQ
handler is ONESHOT.
next prev parent reply other threads:[~2026-01-21 12:49 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
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 [this message]
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=c4e71b60-0aac-44bc-bdf1-13ec1df3e8da@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@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