On Thu, Apr 25, 2019 at 12:11 PM Ulf Hansson <[email protected]> wrote: > > On Thu, 25 Apr 2019 at 11:56, Rafael J. Wysocki <[email protected]> wrote: > > > > On Thu, Apr 25, 2019 at 11:04 AM Ulf Hansson <[email protected]> wrote: > > > > > > Recently genpd was extended to cope with devices belonging to CPUs. > > > However, > > > attaching CPU devices via genpd_dev_pm_attach_by_id|name() doesn't work, > > > because of the virtual device that genpd allocates in this path. > > > > > > In this series, this limitation is addressed, together with a few other > > > related > > > fixes/cleanups. > > > > > > Ulf Hansson (4): > > > PM / Domains: Use the base device for > > > driver_deferred_probe_check_state() > > > PM / Domains: Drop unused in-parameter to some genpd functions > > > PM / Domains: Search for the CPU device outside the genpd lock > > > PM / Domains: Allow to attach a CPU via > > > genpd_dev_pm_attach_by_id|name() > > > > > > drivers/base/power/domain.c | 73 ++++++++++++++++++------------------- > > > include/linux/pm_domain.h | 1 + > > > 2 files changed, 36 insertions(+), 38 deletions(-) > > > > Are there any dependencies between this and the series you've recently > > posted? > > Yep. I should have stated that, sorry. This should be applied on top.
On top of which series?
