Re: [PATCH v3 03/13] PM / Domains: Add DT bindings for PM QoS device latencies

2014-09-26 Thread Ulf Hansson
On 25 September 2014 18:28, Geert Uytterhoeven wrote: > PM QoS device start/stop and save/restore state latencies are more or > less properties of the hardware. > In legacy code, they're specified from platform code. > On DT platforms, their values should come from DT. I am not so sure about

Re: [PATCH v3 03/13] PM / Domains: Add DT bindings for PM QoS device latencies

2014-09-26 Thread Ulf Hansson
On 25 September 2014 18:28, Geert Uytterhoeven geert+rene...@glider.be wrote: PM QoS device start/stop and save/restore state latencies are more or less properties of the hardware. In legacy code, they're specified from platform code. On DT platforms, their values should come from DT. I am

[PATCH v3 03/13] PM / Domains: Add DT bindings for PM QoS device latencies

2014-09-25 Thread Geert Uytterhoeven
PM QoS device start/stop and save/restore state latencies are more or less properties of the hardware. In legacy code, they're specified from platform code. On DT platforms, their values should come from DT. Signed-off-by: Geert Uytterhoeven --- Should these properties be called

[PATCH v3 03/13] PM / Domains: Add DT bindings for PM QoS device latencies

2014-09-25 Thread Geert Uytterhoeven
PM QoS device start/stop and save/restore state latencies are more or less properties of the hardware. In legacy code, they're specified from platform code. On DT platforms, their values should come from DT. Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be --- Should these properties be