From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Yash Shah <yash.shah@sifive.com>,
"Wesley W . Terpstra" <wesley@sifive.com>,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH 1/2 v1] gpio: sifive: Set affinity callback to parent
Date: Tue, 6 Apr 2021 12:20:57 +0200 [thread overview]
Message-ID: <CAMuHMdUu2UpcbvNGuDfHAp+aFGkhMS4rJXLwiqQu6QFB+FytBw@mail.gmail.com> (raw)
In-Reply-To: <20201117213351.249668-1-linus.walleij@linaro.org>
Hi Linus,
On Tue, Nov 17, 2020 at 10:37 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> This assigns the .irq_set_affinity to the parent callback.
> I assume the sifive GPIO can be used in systems with
> SMP.
>
> I used the pattern making the hirerarchy tolerant for missing
> parent as in Marc's earlier patches.
>
> Cc: Yash Shah <yash.shah@sifive.com>
> Cc: Wesley W. Terpstra <wesley@sifive.com>
> Suggested-by: Marc Zyngier <maz@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Thanks for your patch!
> ---
> ChangeLog RFT->v1:
> - Make the affinity setting call return -EINVAL if there
> is no parent.
Would it make sense to incorporate this check into
irq_chip_set_affinity_parent(), so drivers can just point
.irq_set_affinity to the latter, without having to provide (duplicate)
the same wrapper over and over?
> - Real patch because now we believe in this
> ---
> drivers/gpio/gpio-sifive.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/gpio/gpio-sifive.c b/drivers/gpio/gpio-sifive.c
> index c54dd08f2cbf..485820e4488c 100644
> --- a/drivers/gpio/gpio-sifive.c
> +++ b/drivers/gpio/gpio-sifive.c
> @@ -128,6 +128,16 @@ static void sifive_gpio_irq_eoi(struct irq_data *d)
> irq_chip_eoi_parent(d);
> }
>
> +static int sifive_gpio_irq_set_affinity(struct irq_data *data,
> + const struct cpumask *dest,
> + bool force)
> +{
> + if (data->parent_data)
> + return irq_chip_set_affinity_parent(data, dest, force);
> +
> + return -EINVAL;
> +}
> +
> static struct irq_chip sifive_gpio_irqchip = {
> .name = "sifive-gpio",
> .irq_set_type = sifive_gpio_irq_set_type,
> @@ -136,6 +146,7 @@ static struct irq_chip sifive_gpio_irqchip = {
> .irq_enable = sifive_gpio_irq_enable,
> .irq_disable = sifive_gpio_irq_disable,
> .irq_eoi = sifive_gpio_irq_eoi,
> + .irq_set_affinity = sifive_gpio_irq_set_affinity,
> };
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-04-06 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 21:33 [PATCH 1/2 v1] gpio: sifive: Set affinity callback to parent Linus Walleij
2020-11-17 21:33 ` [PATCH 2/2 v1] gpio: tegra186: " Linus Walleij
2021-04-06 10:20 ` Geert Uytterhoeven [this message]
2021-04-06 10:40 ` [PATCH 1/2 v1] gpio: sifive: " Marc Zyngier
2021-04-06 10:51 ` Geert Uytterhoeven
2021-04-06 12:45 ` Marc Zyngier
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=CAMuHMdUu2UpcbvNGuDfHAp+aFGkhMS4rJXLwiqQu6QFB+FytBw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=maz@kernel.org \
--cc=wesley@sifive.com \
--cc=yash.shah@sifive.com \
/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).