* [PATCH 0/2] regulator: freeze delayed hardware access during suspend
@ 2026-10-16 10:05 Jiale Yao
2026-10-16 10:05 ` [PATCH 1/2] regulator: core: freeze deferred disable work " Jiale Yao
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Jiale Yao @ 2026-10-16 10:05 UTC (permalink / raw)
To: Liam Girdwood, Mark Brown, Matti Vaittinen, linux-kernel; +Cc: Jiale Yao
Deferred regulator disable and IRQ recovery callbacks can perform hardware
access after a caller-provided delay. Their current workqueues remain active
while devices are being suspended, allowing the callbacks to reach a
regulator after its backing bus has been suspended.
Move deferred disable to the freezable power-efficient workqueue. Move IRQ
helper callbacks to a freezable workqueue as well, while retaining the
high-priority property for users that request it. Each patch is independent
and can be applied separately.
Jiale Yao (2):
regulator: core: freeze deferred disable work during suspend
regulator: irq: freeze deferred hardware access during suspend
drivers/regulator/core.c | 3 ++-
drivers/regulator/irq_helpers.c | 38 +++++++++++++++++++--------------
2 files changed, 24 insertions(+), 17 deletions(-)
--
2.34.1
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH 1/2] regulator: core: freeze deferred disable work during suspend
2026-10-16 10:05 [PATCH 0/2] regulator: freeze delayed hardware access during suspend Jiale Yao
@ 2026-10-16 10:05 ` Jiale Yao
2026-10-17 7:21 ` jiale yao
2026-10-23 17:36 ` [PATCH " Mark Brown
2026-10-16 10:05 ` [PATCH 2/2] regulator: irq: freeze deferred hardware access " Jiale Yao
2026-10-23 17:40 ` (subset) [PATCH 0/2] regulator: freeze delayed " Mark Brown
2 siblings, 2 replies; 8+ messages in thread
From: Jiale Yao @ 2026-10-16 10:05 UTC (permalink / raw)
To: Liam Girdwood, Mark Brown, linux-kernel; +Cc: Jiale Yao
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH 2/2] regulator: irq: freeze deferred hardware access during suspend
2026-10-16 10:05 [PATCH 0/2] regulator: freeze delayed hardware access during suspend Jiale Yao
2026-10-16 10:05 ` [PATCH 1/2] regulator: core: freeze deferred disable work " Jiale Yao
@ 2026-10-16 10:05 ` Jiale Yao
2026-10-17 7:23 ` jiale yao
2026-10-19 8:00 ` [PATCH " Matti Vaittinen
2026-10-23 17:40 ` (subset) [PATCH 0/2] regulator: freeze delayed " Mark Brown
2 siblings, 2 replies; 8+ messages in thread
From: Jiale Yao @ 2026-10-16 10:05 UTC (permalink / raw)
To: Matti Vaittinen, Liam Girdwood, Mark Brown, linux-kernel; +Cc: Jiale Yao
The regulator IRQ helper delays status checks and recovery callbacks on
non-freezable workqueues. Those callbacks may access regulator hardware
after the backing bus has been suspended.
Use system_freezable_wq for normal-priority callbacks. Allocate a
freezable high-priority workqueue when requested so the high_prio
contract is preserved while hardware access is frozen across suspend.
Signed-off-by: Jiale Yao <yaojiale02@163.com>
---
drivers/regulator/irq_helpers.c | 38 +++++++++++++++++++--------------
1 file changed, 22 insertions(+), 16 deletions(-)
diff --git a/drivers/regulator/irq_helpers.c b/drivers/regulator/irq_helpers.c
index 5b3cfac28667..cdbd170d2b15 100644
--- a/drivers/regulator/irq_helpers.c
+++ b/drivers/regulator/irq_helpers.c
@@ -15,6 +15,7 @@
#include <linux/regmap.h>
#include <linux/slab.h>
#include <linux/spinlock.h>
+#include <linux/workqueue.h>
#include <linux/regulator/driver.h>
#include "internal.h"
@@ -27,6 +28,7 @@ struct regulator_irq {
int irq;
int retry_cnt;
struct delayed_work isr_work;
+ struct workqueue_struct *wq;
};
/*
@@ -145,12 +147,7 @@ static void regulator_notifier_isr_work(struct work_struct *work)
return;
reschedule:
- if (!d->high_prio)
- mod_delayed_work(system_dfl_wq, &h->isr_work,
- msecs_to_jiffies(tmo));
- else
- mod_delayed_work(system_highpri_wq, &h->isr_work,
- msecs_to_jiffies(tmo));
+ mod_delayed_work(h->wq, &h->isr_work, msecs_to_jiffies(tmo));
}
static irqreturn_t regulator_notifier_isr(int irq, void *data)
@@ -248,13 +245,8 @@ static irqreturn_t regulator_notifier_isr(int irq, void *data)
}
if (d->irq_off_ms) {
- if (!d->high_prio)
- schedule_delayed_work(&h->isr_work,
- msecs_to_jiffies(d->irq_off_ms));
- else
- mod_delayed_work(system_highpri_wq,
- &h->isr_work,
- msecs_to_jiffies(d->irq_off_ms));
+ mod_delayed_work(h->wq, &h->isr_work,
+ msecs_to_jiffies(d->irq_off_ms));
}
return IRQ_HANDLED;
@@ -363,13 +355,25 @@ void *regulator_irq_helper(struct device *dev,
init_rdev_errors(h);
- if (h->desc.irq_off_ms)
+ if (h->desc.irq_off_ms) {
+ if (h->desc.high_prio) {
+ h->wq = alloc_workqueue("regulator_irq_highpri",
+ WQ_FREEZABLE | WQ_HIGHPRI, 0);
+ if (!h->wq)
+ return ERR_PTR(-ENOMEM);
+ } else {
+ h->wq = system_freezable_wq;
+ }
+
INIT_DELAYED_WORK(&h->isr_work, regulator_notifier_isr_work);
+ }
ret = request_threaded_irq(h->irq, NULL, regulator_notifier_isr,
IRQF_ONESHOT | irq_flags, h->desc.name, h);
if (ret) {
dev_err(dev, "Failed to request IRQ %d\n", irq);
+ if (h->desc.irq_off_ms && h->desc.high_prio)
+ destroy_workqueue(h->wq);
return ERR_PTR(ret);
}
@@ -393,8 +397,11 @@ void regulator_irq_helper_cancel(void **handle)
struct regulator_irq *h = *handle;
free_irq(h->irq, h);
- if (h->desc.irq_off_ms)
+ if (h->desc.irq_off_ms) {
cancel_delayed_work_sync(&h->isr_work);
+ if (h->desc.high_prio)
+ destroy_workqueue(h->wq);
+ }
h = NULL;
}
@@ -441,4 +448,3 @@ int regulator_irq_map_event_simple(int irq, struct regulator_irq_data *rid,
return 0;
}
EXPORT_SYMBOL_GPL(regulator_irq_map_event_simple);
-
--
2.34.1
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re:[PATCH 1/2] regulator: core: freeze deferred disable work during suspend
2026-10-16 10:05 ` [PATCH 1/2] regulator: core: freeze deferred disable work " Jiale Yao
@ 2026-10-17 7:21 ` jiale yao
2026-10-23 17:36 ` [PATCH " Mark Brown
1 sibling, 0 replies; 8+ messages in thread
From: jiale yao @ 2026-10-17 7:21 UTC (permalink / raw)
To: Liam Girdwood, Mark Brown, linux-kernel
At 2026-10-16 18:05:21, "Jiale Yao" <yaojiale02@163.com> wrote:
>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.
>
Fixes: da07ecd93b19 ("regulator: Implement deferred disable support")
>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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re:[PATCH 2/2] regulator: irq: freeze deferred hardware access during suspend
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
1 sibling, 0 replies; 8+ messages in thread
From: jiale yao @ 2026-10-17 7:23 UTC (permalink / raw)
To: Matti Vaittinen, Liam Girdwood, Mark Brown, linux-kernel
At 2026-10-16 18:05:22, "Jiale Yao" <yaojiale02@163.com> wrote:
>The regulator IRQ helper delays status checks and recovery callbacks on
>non-freezable workqueues. Those callbacks may access regulator hardware
>after the backing bus has been suspended.
>
>Use system_freezable_wq for normal-priority callbacks. Allocate a
>freezable high-priority workqueue when requested so the high_prio
>contract is preserved while hardware access is frozen across suspend.
>
Fixes: 7111c6d1b31b ("regulator: IRQ based event/error notification helpers")
>Signed-off-by: Jiale Yao <yaojiale02@163.com>
>---
> drivers/regulator/irq_helpers.c | 38 +++++++++++++++++++--------------
> 1 file changed, 22 insertions(+), 16 deletions(-)
>
>diff --git a/drivers/regulator/irq_helpers.c b/drivers/regulator/irq_helpers.c
>index 5b3cfac28667..cdbd170d2b15 100644
>--- a/drivers/regulator/irq_helpers.c
>+++ b/drivers/regulator/irq_helpers.c
>@@ -15,6 +15,7 @@
> #include <linux/regmap.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
>+#include <linux/workqueue.h>
> #include <linux/regulator/driver.h>
>
> #include "internal.h"
>@@ -27,6 +28,7 @@ struct regulator_irq {
> int irq;
> int retry_cnt;
> struct delayed_work isr_work;
>+ struct workqueue_struct *wq;
> };
>
> /*
>@@ -145,12 +147,7 @@ static void regulator_notifier_isr_work(struct work_struct *work)
> return;
>
> reschedule:
>- if (!d->high_prio)
>- mod_delayed_work(system_dfl_wq, &h->isr_work,
>- msecs_to_jiffies(tmo));
>- else
>- mod_delayed_work(system_highpri_wq, &h->isr_work,
>- msecs_to_jiffies(tmo));
>+ mod_delayed_work(h->wq, &h->isr_work, msecs_to_jiffies(tmo));
> }
>
> static irqreturn_t regulator_notifier_isr(int irq, void *data)
>@@ -248,13 +245,8 @@ static irqreturn_t regulator_notifier_isr(int irq, void *data)
> }
>
> if (d->irq_off_ms) {
>- if (!d->high_prio)
>- schedule_delayed_work(&h->isr_work,
>- msecs_to_jiffies(d->irq_off_ms));
>- else
>- mod_delayed_work(system_highpri_wq,
>- &h->isr_work,
>- msecs_to_jiffies(d->irq_off_ms));
>+ mod_delayed_work(h->wq, &h->isr_work,
>+ msecs_to_jiffies(d->irq_off_ms));
> }
>
> return IRQ_HANDLED;
>@@ -363,13 +355,25 @@ void *regulator_irq_helper(struct device *dev,
>
> init_rdev_errors(h);
>
>- if (h->desc.irq_off_ms)
>+ if (h->desc.irq_off_ms) {
>+ if (h->desc.high_prio) {
>+ h->wq = alloc_workqueue("regulator_irq_highpri",
>+ WQ_FREEZABLE | WQ_HIGHPRI, 0);
>+ if (!h->wq)
>+ return ERR_PTR(-ENOMEM);
>+ } else {
>+ h->wq = system_freezable_wq;
>+ }
>+
> INIT_DELAYED_WORK(&h->isr_work, regulator_notifier_isr_work);
>+ }
>
> ret = request_threaded_irq(h->irq, NULL, regulator_notifier_isr,
> IRQF_ONESHOT | irq_flags, h->desc.name, h);
> if (ret) {
> dev_err(dev, "Failed to request IRQ %d\n", irq);
>+ if (h->desc.irq_off_ms && h->desc.high_prio)
>+ destroy_workqueue(h->wq);
>
> return ERR_PTR(ret);
> }
>@@ -393,8 +397,11 @@ void regulator_irq_helper_cancel(void **handle)
> struct regulator_irq *h = *handle;
>
> free_irq(h->irq, h);
>- if (h->desc.irq_off_ms)
>+ if (h->desc.irq_off_ms) {
> cancel_delayed_work_sync(&h->isr_work);
>+ if (h->desc.high_prio)
>+ destroy_workqueue(h->wq);
>+ }
>
> h = NULL;
> }
>@@ -441,4 +448,3 @@ int regulator_irq_map_event_simple(int irq, struct regulator_irq_data *rid,
> return 0;
> }
> EXPORT_SYMBOL_GPL(regulator_irq_map_event_simple);
>-
>--
>2.34.1
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH 2/2] regulator: irq: freeze deferred hardware access during suspend
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 ` Matti Vaittinen
1 sibling, 0 replies; 8+ messages in thread
From: Matti Vaittinen @ 2026-10-19 8:00 UTC (permalink / raw)
To: Jiale Yao, Liam Girdwood, Mark Brown, linux-kernel
On 16/10/2026 13:05, Jiale Yao wrote:
> The regulator IRQ helper delays status checks and recovery callbacks on
> non-freezable workqueues. Those callbacks may access regulator hardware
> after the backing bus has been suspended.
I wonder if there has been a real system where the problem has been seen
or if this is purely a theoretical problem? But yes, I think this can
happen.
> Use system_freezable_wq for normal-priority callbacks. Allocate a
> freezable high-priority workqueue when requested so the high_prio
> contract is preserved while hardware access is frozen across suspend.
> > Signed-off-by: Jiale Yao <yaojiale02@163.com>
I don't really know the internals of workqueues well enough to say if
there are any potential side-effects. Hence my review is a bit of
superficial. With this remark:
Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> ---
> drivers/regulator/irq_helpers.c | 38 +++++++++++++++++++--------------
> 1 file changed, 22 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/regulator/irq_helpers.c b/drivers/regulator/irq_helpers.c
> index 5b3cfac28667..cdbd170d2b15 100644
> --- a/drivers/regulator/irq_helpers.c
> +++ b/drivers/regulator/irq_helpers.c
> @@ -15,6 +15,7 @@
> #include <linux/regmap.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> +#include <linux/workqueue.h>
> #include <linux/regulator/driver.h>
>
> #include "internal.h"
> @@ -27,6 +28,7 @@ struct regulator_irq {
> int irq;
> int retry_cnt;
> struct delayed_work isr_work;
> + struct workqueue_struct *wq;
> };
>
> /*
> @@ -145,12 +147,7 @@ static void regulator_notifier_isr_work(struct work_struct *work)
> return;
>
> reschedule:
> - if (!d->high_prio)
> - mod_delayed_work(system_dfl_wq, &h->isr_work,
> - msecs_to_jiffies(tmo));
> - else
> - mod_delayed_work(system_highpri_wq, &h->isr_work,
> - msecs_to_jiffies(tmo));
> + mod_delayed_work(h->wq, &h->isr_work, msecs_to_jiffies(tmo));
I like the fact that this change removes the if (!d->high_prio) from the
ISR (below) and this worker, and does the queue selection at the
initialization time. I suppose this could be done even if workqueue
types weren't changed. Thanks for this :)
> }
>
> static irqreturn_t regulator_notifier_isr(int irq, void *data)
> @@ -248,13 +245,8 @@ static irqreturn_t regulator_notifier_isr(int irq, void *data)
> }
>
> if (d->irq_off_ms) {
> - if (!d->high_prio)
> - schedule_delayed_work(&h->isr_work,
> - msecs_to_jiffies(d->irq_off_ms));
> - else
> - mod_delayed_work(system_highpri_wq,
> - &h->isr_work,
> - msecs_to_jiffies(d->irq_off_ms));
> + mod_delayed_work(h->wq, &h->isr_work,
> + msecs_to_jiffies(d->irq_off_ms));
> }
>
> return IRQ_HANDLED;
> @@ -363,13 +355,25 @@ void *regulator_irq_helper(struct device *dev,
>
> init_rdev_errors(h);
>
> - if (h->desc.irq_off_ms)
> + if (h->desc.irq_off_ms) {
> + if (h->desc.high_prio) {
> + h->wq = alloc_workqueue("regulator_irq_highpri",
> + WQ_FREEZABLE | WQ_HIGHPRI, 0);
> + if (!h->wq)
> + return ERR_PTR(-ENOMEM);
> + } else {
> + h->wq = system_freezable_wq;
> + }
> +
> INIT_DELAYED_WORK(&h->isr_work, regulator_notifier_isr_work);
> + }
>
> ret = request_threaded_irq(h->irq, NULL, regulator_notifier_isr,
> IRQF_ONESHOT | irq_flags, h->desc.name, h);
> if (ret) {
> dev_err(dev, "Failed to request IRQ %d\n", irq);
> + if (h->desc.irq_off_ms && h->desc.high_prio)
> + destroy_workqueue(h->wq);
>
> return ERR_PTR(ret);
> }
> @@ -393,8 +397,11 @@ void regulator_irq_helper_cancel(void **handle)
> struct regulator_irq *h = *handle;
>
> free_irq(h->irq, h);
> - if (h->desc.irq_off_ms)
> + if (h->desc.irq_off_ms) {
> cancel_delayed_work_sync(&h->isr_work);
> + if (h->desc.high_prio)
> + destroy_workqueue(h->wq);
> + }
>
> h = NULL;
> }
> @@ -441,4 +448,3 @@ int regulator_irq_map_event_simple(int irq, struct regulator_irq_data *rid,
> return 0;
> }
> EXPORT_SYMBOL_GPL(regulator_irq_map_event_simple);
> -
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH 1/2] regulator: core: freeze deferred disable work during suspend
2026-10-16 10:05 ` [PATCH 1/2] regulator: core: freeze deferred disable work " Jiale Yao
2026-10-17 7:21 ` jiale yao
@ 2026-10-23 17:36 ` Mark Brown
1 sibling, 0 replies; 8+ messages in thread
From: Mark Brown @ 2026-10-23 17:36 UTC (permalink / raw)
To: Jiale Yao; +Cc: Liam Girdwood, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
On Fri, Oct 16, 2026 at 06:05:21PM +0800, Jiale Yao wrote:
> 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.
This is going to have a fun interaction with the only current user of
deferred disables, DAPM. If a DAPM supply that uses deferred disables
is active at system suspend then it will disable it using a deferred
disable but since the workqueue is frozen quite early on in suspend this
will simply result in the disable not happening until after the suspend
has completed which isn't the desired outcome.
Since if we're suspending it's reasonable to assume that the supply
won't be bounced on again quickly, or that if it is we can reasonably
pay the cost of full ramp up, we should probably arrange for the disable
to be processed immeditely if we're in suspend. In addition if there
are already pending disables it'd make sense to flush them rather than
letting the workqueue freeze, for similar reasons.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: (subset) [PATCH 0/2] regulator: freeze delayed hardware access during suspend
2026-10-16 10:05 [PATCH 0/2] regulator: freeze delayed hardware access during suspend Jiale Yao
2026-10-16 10:05 ` [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-23 17:40 ` Mark Brown
2 siblings, 0 replies; 8+ messages in thread
From: Mark Brown @ 2026-10-23 17:40 UTC (permalink / raw)
To: Liam Girdwood, Matti Vaittinen, linux-kernel, Jiale Yao
On Fri, 16 Oct 2026 18:05:20 +0800, Jiale Yao wrote:
> regulator: freeze delayed hardware access during suspend
>
> Deferred regulator disable and IRQ recovery callbacks can perform hardware
> access after a caller-provided delay. Their current workqueues remain active
> while devices are being suspended, allowing the callbacks to reach a
> regulator after its backing bus has been suspended.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-7.4
Thanks!
[2/2] regulator: irq: freeze deferred hardware access during suspend
https://git.kernel.org/broonie/regulator/c/8a6d73e316f9
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2026-10-23 17:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-16 10:05 [PATCH 0/2] regulator: freeze delayed hardware access during suspend Jiale Yao
2026-10-16 10:05 ` [PATCH 1/2] regulator: core: freeze deferred disable work " Jiale Yao
2026-10-17 7:21 ` jiale yao
2026-10-23 17:36 ` [PATCH " Mark Brown
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
2026-10-23 17:40 ` (subset) [PATCH 0/2] regulator: freeze delayed " Mark Brown
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®