diff options
| author | Ben Skeggs <bskeggs@redhat.com> | 2023-01-31 08:37:13 +1000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-02-22 12:59:43 +0100 |
| commit | 07a0e6d2010664f0e8eb122bb4e1a2a6e008b0e4 (patch) | |
| tree | 41cdbbad83f4c86db78130f77ab90ec0b109717b /drivers/gpu/drm/nouveau/dispnv50/curs507a.c | |
| parent | b266c2e72ef319ebc6ae298766c81bfd3ec33f57 (diff) | |
| download | linux-07a0e6d2010664f0e8eb122bb4e1a2a6e008b0e4.tar.gz | |
drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == COMPLETED
[ Upstream commit d22915d22ded21fd5b24b60d174775789f173997 ] Starting from Turing, the driver is no longer responsible for initiating DEVINIT when required as the GPU started loading a FW image from ROM and executing DEVINIT itself after power-on. However - we apparently still need to wait for it to complete. This should correct some issues with runpm on some systems, where we get control of the HW before it's been fully reinitialised after resume from suspend. Signed-off-by: Ben Skeggs <bskeggs@redhat.com> Reviewed-by: Lyude Paul <lyude@redhat.com> Signed-off-by: Lyude Paul <lyude@redhat.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230130223715.1831509-1-bskeggs@redhat.com Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/gpu/drm/nouveau/dispnv50/curs507a.c')
0 files changed, 0 insertions, 0 deletions