summaryrefslogtreecommitdiffstats
path: root/kernel/locking/mutex.c
diff options
context:
space:
mode:
authorUlf Hansson <ulf.hansson@linaro.org>2017-02-17 10:55:25 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-02-23 22:25:46 +0100
commit2da835452a0875866ca55d23126c77b9372f0015 (patch)
treeed9bc9cad8e875f3ffb7aba39a6510b7a09868b9 /kernel/locking/mutex.c
parentPM / Domains: Rename is_async to one_dev_on for genpd_power_off() (diff)
downloadlinux-2da835452a0875866ca55d23126c77b9372f0015.tar.xz
linux-2da835452a0875866ca55d23126c77b9372f0015.zip
PM / Domains: Power off masters immediately in the power off sequence
Once a subdomain is powered off, genpd queues a power off work for each of the subdomain's corresponding masters, thus postponing the masters to be powered off to a later point. When genpd used intermediate power off states, which was removed in commit ba2bbfbf6307 ("PM / Domains: Remove intermediate states from the power off sequence"), this behaviour made sense, but now it simply doesn't. Genpd can easily try to power off the masters in the same context as the subdomain, of course by acquiring/releasing the lock. Then, let's convert to this behaviour, as it avoids unnecessary works from being queued. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/locking/mutex.c')
0 files changed, 0 insertions, 0 deletions