soc: qcom: rpmh-rsc: We aren't notified of our own failure w/ NOTIFY_BAD
authorDouglas Anderson <dianders@chromium.org>
Mon, 4 May 2020 17:50:16 +0000 (10:50 -0700)
committerBjorn Andersson <bjorn.andersson@linaro.org>
Fri, 15 May 2020 18:42:58 +0000 (11:42 -0700)
commitc45def5d804abaa48c205f8ba5cd52bfbeeae70c
treee4c2e1a511f70cf390876d2c6ffb26b03a1007f0
parent1143c36656b8dccf0ece93053502a147d3c60961
soc: qcom: rpmh-rsc: We aren't notified of our own failure w/ NOTIFY_BAD

When a PM Notifier returns NOTIFY_BAD it doesn't get called with
CPU_PM_ENTER_FAILED.  It only get called for CPU_PM_ENTER_FAILED if
someone else (further down the notifier chain) returns NOTIFY_BAD.

Handle this case by taking our CPU out of the list of ones that have
entered PM.  Without this it's possible we could detect that the last
CPU went down (and we would flush) even if some CPU was alive.  That's
not good since our flushing routines currently assume they're running
on the last CPU for mutual exclusion.

Fixes: 985427f997b6 ("soc: qcom: rpmh: Invoke rpmh_flush() for dirty caches")
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Maulik Shah <mkshah@codeaurora.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Link: https://lore.kernel.org/r/20200504104917.v6.2.I1927d1bca2569a27b2d04986baf285027f0818a2@changeid
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
drivers/soc/qcom/rpmh-rsc.c