diff options
| author | Ulf Hansson <ulf.hansson@linaro.org> | 2018-01-10 21:31:56 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2018-01-11 01:57:44 +0100 |
| commit | a935424bb658f9ca37eb5e94119b857998341356 (patch) | |
| tree | 4763ccc31976bb54544e2638dcd9bb2ff934ab2d /kernel/bpf/arraymap.c | |
| parent | 001d50c9a14f1fab94b329161a1db9235b4e60da (diff) | |
PM / domains: Don't skip driver's ->suspend|resume_noirq() callbacks
Commit 10da65423fdb (PM / Domains: Call driver's noirq callbacks)
started to respect driver's noirq callbacks, but while doing that it
also introduced a few potential problems.
More precisely, in genpd_finish_suspend() and genpd_resume_noirq()
the noirq callbacks at the driver level should be invoked, no matter
of whether dev->power.wakeup_path is set or not.
Additionally, the commit in question also made genpd_resume_noirq()
to ignore the return value from pm_runtime_force_resume().
Let's fix both these issues!
Fixes: 10da65423fdb (PM / Domains: Call driver's noirq callbacks)
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/bpf/arraymap.c')
0 files changed, 0 insertions, 0 deletions