[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VeW6EWrGPbzBrSPry9Lb8GDvA-C-mkCvmJMTVPeeVxjKg@mail.gmail.com>
Date: Tue, 9 Feb 2021 14:46:19 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Nikita Shubin <nikita.shubin@...uefel.me>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Alexander Sverdlin <alexander.sverdlin@...il.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 2/7] gpio: ep93xx: Fix single irqchip with multi gpiochips
On Tue, Feb 9, 2021 at 2:35 PM Nikita Shubin <nikita.shubin@...uefel.me> wrote:
> On Monday, 8 February 2021 16:20:17 MSK Andy Shevchenko wrote:
> >On Mon, Feb 8, 2021 at 11:00 AM Nikita Shubin
> <nikita.shubin@...uefel.me> wrote:
...
> >> +static void ep93xx_init_irq_chip(struct device *dev, struct irq_chip
> >> *ic, const char *label) +{
> >>
> >> + ic->name = devm_kasprintf(dev, GFP_KERNEL, "gpio-irq-%s",
> >> label);
> >Is the label being NULL okay?
>
> The label is taken from ep93xx_gpio_banks[], so unless we explicitly
> pass zero to ep93xx_init_irq_chip(), we are ok.
Maybe I was unclear, let me rephrase: Is the *resulting* label being NULL okay?
> >> + ic->irq_ack = ep93xx_gpio_irq_ack;
> >> + ic->irq_mask_ack = ep93xx_gpio_irq_mask_ack;
> >> + ic->irq_mask = ep93xx_gpio_irq_mask;
> >> + ic->irq_unmask = ep93xx_gpio_irq_unmask;
> >> + ic->irq_set_type = ep93xx_gpio_irq_type;
> >> +}
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists