summaryrefslogtreecommitdiff
path: root/scripts/lib/kdoc
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2022-12-12 19:13:38 +0300
committerAndi Shyti <andi.shyti@linux.intel.com>2023-01-10 15:10:12 +0300
commit3db9d590557da3aa2c952f2fecd3e9b703dad790 (patch)
tree3237bab98ce27eb6f920607af476964a4fd3e7ac /scripts/lib/kdoc
parent4f16749f89596c4eb65c0801c86e4a74ad6c62a9 (diff)
downloadlinux-3db9d590557da3aa2c952f2fecd3e9b703dad790.tar.xz
drm/i915/gt: Reset twice
After applying an engine reset, on some platforms like Jasperlake, we occasionally detect that the engine state is not cleared until shortly after the resume. As we try to resume the engine with volatile internal state, the first request fails with a spurious CS event (it looks like it reports a lite-restore to the hung context, instead of the expected idle->active context switch). Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: stable@vger.kernel.org Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com> Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20221212161338.1007659-1-andi.shyti@linux.intel.com
Diffstat (limited to 'scripts/lib/kdoc')
0 files changed, 0 insertions, 0 deletions