From: Michael Reeves via B4 Relay <devnull+michael.reeves077.gmail.com@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Andrew Ballance <andrewjballance@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
maple-tree@lists.infradead.org, asahi@lists.linux.dev,
linux-mm@kvack.org, Michael Reeves <michael.reeves077@gmail.com>
Subject: [PATCH v3 0/2] regmap: Fix cache lifecycle locking and teardown
Date: Tue, 06 Oct 2026 18:03:14 +1100 [thread overview]
Message-ID: <20261006-regcache-lifecycle-submit-v3-0-37bdd82fd47c@gmail.com> (raw)
Fix an "Invalid wait context" lockdep warning during Apple GPIO probe and
correct debugfs ordering during cache teardown.
Tested on Apple M3 MacBook Air (T8122):
- All 4 GPIO controllers probe successfully with lockdep enabled.
- The "Invalid wait context" warning no longer occurs.
- The regmap KUnit suite passes and lockdep remains enabled.
---
Changes in v3:
- Link to v2: https://lore.kernel.org/r/20261004-regcache-lifecycle-submit-v2-0-976d405e89a7@gmail.com
- Add Maple-state irqsave and irqrestore helpers.
- Use the helpers for cache teardown and document why IRQ safety is needed.
- Rebase onto the latest upstream tree.
Changes in v2:
- Link to v1: https://lore.kernel.org/r/20260925-regcache-lifecycle-submit-v1-1-83b75ca79d96@gmail.com
- Make Maple cache teardown IRQ-safe.
- Fix debugfs ordering during cache teardown and reinitialization.
- Rebase onto the latest upstream tree.
---
Michael Reeves (2):
regmap: Remove debugfs before cache teardown
regmap: Drop map lock during cache init and exit
drivers/base/regmap/regcache-maple.c | 9 +++++++--
drivers/base/regmap/regcache.c | 6 ------
drivers/base/regmap/regmap-debugfs.c | 1 +
drivers/base/regmap/regmap.c | 15 +++++++++------
include/linux/maple_tree.h | 4 ++++
5 files changed, 21 insertions(+), 14 deletions(-)
---
base-commit: 2c3418fffa9d037b2038a6db48be63f9e2291806
change-id: 20260925-regcache-lifecycle-submit-74f366be0fbc
Best regards,
--
Michael Reeves <michael.reeves077@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Michael Reeves <michael.reeves077@gmail.com>
To: Mark Brown <broonie@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Andrew Ballance <andrewjballance@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
maple-tree@lists.infradead.org, asahi@lists.linux.dev,
linux-mm@kvack.org, Michael Reeves <michael.reeves077@gmail.com>
Subject: [PATCH v3 0/2] regmap: Fix cache lifecycle locking and teardown
Date: Tue, 06 Oct 2026 18:03:14 +1100 [thread overview]
Message-ID: <20261006-regcache-lifecycle-submit-v3-0-37bdd82fd47c@gmail.com> (raw)
Fix an "Invalid wait context" lockdep warning during Apple GPIO probe and
correct debugfs ordering during cache teardown.
Tested on Apple M3 MacBook Air (T8122):
- All 4 GPIO controllers probe successfully with lockdep enabled.
- The "Invalid wait context" warning no longer occurs.
- The regmap KUnit suite passes and lockdep remains enabled.
---
Changes in v3:
- Link to v2: https://lore.kernel.org/r/20261004-regcache-lifecycle-submit-v2-0-976d405e89a7@gmail.com
- Add Maple-state irqsave and irqrestore helpers.
- Use the helpers for cache teardown and document why IRQ safety is needed.
- Rebase onto the latest upstream tree.
Changes in v2:
- Link to v1: https://lore.kernel.org/r/20260925-regcache-lifecycle-submit-v1-1-83b75ca79d96@gmail.com
- Make Maple cache teardown IRQ-safe.
- Fix debugfs ordering during cache teardown and reinitialization.
- Rebase onto the latest upstream tree.
---
Michael Reeves (2):
regmap: Remove debugfs before cache teardown
regmap: Drop map lock during cache init and exit
drivers/base/regmap/regcache-maple.c | 9 +++++++--
drivers/base/regmap/regcache.c | 6 ------
drivers/base/regmap/regmap-debugfs.c | 1 +
drivers/base/regmap/regmap.c | 15 +++++++++------
include/linux/maple_tree.h | 4 ++++
5 files changed, 21 insertions(+), 14 deletions(-)
---
base-commit: 2c3418fffa9d037b2038a6db48be63f9e2291806
change-id: 20260925-regcache-lifecycle-submit-74f366be0fbc
Best regards,
--
Michael Reeves <michael.reeves077@gmail.com>
next reply other threads:[~2026-10-06 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:03 Michael Reeves via B4 Relay [this message]
2026-10-06 7:03 ` [PATCH v3 0/2] regmap: Fix cache lifecycle locking and teardown Michael Reeves
2026-10-06 7:03 ` [PATCH v3 1/2] regmap: Remove debugfs before cache teardown Michael Reeves via B4 Relay
2026-10-06 7:03 ` Michael Reeves
2026-10-08 10:46 ` Peng Fan
2026-10-06 7:03 ` [PATCH v3 2/2] regmap: Drop map lock during cache init and exit Michael Reeves via B4 Relay
2026-10-06 7:03 ` Michael Reeves
2026-10-08 10:55 ` Peng Fan
2026-10-12 23:12 ` [PATCH v3 0/2] regmap: Fix cache lifecycle locking and teardown Mark Brown
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=20261006-regcache-lifecycle-submit-v3-0-37bdd82fd47c@gmail.com \
--to=devnull+michael.reeves077.gmail.com@kernel.org \
--cc=aliceryhl@google.com \
--cc=andrewjballance@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=michael.reeves077@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.