aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/mem-phys-addr.py
diff options
context:
space:
mode:
authorGilad Ben-Yossef <[email protected]>2019-02-07 13:36:11 +0000
committerHerbert Xu <[email protected]>2019-02-08 07:28:02 +0000
commit1358c13a48c43f5e4de0c1835291837a27b9720c (patch)
treee5ec75ed516856e6e08a1cbe1dc5f6415c20a810 /tools/perf/scripts/python/mem-phys-addr.py
parentcrypto: cavium/nitrox - Invoke callback after DMA unmap (diff)
downloadkernel-1358c13a48c43f5e4de0c1835291837a27b9720c.tar.gz
kernel-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 <[email protected]> Cc: Vincent Guittot <[email protected]> Cc: [email protected] # v4.20 Signed-off-by: Herbert Xu <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions