From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 1/7] regcache: extract locked helpers to replace open-coded lock/unlock pairs
Date: Wed, 30 Sep 2026 17:46:55 +0800 [thread overview]
Message-ID: <20260930-regmap-lock-2nd-v1-1-33a8a482f9ae@nxp.com> (raw)
In-Reply-To: <20260930-regmap-lock-2nd-v1-0-33a8a482f9ae@nxp.com>
From: Peng Fan <peng.fan@nxp.com>
The previous patch ("regcache: use the regmap scoped lock guard")
deliberately left regcache_init() with explicit map->lock()/unlock()
calls because the function has a goto err_* cleanup ladder and mixing
goto with cleanup helpers in the same function is discouraged by
cleanup.h.
Solve this by extracting two static helpers:
regcache_locked_op() - acquires the regmap lock via guard(regmap),
invokes an int-returning cache_ops callback
(init, populate), and returns its result.
Returns 0 when the callback is NULL.
regcache_locked_exit() - acquires the regmap lock via guard(regmap)
and invokes the void-returning exit
callback. Returns immediately when the
callback is NULL.
Because the lock scope is now entirely inside the helper functions,
it never crosses a goto target in the caller, so the cleanup.h
concern does not apply.
Convert all four remaining open-coded lock/unlock sites in
regcache_init() (init, populate, error-path exit) and the
scoped_guard in regcache_exit() to use these helpers.
No functional change.
Assisted-by: LLM
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
drivers/base/regmap/regcache.c | 57 +++++++++++++++++++++---------------------
1 file changed, 29 insertions(+), 28 deletions(-)
diff --git a/drivers/base/regmap/regcache.c b/drivers/base/regmap/regcache.c
index 4c80db5d6f6f..ebfa27bb6f54 100644
--- a/drivers/base/regmap/regcache.c
+++ b/drivers/base/regmap/regcache.c
@@ -121,6 +121,28 @@ static void regcache_hw_exit(struct regmap *map)
kfree(map->reg_defaults_raw);
}
+static int regcache_locked_op(struct regmap *map,
+ int (*op)(struct regmap *map),
+ const char *action)
+{
+ if (!op)
+ return 0;
+
+ dev_dbg(map->dev, "%s %s cache\n", action, map->cache_ops->name);
+ guard(regmap)(map);
+ return op(map);
+}
+
+static void regcache_locked_exit(struct regmap *map)
+{
+ if (!map->cache_ops->exit)
+ return;
+
+ dev_dbg(map->dev, "Destroying %s cache\n", map->cache_ops->name);
+ guard(regmap)(map);
+ map->cache_ops->exit(map);
+}
+
int regcache_init(struct regmap *map, const struct regmap_config *config)
{
bool sort_defaults = false;
@@ -222,15 +244,9 @@ int regcache_init(struct regmap *map, const struct regmap_config *config)
map->max_register_is_set = true;
}
- if (map->cache_ops->init) {
- dev_dbg(map->dev, "Initializing %s cache\n",
- map->cache_ops->name);
- map->lock(map->lock_arg);
- ret = map->cache_ops->init(map);
- map->unlock(map->lock_arg);
- if (ret)
- goto err_free_reg_defaults;
- }
+ ret = regcache_locked_op(map, map->cache_ops->init, "Initializing");
+ if (ret)
+ goto err_free_reg_defaults;
/*
* Some devices such as PMICs don't have cache defaults,
@@ -243,12 +259,8 @@ int regcache_init(struct regmap *map, const struct regmap_config *config)
goto err_exit;
}
- if (map->cache_ops->populate &&
- (map->num_reg_defaults || map->reg_default_cb)) {
- dev_dbg(map->dev, "Populating %s cache\n", map->cache_ops->name);
- map->lock(map->lock_arg);
- ret = map->cache_ops->populate(map);
- map->unlock(map->lock_arg);
+ if (map->num_reg_defaults || map->reg_default_cb) {
+ ret = regcache_locked_op(map, map->cache_ops->populate, "Populating");
if (ret)
goto err_free;
}
@@ -257,12 +269,7 @@ int regcache_init(struct regmap *map, const struct regmap_config *config)
err_free:
regcache_hw_exit(map);
err_exit:
- if (map->cache_ops->exit) {
- dev_dbg(map->dev, "Destroying %s cache\n", map->cache_ops->name);
- map->lock(map->lock_arg);
- map->cache_ops->exit(map);
- map->unlock(map->lock_arg);
- }
+ regcache_locked_exit(map);
err_free_reg_defaults:
kfree(map->reg_defaults);
@@ -277,13 +284,7 @@ void regcache_exit(struct regmap *map)
BUG_ON(!map->cache_ops);
regcache_hw_exit(map);
-
- if (map->cache_ops->exit) {
- dev_dbg(map->dev, "Destroying %s cache\n",
- map->cache_ops->name);
- scoped_guard(regmap, map)
- map->cache_ops->exit(map);
- }
+ regcache_locked_exit(map);
kfree(map->reg_defaults);
}
--
2.51.0
next prev parent reply other threads:[~2026-09-30 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:46 [PATCH 0/7] regmap: cleanups for regcache and regmap init paths Peng Fan (OSS)
2026-09-30 9:46 ` Peng Fan (OSS) [this message]
2026-09-30 9:46 ` [PATCH 2/7] regcache: extract __regcache_sync() to deduplicate sync dispatch Peng Fan (OSS)
2026-09-30 9:46 ` [PATCH 3/7] regcache: simplify control flow and reduce nesting Peng Fan (OSS)
2026-09-30 9:46 ` [PATCH 4/7] regmap: use krealloc_array() in regmap_register_patch() Peng Fan (OSS)
2026-09-30 9:46 ` [PATCH 5/7] regmap: use devm_kmemdup() for bus copies and remove free_on_exit Peng Fan (OSS)
2026-09-30 9:47 ` [PATCH 6/7] regmap: return errors directly before map allocation in __regmap_init() Peng Fan (OSS)
2026-09-30 9:47 ` [PATCH 7/7] regmap: fix potential double-free of map->reg_defaults on cache reinit Peng Fan (OSS)
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=20260930-regmap-lock-2nd-v1-1-33a8a482f9ae@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=rafael@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®