[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260122162206.9wrHkrTZ@linutronix.de>
Date: Thu, 22 Jan 2026 17:22:06 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Marek Vasut <marek.vasut+renesas@...lbox.org>
Cc: linux-input@...r.kernel.org,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Cheng-Yang Chou <yphbchou0911@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Frank Li <Frank.Li@....com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Jinjie Ruan <ruanjinjie@...wei.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>,
Marc Zyngier <maz@...nel.org>, Thomas Gleixner <tglx@...nel.org>,
linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH 1/2] linux/interrupt.h: allow "guard" notation to disable
and reenable IRQ with valid IRQ check
On 2026-01-22 00:23:47 [+0100], Marek Vasut wrote:
> @@ -242,6 +242,21 @@ extern void irq_wake_thread(unsigned int irq, void *dev_id);
> DEFINE_LOCK_GUARD_1(disable_irq, int,
> disable_irq(*_T->lock), enable_irq(*_T->lock))
>
> +static inline void disable_valid_irq(unsigned int irq)
> +{
> + if (irq > 0)
> + disable_irq(irq);
> +}
| $ grep " 0:" /proc/interrupts
| 0: 43 0 IO-APIC 2-edge timer
in other words, interrupt 0 is valid.
Sebastian
Powered by blists - more mailing lists