From: Marc Zyngier <maz@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH] gpio: tc3589x: Make irqchip immutable
Date: Mon, 26 Sep 2022 10:37:21 +0100 [thread overview]
Message-ID: <87sfkeo4ry.wl-maz@kernel.org> (raw)
In-Reply-To: <20220926093047.1699027-1-linus.walleij@linaro.org>
On Mon, 26 Sep 2022 10:30:47 +0100,
Linus Walleij <linus.walleij@linaro.org> wrote:
>
> This turns the Toshiba tc3589x gpio irqchip immutable.
>
> Cc: Marc Zyngier <maz@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> drivers/gpio/gpio-tc3589x.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/gpio-tc3589x.c b/drivers/gpio/gpio-tc3589x.c
> index 443fe975bf13..f9edb720710a 100644
> --- a/drivers/gpio/gpio-tc3589x.c
> +++ b/drivers/gpio/gpio-tc3589x.c
> @@ -244,13 +244,15 @@ static void tc3589x_gpio_irq_unmask(struct irq_data *d)
> tc3589x_gpio->regs[REG_DIRECT][regoffset] &= ~mask;
> }
>
> -static struct irq_chip tc3589x_gpio_irq_chip = {
> +static const struct irq_chip tc3589x_gpio_irq_chip = {
> .name = "tc3589x-gpio",
> .irq_bus_lock = tc3589x_gpio_irq_lock,
> .irq_bus_sync_unlock = tc3589x_gpio_irq_sync_unlock,
> .irq_mask = tc3589x_gpio_irq_mask,
> .irq_unmask = tc3589x_gpio_irq_unmask,
Don't you need to update these two methods with the callbacks into the
gpiolib core code?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-09-26 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 9:30 [PATCH] gpio: tc3589x: Make irqchip immutable Linus Walleij
2022-09-26 9:37 ` Marc Zyngier [this message]
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=87sfkeo4ry.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).