| commit | f0d947ac01632fa6c75cb07262922a93736385c1 | |
| author | Krzysztof Kozlowski <k.kozlowski@samsung.com> | |
| Mon, 14 Mar 2016 00:07:12 +0000 (14 09:07 +0900) | ||
| committer | Herbert Xu <herbert@gondor.apana.org.au> | |
| Tue, 5 Apr 2016 12:35:42 +0000 (5 20:35 +0800) | ||
| tree | 1a9416c44fb8905ea243dc123212f0ce7e7fdfb0 | treesnapshot (tar.gz zip) |
| parent | 97ee7ed394f9f277f492026b9a0708cd92e6ef7d | commitdiff |
hwrng: exynos - Runtime suspend device after init
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.
However for this purpose autosuspend is enabled so it is safe to runtime
put just after the initialization.
Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
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.
However for this purpose autosuspend is enabled so it is safe to runtime
put just after the initialization.
Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
| drivers/char/hw_random/exynos-rng.c | diffblobblamehistory |