talos-op-linux/drivers/gpu/drm/nouveau, branch master

drm/nouveau/kms/gv100-: avoid sending a core update until the first modeset

2020-02-03T11:36:54+00:00

The OR routing logic in NVKM does not expect to receive supervisor interrupts until the DD has provided consistent information on the ORs it's using and the EVO/NVD assembly state to match. The combination of changing window ownership + core channel update during display init triggered a situation where we'd disconnect an OR from the pad it was meant to still be driving on some systems. Signed-off-by: Ben Skeggs

drm/nouveau/kms/gv100-: move window ownership setup into modesetting path

2020-02-03T11:36:54+00:00

For various complicated reasons, we need to avoid sending a core update method during display init. Something, which we've been required to do on GV100 and up because we've been assigning windows to heads there and the HW is rather picky about when that's allowed. This moves window assignment into the modesetting path at a point where it's much safer to send our first update methods to NVDisplay. Signed-off-by: Ben Skeggs

drm/nouveau/disp/gv100-: halt NV_PDISP_FE_RM_INTR_STAT_CTRL_DISP_ERROR storms

2020-02-03T11:36:54+00:00

Signed-off-by: Ben Skeggs

drm/nouveau/fb/gp102-: allow module to load even when scrubber binary is missing

2020-01-29T05:49:56+00:00

Without relaxing this requirement, TU10x boards will fail to load without an updated linux-firmware, and TU11x will completely fail to load because FW isn't available yet. Signed-off-by: Ben Skeggs

drm/nouveau/acr: return error when registering LSF if ACR not supported

2020-01-29T05:49:56+00:00

This fixes an oops on TU11x GPUs where SEC2 attempts to register its falcon, and triggers a NULL-pointer deref because ACR isn't yet supported. Signed-off-by: Ben Skeggs

drm/nouveau/disp/gv100-: not all channel types support reporting error codes

2020-01-29T05:49:56+00:00

Signed-off-by: Ben Skeggs

drm/nouveau/disp/nv50-: prevent oops when no channel method map provided

2020-01-29T05:49:56+00:00

The implementations for most channel types contains a map of methods to priv registers in order to provide debugging info when a disp exception has been raised. This info is missing from the implementation of PIO channels as they're rather simplistic already, however, if an exception is raised by one of them, we'd end up triggering a NULL-pointer deref. Not ideal... Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=206299 Signed-off-by: Ben Skeggs

drm/nouveau: support synchronous pushbuf submission

2020-01-29T05:49:56+00:00

This is useful for debugging GPU hangs. Signed-off-by: Ben Skeggs

drm/nouveau: signal pending fences when channel has been killed

2020-01-29T05:49:47+00:00

Signed-off-by: Ben Skeggs

drm/nouveau: reject attempts to submit to dead channels

2020-01-29T05:49:47+00:00

Signed-off-by: Ben Skeggs