On Thu, 2016-05-19 at 10:27 +0000, Hongbo Zhang wrote:

quoted

For the pm module of the core kernel a low power state is a sleep
state if even one of three conditions is met:

a) a device that can be used for input is not a source of wake ups
b) tasks need to be frozen to enter it
c) the display goes off, while it should be on

Generally runtime PM is better if you can get the same results.
Going to a system sleep state is a necessary evil.

As I just explained in previous reply, many devices in our Soc cannot
be physically clock or power gated, all the non-wakeup devices can
only be gated off at same time by a PM module, so runtime PM doesn't
fit for us well.

You are looking for a contradiction where none is to be found. We have
PM domains which allow you to model common clocks and gates. You simply
use the driver core and it will use the common gate when every device is
idle. Obviously this is also true when the system is suspended. But not
necessarily only when the system is suspended.

	Regards
		Oliver