diff options
| author | Alexandre Courbot <acourbot@nvidia.com> | 2016-04-01 15:40:59 +0900 |
|---|---|---|
| committer | Ben Skeggs <bskeggs@redhat.com> | 2016-05-20 14:43:04 +1000 |
| commit | c6007dc4e55e1a483c4d1e32dc1055b41aeacfc1 (patch) | |
| tree | f2114f0010978daed3c954fb88e5b605bc02170f /Documentation | |
| parent | 4dc28134a8c124aa01b441e1e5b8b54312edc5dd (diff) | |
drm/nouveau/devinit/gf100: make devinit on resume safer
In case of successful suspend, devinit will have to be run and this is
the behavior currently hardcoded. However, as FD bug 94725 suggests,
there might be cases where runtime suspend leaves the GPU powered, and
in such cases devinit should not be run on resume.
On GF100+ we have a reliable way to know whether we need to run devinit.
Use it instead of blindly trusting the flag set by nvkm_devinit_fini().
The code around the NvForcePost also needs to be slightly reworked in
order to keep working.
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Suggested-by: Dave Airlie <airlied@redhat.com>
Suggested-by: Karol Herbst <nouveau@karolherbst.de>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions