From: Jiale Yao <yaojiale02@163.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Cc: Jiale Yao <yaojiale02@163.com>
Subject: [PATCH 1/2] regulator: core: freeze deferred disable work during suspend
Date: Fri, 16 Oct 2026 18:05:21 +0800 [thread overview]
Message-ID: <20261016100522.2582557-2-yaojiale02@163.com> (raw)
In-Reply-To: <20261016100522.2582557-1-yaojiale02@163.com>
regulator_disable_deferred() schedules hardware access after a
caller-provided delay. The power-efficient system workqueue remains
active during system suspend, so deferred regulator operations can reach
a bus after its controller has been suspended.
Use the freezable power-efficient workqueue to preserve the existing
power policy while deferring regulator access until devices have resumed.
Signed-off-by: Jiale Yao <yaojiale02@163.com>
---
drivers/regulator/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 6a4008f387b5..317f02696e47 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -3465,7 +3465,8 @@ int regulator_disable_deferred(struct regulator *regulator, int ms)
regulator_lock(rdev);
regulator->deferred_disables++;
- mod_delayed_work(system_power_efficient_wq, &rdev->disable_work,
+ mod_delayed_work(system_freezable_power_efficient_wq,
+ &rdev->disable_work,
msecs_to_jiffies(ms));
regulator_unlock(rdev);
--
2.34.1
next prev parent reply other threads:[~2026-10-16 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:05 [PATCH 0/2] regulator: freeze delayed hardware access " Jiale Yao
2026-10-16 10:05 ` Jiale Yao [this message]
2026-10-17 7:21 ` Re:[PATCH 1/2] regulator: core: freeze deferred disable work " jiale yao
2026-10-16 10:05 ` [PATCH 2/2] regulator: irq: freeze deferred hardware access " Jiale Yao
2026-10-17 7:23 ` jiale yao
2026-10-19 8:00 ` [PATCH " Matti Vaittinen
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=20261016100522.2582557-2-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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®