PM / Domains: Don't measure ->start|stop() latency in system PM callbacks
authorUlf Hansson <ulf.hansson@linaro.org>
Thu, 15 Oct 2015 15:02:06 +0000 (17:02 +0200)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 28 Oct 2015 03:33:04 +0000 (04:33 +0100)
commit51cda844892fded75d3ad07d0233e73572eba2f3
tree911179ce9dd03df7dd86b24c5bd1aa9d70c80889
parent88cfe5356a9b5cbc77e444b55c7e0d8ba4cc5ecb
PM / Domains: Don't measure ->start|stop() latency in system PM callbacks

Measure latency does by itself contribute to an increased latency, thus we
should avoid it when it isn't needed.

Genpd measures latencies in the system PM phase for the ->start|stop()
callbacks and is thus affecting the system PM suspend/resume time.
Moreover these latencies are validated only at runtime PM suspend/resume.

To this reasoning, let's decide to leave these measurements out of the
system PM phase. There should be plenty of occasions during runtime PM to
perform these measurements anyway.

Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Lina Iyer <lina.iyer@linaro.org>
Acked-by: Kevin Hilman <khilman@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/base/power/domain.c