Re: [PATCH 1/3] drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == COMPLETED

2023-01-30 Thread Ben Skeggs
On Tue, 31 Jan 2023 at 09:19, Lyude Paul wrote: > > For the whole series: > > Reviewed-by: Lyude Paul > > Will push to drm-misc-fixes in just a moment Thank you Lyude! Much appreciated. Ben. > > On Tue, 2023-01-31 at 08:37 +1000, Ben Skeggs wrote: > > Starting from Turing, the driver is no

Re: [PATCH 1/3] drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == COMPLETED

2023-01-30 Thread Lyude Paul
For the whole series: Reviewed-by: Lyude Paul Will push to drm-misc-fixes in just a moment On Tue, 2023-01-31 at 08:37 +1000, Ben Skeggs wrote: > 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

[PATCH 1/3] drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == COMPLETED

2023-01-30 Thread Ben Skeggs
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