From: Sander Vanheule <sander@svanheule.net>
To: Michael Walle <mwalle@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sander Vanheule <sander@svanheule.net>
Subject: [RFC PATCH 0/2] gpio: regmap: Ensure writes for aliased data values
Date: Mon, 20 Oct 2025 13:56:34 +0200 [thread overview]
Message-ID: <20251020115636.55417-1-sander@svanheule.net> (raw)
These patches aim to fix an issue with aliased data registers, where the
input values are read from an offset and the output values are written
to the same offset. The current use of regmap_update_bits() may cause an
input value to be used to decide not to write a new output value.
The first patch in this RFC aims to fix the above issue. The second
patch is optional, but allows to recover some performance by leveraging
the regmap cache.
I am currently revisiting an older patch series of mine [1]. I am
submitting these as an RFC to see if they are acceptable, but would
include the patch(es) in the respin of the series.
[1] https://lore.kernel.org/linux-gpio/cover.1623532208.git.sander@svanheule.net/
Sander Vanheule (2):
gpio: regmap: Force writes for aliased data regs
gpio: regmap: Bypass cache for aliased outputs
drivers/gpio/gpio-regmap.c | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-20 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 11:56 Sander Vanheule [this message]
2025-10-20 11:56 ` [RFC PATCH 1/2] gpio: regmap: Force writes for aliased data regs Sander Vanheule
2025-10-20 13:02 ` Michael Walle
2025-10-20 13:25 ` Sander Vanheule
2025-10-20 14:07 ` Michael Walle
2025-10-21 7:33 ` Michael Walle
2025-10-21 9:00 ` Sander Vanheule
2025-10-20 11:56 ` [RFC PATCH 2/2] gpio: regmap: Bypass cache for aliased outputs Sander Vanheule
2025-10-21 7:18 ` Linus Walleij
2025-10-21 9:01 ` Sander Vanheule
2025-10-21 12:21 ` Bartosz Golaszewski
2025-10-21 12:56 ` Sander Vanheule
2025-10-21 7:38 ` Michael Walle
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=20251020115636.55417-1-sander@svanheule.net \
--to=sander@svanheule.net \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@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
all inboxes | Powered by JetHome®