Re: [PATCH v3 0/6] PM: QoS: Introduce a CPU system wakeup QoS limit for s2idle

[Kevin Hilman <khilman@baylibre.com>]

Ulf Hansson <ulf.hansson@linaro.org> writes:

> Changes in v3:
> 	- Take new the new QoS limit into account for cpuidle too (Rafael).
> 	- Add a new Kconfig for the new QoS interface (Rafael)
> 	- Improved the documentation (Dhruva) 
> 	- Clarified commit messages and added acks.
>
> Changes in v2:
> 	- Limit the new QoS to CPUs  and make some corresponding renaming of the
> 	functions along with name of the device node for user space.
> 	- Make sure we deal with the failure/error path correctly when there are
> 	no state available for s2idle.
> 	- Add documentation.
>
> Some platforms supports multiple low power states for CPUs that can be used
> when entering system-wide suspend and s2idle in particular. Currently we are
> always selecting the deepest possible state for the CPUs, which can break the
> system wakeup latency constraint that may be required for a use case.
>
> Therefore, this series suggests to introduce a new interface for user space,
> allowing us to specify the CPU system wakeup QoS limit. The QoS limit is then
> taken into account when selecting a suitable low power state for s2idle/cpuidle.

Reviewed-by: Kevin Hilman (TI) <khilman@baylibre.com>
Tested-by: Kevin Hilman (TI) <khilman@baylibre.com>