diff options
| author | Marcin Slusarz <marcin.slusarz@gmail.com> | 2012-12-25 21:13:22 +0400 |
|---|---|---|
| committer | Ben Skeggs <bskeggs@redhat.com> | 2013-01-13 12:07:45 +0400 |
| commit | f20ebd034eab43fd38c58b11c5bb5fb125e5f7d7 (patch) | |
| tree | ed2a7bb7dfc91febaa62b926e79714ea71a9a790 /lib/locking-selftest-rlock.h | |
| parent | 92441b2263866c27ef48137be5aa6c8c692652fc (diff) | |
| download | linux-f20ebd034eab43fd38c58b11c5bb5fb125e5f7d7.tar.xz | |
drm/nv17-50: restore fence buffer on resume
Since commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 "drm/nouveau/fence:
convert to exec engine, and improve channel sync" nouveau fence sync
implementation for nv17-50 and nvc0+ started to rely on state of fence buffer
left by previous sync operation. But as pinned bo's (where fence state is
stored) are not saved+restored across suspend/resume, we need to do it
manually.
nvc0+ was fixed by commit d6ba6d215a538a58f0f0026f0961b0b9125e8042
"drm/nvc0/fence: restore pre-suspend fence buffer context on resume".
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=50121
Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'lib/locking-selftest-rlock.h')
0 files changed, 0 insertions, 0 deletions