From: Ryan Brue <ryanbrue.dev@gmail.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mark Brown <broonie@kernel.org>, Lee Jones <lee@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Sean Wang <sean.wang@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Bartosz Golaszewski <brgl@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Chaotian Jing <chaotian.jing@mediatek.com>,
Hongzhou Yang <hongzhou.yang@mediatek.com>,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rt-devel@lists.linux.dev, mfd@lists.linux.dev
Subject: Re: [PATCH] pinctrl: mediatek: common-v1: Use a raw spinlock for the pinctrl regmap
Date: Tue, 6 Oct 2026 19:57:01 -0500 [thread overview]
Message-ID: <d3d3e7b3-eb8b-456d-9a2c-116334e86c14@gmail.com> (raw)
In-Reply-To: <CAGXv+5FssQL3Go3VDFbLAT6HP12RS3U3OgxhYOeapzs64QTdUw@mail.gmail.com>
Hi Chen-Yu and Sebastian,
Thanks for looking at this.
On 9/30/26 3:17 AM, Chen-Yu Tsai wrote:
> The syscon node is the provider of the regmap. You need to fix it there,
> not duplicate it in the consumer.
Unless I'm misunderstanding, no driver binds to that node, so its regmap
comes from the generic syscon code, and changing it there would affect
every syscon. Lee, Arnd, Mark, would that be acceptable?
These are the options I see. Please let me know if there's a better one:
- Do what Sebastian suggested and make syscon use a raw spinlock, except
when the node has a clock, since regmap-mmio calls clk_enable() under
the lock. Off PREEMPT_RT, nothing changes. On RT the lock would no
longer be preemptible for most syscons, including across bulk writes.
Most syscon users that do bulk writes only write a few registers, but
enabling the Amlogic G12A PCIe PLL writes a sequence with 40 us of
udelay() under the lock.
- Have the pinctrl ioremap() the node a second time alongside syscon's
mapping and read the input register (DIN) with readl(). That read is the
only access the EINT code makes in raw context. This would go around the
syscon, and it requires that DIN never be written in a multi-step
sequence, which is currently the case.
I'd like to know the best approach before sending out a v2.
Best regards,
Ryan Brue
prev parent reply other threads:[~2026-10-07 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 17:57 Ryan Brue
2026-09-29 18:09 ` sashiko-bot
2026-09-30 8:06 ` Sebastian Andrzej Siewior
2026-09-30 8:17 ` Chen-Yu Tsai
2026-10-07 0:57 ` Ryan Brue [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=d3d3e7b3-eb8b-456d-9a2c-116334e86c14@gmail.com \
--to=ryanbrue.dev@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=chaotian.jing@mediatek.com \
--cc=clrkwllms@kernel.org \
--cc=hongzhou.yang@mediatek.com \
--cc=lee@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=linux-mediatek@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=mfd@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=sean.wang@kernel.org \
--cc=wenst@chromium.org \
--cc=yingjoe.chen@mediatek.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®