Re: [PATCH v2 1/4] hwrng: exynos - Runtime suspend device after init

2016-04-05 Thread Herbert Xu
On Mon, Mar 14, 2016 at 09:07:12AM +0900, Krzysztof Kozlowski wrote: > The driver uses pm_runtime_put_noidle() after initialization so the > device might remain in active state if the core does not read from it > (the read callback contains regular runtime put). The put_noidle() was > chosen

Re: [PATCH v2 1/4] hwrng: exynos - Runtime suspend device after init

2016-04-05 Thread Herbert Xu
On Mon, Mar 14, 2016 at 09:07:12AM +0900, Krzysztof Kozlowski wrote: > The driver uses pm_runtime_put_noidle() after initialization so the > device might remain in active state if the core does not read from it > (the read callback contains regular runtime put). The put_noidle() was > chosen

[PATCH v2 1/4] hwrng: exynos - Runtime suspend device after init

2016-03-13 Thread Krzysztof Kozlowski
The driver uses pm_runtime_put_noidle() after initialization so the device might remain in active state if the core does not read from it (the read callback contains regular runtime put). The put_noidle() was chosen probably to avoid unneeded suspend and resume cycle after the initialization.

[PATCH v2 1/4] hwrng: exynos - Runtime suspend device after init

2016-03-13 Thread Krzysztof Kozlowski
The driver uses pm_runtime_put_noidle() after initialization so the device might remain in active state if the core does not read from it (the read callback contains regular runtime put). The put_noidle() was chosen probably to avoid unneeded suspend and resume cycle after the initialization.