From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: longzhao@ambarella.com
Cc: Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Michael Walle <mwalle@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Long Zhao <zl020895@163.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v10 6/8] gpio: pl061: use cleanup helpers for locks
Date: Thu, 15 Oct 2026 22:31:50 +0300 [thread overview]
Message-ID: <atEqJqIWsZYd750M@ashevche-desk.local> (raw)
In-Reply-To: <20261015-cv75-gpio-v10-6-3fe3eb315a55@ambarella.com>
On Thu, Oct 15, 2026 at 06:53:33PM +0800, Long Zhao via B4 Relay wrote:
> Convert raw_spinlock critical sections to guard() from cleanup.h.
guard()()
...
> @@ -270,9 +265,9 @@ static void pl061_irq_mask(struct irq_data *d)
> struct pl061 *pl061 = gpiochip_get_data(gc);
> u8 mask = BIT(irqd_to_hwirq(d) % PL061_GPIO_NR);
>
> - raw_spin_lock(&pl061->lock);
> + guard(raw_spinlock)(&pl061->lock);
Should be scoped_guard() in this case.
> regmap_clear_bits(pl061->regmap, GPIOIE, mask);
> - raw_spin_unlock(&pl061->lock);
>
> gpiochip_disable_irq(gc, d->hwirq);
> }
> @@ -285,9 +280,9 @@ static void pl061_irq_unmask(struct irq_data *d)
>
> gpiochip_enable_irq(gc, d->hwirq);
>
> - raw_spin_lock(&pl061->lock);
> + guard(raw_spinlock)(&pl061->lock);
> +
> regmap_set_bits(pl061->regmap, GPIOIE, mask);
> - raw_spin_unlock(&pl061->lock);
> }
Otherwise will be asymmetric with the unmask().
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-15 19:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 10:53 [PATCH v10 0/8] gpio: add Ambarella CV75 PL061 support Long Zhao via B4 Relay
2026-10-15 10:53 ` [PATCH v10 1/8] dt-bindings: gpio: pl061: add Ambarella CV75 variant Long Zhao via B4 Relay
2026-10-16 13:24 ` Linus Walleij
2026-10-15 10:53 ` [PATCH v10 2/8] gpiolib: regmap: add GPIO_REGMAP_QUIRK_SET_AFTER_DIR Long Zhao via B4 Relay
2026-10-16 13:25 ` Linus Walleij
2026-10-15 10:53 ` [PATCH v10 3/8] gpio: pl061: drop redundant pending check in the IRQ handler Long Zhao via B4 Relay
2026-10-15 19:21 ` Andy Shevchenko
2026-10-16 13:29 ` Linus Walleij
2026-10-15 10:53 ` [PATCH v10 4/8] gpio: pl061: convert register access to regmap Long Zhao via B4 Relay
2026-10-15 19:28 ` Andy Shevchenko
2026-10-15 10:53 ` [PATCH v10 5/8] gpio: pl061: use IRQ_TYPE_LEVEL_MASK and IRQ_TYPE_EDGE_BOTH Long Zhao via B4 Relay
2026-10-15 10:53 ` [PATCH v10 6/8] gpio: pl061: use cleanup helpers for locks Long Zhao via B4 Relay
2026-10-15 19:31 ` Andy Shevchenko [this message]
2026-10-15 10:53 ` [PATCH v10 7/8] gpio: pl061: switch data path to gpio-regmap Long Zhao via B4 Relay
2026-10-15 19:48 ` Andy Shevchenko
2026-10-15 10:53 ` [PATCH v10 8/8] gpio: pl061: add Ambarella register-layout variant Long Zhao via B4 Relay
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=atEqJqIWsZYd750M@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longzhao@ambarella.com \
--cc=mwalle@kernel.org \
--cc=robh@kernel.org \
--cc=zl020895@163.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
all inboxes | Powered by JetHome®