[PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Rafael J. Wysocki]

Hi All,

Applying this series will cause power.no_pm to be set for faux devices (so they
don't get processed unnecessarily during system-wide suspend/resume transitions)
and power.no_callbacks to be set along with power.no_pm (for consistency).

Thanks!

[PATCH v1 1/2] driver core: faux: Set power.no_pm for faux devices

[Rafael J. Wysocki]

From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Since faux devices are not supposed to be involved in any kind of
power management, set the no_pm flag for all of them.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
 drivers/base/faux.c |    1 +
 1 file changed, 1 insertion(+)

--- a/drivers/base/faux.c
+++ b/drivers/base/faux.c
@@ -155,6 +155,7 @@
 		dev->parent = &faux_bus_root;
 	dev->bus = &faux_bus_type;
 	dev_set_name(dev, "%s", name);
+	device_set_pm_not_required(dev);
 
 	ret = device_add(dev);
 	if (ret) {

[PATCH v1 2/2] driver core/PM: Set power.no_callbacks along with power.no_pm

[Rafael J. Wysocki]

From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Devices with power.no_pm set are not expected to need any power
management at all, so modify device_set_pm_not_required() to set
power.no_callbacks for them too in case runtime PM will be enabled
for any of them (which in principle may be done for convenience if
such a device participates in a dependency chain).

Since device_set_pm_not_required() must be called before device_add()
or it would not have any effect, it can update power.no_callbacks
without locking, unlike pm_runtime_no_callbacks() that can be called
after registering the target device.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
 include/linux/device.h |    3 +++
 1 file changed, 3 insertions(+)

--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -851,6 +851,9 @@
 static inline void device_set_pm_not_required(struct device *dev)
 {
 	dev->power.no_pm = true;
+#ifdef CONFIG_PM
+	dev->power.no_callbacks = true;
+#endif
 }
 
 static inline void dev_pm_syscore_device(struct device *dev, bool val)

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Greg Kroah-Hartman]

On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> Hi All,
> 
> Applying this series will cause power.no_pm to be set for faux devices (so they
> don't get processed unnecessarily during system-wide suspend/resume transitions)
> and power.no_callbacks to be set along with power.no_pm (for consistency).

Oh, nice!  I forgot about that entirely.  Should these be backported to
older kernels as well?

thanks,

greg k-h

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Rafael J. Wysocki]

On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > Hi All,
> >
> > Applying this series will cause power.no_pm to be set for faux devices (so they
> > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > and power.no_callbacks to be set along with power.no_pm (for consistency).
>
> Oh, nice!  I forgot about that entirely.  Should these be backported to
> older kernels as well?

Doing it shouldn't hurt.

Cheers, Rafael

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Sudeep Holla]

On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> Hi All,
> 
> Applying this series will cause power.no_pm to be set for faux devices (so they
> don't get processed unnecessarily during system-wide suspend/resume transitions)
> and power.no_callbacks to be set along with power.no_pm (for consistency).
> 

Nice, even I hadn't noticed about these before. The changes looks good
to me.

Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>

--
Regards,
Sudeep

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Rafael J. Wysocki]

On Thu, Aug 28, 2025 at 1:20 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>
> On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > > Hi All,
> > >
> > > Applying this series will cause power.no_pm to be set for faux devices (so they
> > > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > > and power.no_callbacks to be set along with power.no_pm (for consistency).
> >
> > Oh, nice!  I forgot about that entirely.  Should these be backported to
> > older kernels as well?

So do you want me to resend these patches with suitable Cc: stable tags?

Alternatively, I can just apply them with the tags and route them
through my tree, whatever you prefer.

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Rafael J. Wysocki]

On Fri, Aug 29, 2025 at 9:09 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
>
> On Thu, Aug 28, 2025 at 1:20 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> >
> > On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > > > Hi All,
> > > >
> > > > Applying this series will cause power.no_pm to be set for faux devices (so they
> > > > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > > > and power.no_callbacks to be set along with power.no_pm (for consistency).
> > >
> > > Oh, nice!  I forgot about that entirely.  Should these be backported to
> > > older kernels as well?
>
> So do you want me to resend these patches with suitable Cc: stable tags?
>
> Alternatively, I can just apply them with the tags and route them
> through my tree, whatever you prefer.

In the absence of more feedback, this is what I'm going to do.

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Greg Kroah-Hartman]

On Wed, Sep 03, 2025 at 01:33:18PM +0200, Rafael J. Wysocki wrote:
> On Fri, Aug 29, 2025 at 9:09 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> >
> > On Thu, Aug 28, 2025 at 1:20 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > >
> > > On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > > > > Hi All,
> > > > >
> > > > > Applying this series will cause power.no_pm to be set for faux devices (so they
> > > > > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > > > > and power.no_callbacks to be set along with power.no_pm (for consistency).
> > > >
> > > > Oh, nice!  I forgot about that entirely.  Should these be backported to
> > > > older kernels as well?
> >
> > So do you want me to resend these patches with suitable Cc: stable tags?
> >
> > Alternatively, I can just apply them with the tags and route them
> > through my tree, whatever you prefer.
> 
> In the absence of more feedback, this is what I'm going to do.

Thanks, sorry for the delay, been swamped with conferences and travel :(

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Greg Kroah-Hartman]

On Sat, Sep 06, 2025 at 01:53:11PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Sep 03, 2025 at 01:33:18PM +0200, Rafael J. Wysocki wrote:
> > On Fri, Aug 29, 2025 at 9:09 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > >
> > > On Thu, Aug 28, 2025 at 1:20 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > > >
> > > > On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
> > > > <gregkh@linuxfoundation.org> wrote:
> > > > >
> > > > > On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > > > > > Hi All,
> > > > > >
> > > > > > Applying this series will cause power.no_pm to be set for faux devices (so they
> > > > > > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > > > > > and power.no_callbacks to be set along with power.no_pm (for consistency).
> > > > >
> > > > > Oh, nice!  I forgot about that entirely.  Should these be backported to
> > > > > older kernels as well?
> > >
> > > So do you want me to resend these patches with suitable Cc: stable tags?
> > >
> > > Alternatively, I can just apply them with the tags and route them
> > > through my tree, whatever you prefer.
> > 
> > In the absence of more feedback, this is what I'm going to do.
> 
> Thanks, sorry for the delay, been swamped with conferences and travel :(

Wait, I can take them right now, no need to resend them.

greg k-h

Re: [PATCH v1 0/2] driver core/PM: Two updates related to power.no_pm

[Rafael J. Wysocki]

On Sat, Sep 6, 2025 at 1:54 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Sat, Sep 06, 2025 at 01:53:11PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Sep 03, 2025 at 01:33:18PM +0200, Rafael J. Wysocki wrote:
> > > On Fri, Aug 29, 2025 at 9:09 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > > >
> > > > On Thu, Aug 28, 2025 at 1:20 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > > > >
> > > > > On Thu, Aug 28, 2025 at 1:07 PM Greg Kroah-Hartman
> > > > > <gregkh@linuxfoundation.org> wrote:
> > > > > >
> > > > > > On Thu, Aug 28, 2025 at 12:55:50PM +0200, Rafael J. Wysocki wrote:
> > > > > > > Hi All,
> > > > > > >
> > > > > > > Applying this series will cause power.no_pm to be set for faux devices (so they
> > > > > > > don't get processed unnecessarily during system-wide suspend/resume transitions)
> > > > > > > and power.no_callbacks to be set along with power.no_pm (for consistency).
> > > > > >
> > > > > > Oh, nice!  I forgot about that entirely.  Should these be backported to
> > > > > > older kernels as well?
> > > >
> > > > So do you want me to resend these patches with suitable Cc: stable tags?
> > > >
> > > > Alternatively, I can just apply them with the tags and route them
> > > > through my tree, whatever you prefer.
> > >
> > > In the absence of more feedback, this is what I'm going to do.
> >
> > Thanks, sorry for the delay, been swamped with conferences and travel :(

No worries.

> Wait, I can take them right now, no need to resend them.

Cool, thanks!