diff options
| author | Gilad Ben-Yossef | 2019-02-07 14:36:11 +0100 |
|---|---|---|
| committer | Herbert Xu | 2019-02-08 08:28:02 +0100 |
| commit | 1358c13a48c43f5e4de0c1835291837a27b9720c (patch) | |
| tree | e5ec75ed516856e6e08a1cbe1dc5f6415c20a810 /drivers/gpu/drm/i915/intel_dp.c | |
| parent | crypto: cavium/nitrox - Invoke callback after DMA unmap (diff) | |
| download | kernel-qcow2-linux-1358c13a48c43f5e4de0c1835291837a27b9720c.tar.gz kernel-qcow2-linux-1358c13a48c43f5e4de0c1835291837a27b9720c.tar.xz kernel-qcow2-linux-1358c13a48c43f5e4de0c1835291837a27b9720c.zip | |
crypto: ccree - fix resume race condition on init
We were enabling autosuspend, which is using data set by the
hash module, prior to the hash module being inited, casuing
a crash on resume as part of the startup sequence if the race
was lost.
This was never a real problem because the PM infra was using low
res timers so we were always winning the race, until commit 8234f6734c5d
("PM-runtime: Switch autosuspend over to using hrtimers") changed that :-)
Fix this by seperating the PM setup and enablement and doing the
latter only at the end of the init sequence.
Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>
Cc: stable@kernel.org # v4.20
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_dp.c')
0 files changed, 0 insertions, 0 deletions