drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == COMPLETED
authorBen Skeggs <bskeggs@redhat.com>
Mon, 30 Jan 2023 22:37:13 +0000 (08:37 +1000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 22 Feb 2023 11:57:02 +0000 (12:57 +0100)
commit5027084bc09746f74e26bff45223ede8fc8b50aa
treecdabd59d49fe840543b7bf4a98ddd154951a81d0
parent4fdc19e4fa238e4a12983c54dc1d0d201a00dc18
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>
drivers/gpu/drm/nouveau/nvkm/subdev/devinit/tu102.c