[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZmIt-3uiNedKxMkR@google.com>
Date: Thu, 6 Jun 2024 14:45:31 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: linux-kernel@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] linux/interrupt.h: allow "guard" notation to disable and
reenable IRQ
On Tue, Jun 04, 2024 at 01:55:34PM -0700, Dmitry Torokhov wrote:
> On Tue, Jun 04, 2024 at 08:51:06PM +0200, Thomas Gleixner wrote:
> > On Thu, May 30 2024 at 11:07, Dmitry Torokhov wrote:
> > > Drivers often need to first disable an interrupt, carry out some
> > > action, and then reenable the interrupt. Introduce support for the
> > > "guard" notation for this so that the following is possible:
> > >
> > > ...
> > >
> > > scoped_cond_guard(mutex_intr, return -EINTR, &data->sysfs_mutex) {
> > > guard(disable_irq)(&client->irq);
> > >
> > > error = elan_acquire_baseline(data);
> > > if (error)
> > > return error;
> > > }
> > >
> > > ...
> > >
> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
> >
> > I assume you want to carry this through the input tree, so you can
> > modify the drivers.
> >
> > If so:
> >
> > Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
>
> Thanks Thomas. I'll stick this patch into an immutable branch off v6.9
> in case you (or someone else) wants to pull it in and start using it.
I made:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git ib/6.9-disable-irq-guard
Thanks.
--
Dmitry
Powered by blists - more mailing lists