[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75VeCsbSe1knoDwjMjjg-YAK2K_RwV_giRt=H9VG-KwmQGQ@mail.gmail.com>
Date: Wed, 15 Feb 2023 13:51:04 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Alexander Stein <alexander.stein@...tq-group.com>,
Bartosz Golaszewski <brgl@...ev.pl>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] gpio: vf610: make irq_chip immutable
On Wed, Feb 15, 2023 at 12:18 PM Linus Walleij <linus.walleij@...aro.org> wrote:
> On Tue, Feb 14, 2023 at 11:52 AM <andy.shevchenko@...il.com> wrote:
> > Tue, Feb 14, 2023 at 08:36:38AM +0100, Alexander Stein kirjoitti:
> > > Since recently, the kernel is nagging about mutable irq_chips:
> > >
> > > "not an immutable chip, please consider fixing it!"
> > >
> > > Drop the unneeded copy, flag it as IRQCHIP_IMMUTABLE, add the new
> > > helper functions and call the appropriate gpiolib functions.
> >
> > ...
> >
> > > The overall changes are based on commit f1138dacb7ff
> > > ("gpio: sch: make irq_chip immutable")
> >
> > Nice, but you forgot one crucial detail. You need to mark GPIO resuested
> > whenever it's locked as IRQ and otherwise when unlocked.
>
> +static const struct irq_chip vf610_irqchip = {
> (...)
> + GPIOCHIP_IRQ_RESOURCE_HELPERS,
>
> That's what this macro does ;)
Maybe I was unclear, but I meant that the above mentioned macro
requires to have the helpers to be called to enable the GPIO line.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists