From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-kernel@vger.kernel.org, Doug Berger <opendmb@gmail.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Christophe Leroy <chleroy@kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/3] gpio: brcmstb: implement irq_mask_ack
Date: Thu, 22 Jan 2026 11:17:24 -0800 [thread overview]
Message-ID: <cb4ef2ed-ba94-4475-b02a-5b6e39943e81@broadcom.com> (raw)
In-Reply-To: <CAHp75Vc=ejHPwA05MHBxJQdJWv49pcuTNax0VikXruvwVM+Y9A@mail.gmail.com>
On 1/21/2026 11:36 PM, Andy Shevchenko wrote:
> On Thu, Jan 22, 2026 at 3:06 AM Florian Fainelli
> <florian.fainelli@broadcom.com> wrote:
>>
>> From: Doug Berger <opendmb@gmail.com>
>>
>> The irq_mask_ack operation is slightly more efficient than doing
>> irq_mask and irq_ack separately.
>
> I would refer to the callbacks as
>
> .irq_mask()
> .irq_ack()
>
> et cetera.
Ack.
>
>> More importantly for this driver it bypasses the check of
>> irqd_irq_masked ensuring a previously masked but still active
>> interrupt gets remasked if unmasked at the hardware level. This
>> allows the driver to more efficiently unmask the wake capable
>> interrupts when quiescing without needing to enable the irqs
>> individually to clear the irqd_irq_masked state.
>
> ...
>
>> -// Copyright (C) 2015-2017 Broadcom
>> +// Copyright (C) 2015-2026 Broadcom
>
> Shouldn't it be rather 2015-2017,2026 ? (In one case when I updated a
> driver for Intel, I went via Git history to gather the info.)
Ack.
>
> ...
>
>> static void brcmstb_gpio_set_imask(struct brcmstb_gpio_bank *bank,
>> - unsigned int hwirq, bool enable)
>> + unsigned int hwirq, bool enable, bool ack)
>
> This type of interface is usually discouraged as it makes code harder
> to read and follow. Since there are a lot of duplication, I recommend
> to move the ack op to a separate helper.
Good point, knowing the order and what set in those parameters can be
confusing.
>
> ...
>
>> - gpio_generic_write_reg(&bank->chip,
>> - priv->reg_base + GIO_MASK(bank->id), imask);
>> + if (ack)
>> + gpio_generic_write_reg(&bank->chip,
>> + priv->reg_base + GIO_MASK(bank->id),
>> + imask);
>
> Id est this piece...
>
>
>
>> +static void brcmstb_gpio_irq_mask_ack(struct irq_data *d)
>> +{
>> + struct gpio_chip *gc = irq_data_get_irq_chip_data(d);
>> + struct brcmstb_gpio_bank *bank = gpiochip_get_data(gc);
>> +
>> + brcmstb_gpio_set_imask(bank, d->hwirq, false, true);
>
> ...and call it here explicitly (seems the only place for it, so it can
> even be just moved here without an intermediate helper).
Will do, thanks!
--
Florian
next prev parent reply other threads:[~2026-01-22 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 1:05 [PATCH 0/3] gpio: brcmstb: Bug fixes and wake-up interrupt improvements Florian Fainelli
2026-01-22 1:05 ` [PATCH 1/3] gpio: brcmstb: correct hwirq to bank map Florian Fainelli
2026-01-22 1:05 ` [PATCH 2/3] gpio: brcmstb: implement irq_mask_ack Florian Fainelli
2026-01-22 7:36 ` Andy Shevchenko
2026-01-22 19:17 ` Florian Fainelli [this message]
2026-01-22 19:26 ` Florian Fainelli
2026-01-23 19:01 ` Florian Fainelli
2026-01-22 1:05 ` [PATCH 3/3] gpio: brcmstb: allow parent_irq to wake Florian Fainelli
2026-01-22 7:42 ` Andy Shevchenko
2026-01-22 19:24 ` Florian Fainelli
2026-01-26 16:26 ` Andy Shevchenko
2026-01-22 7:44 ` Andy Shevchenko
2026-01-22 7:45 ` Andy Shevchenko
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=cb4ef2ed-ba94-4475-b02a-5b6e39943e81@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=brgl@kernel.org \
--cc=chleroy@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=opendmb@gmail.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