author | Tero Kristo <t-kristo@ti.com> | |
Thu, 4 Aug 2016 10:28:42 +0000 (13:28 +0300) | ||
committer | Herbert Xu <herbert@gondor.apana.org.au> | |
Tue, 13 Sep 2016 12:22:06 +0000 (20:22 +0800) | ||
commit | f303b455bb95233297c179b525a851a792e469b2 | |
tree | 5e820d3a589b8c7f132ce04d4bd54b42dbd9963a | tree | snapshot (tar.xz tar.gz zip) |
parent | cb8d5c8346640f3622bc832fede4b514096f762e | commit | diff |
crypto: omap-aes - use runtime_pm autosuspend for clock handling
Calling runtime PM API at the cra_init/exit is bad for power management
purposes, as the lifetime for a CRA can be very long. Instead, use
pm_runtime autosuspend approach for handling the device clocks. Clocks
are enabled when they are actually required, and autosuspend disables
these if they have not been used for a sufficiently long time period.
By default, the timeout value is 1 second.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Calling runtime PM API at the cra_init/exit is bad for power management
purposes, as the lifetime for a CRA can be very long. Instead, use
pm_runtime autosuspend approach for handling the device clocks. Clocks
are enabled when they are actually required, and autosuspend disables
these if they have not been used for a sufficiently long time period.
By default, the timeout value is 1 second.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
drivers/crypto/omap-aes.c | diff | blob | history |