- 18 May, 2018 40 commits
-
-
Ben Skeggs authored
No real surprises here so far. Signed-off-by:Ben Skeggs <bskeggs@redhat.com>
-
Ben Skeggs authored
Appears to be compatible with GP100. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Will be required to support Volta. Signed-off-by: -
Ben Skeggs authored
Required to eventually support DRM colour management APIs, and to support Volta. Signed-off-by: -
Ben Skeggs authored
When only the position of a window changes, there's no need to submit an image update as well. Will be required to support the overlays, and Volta windows. Signed-off-by: -
Ben Skeggs authored
Window visibility is going to become a little more complicated with the upcoming LUT changes, so store the calculated value to avoid needing to recalculate the armed state again. Signed-off-by: -
Ben Skeggs authored
This is just cleaning up some left-overs from when we needed a custom legacy page flip implementation. Signed-off-by: -
Ben Skeggs authored
This will be required to support Volta. Signed-off-by: -
Ben Skeggs authored
Instead of windows returning their core channel interlock mask if they know core has been modified, it's recorded unconditionally and used if required when update methods are emitted. This will be required to support Volta. Signed-off-by: -
Ben Skeggs authored
GV100 doesn't support MST, use the information provided in VBIOS tables to detect its presence instead. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
This will be required to support additional HW features. Signed-off-by: -
Ben Skeggs authored
This is a simplification that'll be used to improve interlock handling. Signed-off-by: -
Ben Skeggs authored
This will be required to support Volta, where window ID != head. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
There should be no code changes here, just shuffling stuff around. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Removes duplicated code from OR-specific functions. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
We don't support address-only transactions there. Signed-off-by: -
Ben Skeggs authored
The code is about to be split up, and this matches dispnv04. Signed-off-by: -
Ben Skeggs authored
This function is useful outside of DRM code. Signed-off-by: -
Ben Skeggs authored
Hasn't been required for a long time. Signed-off-by: -
Ben Skeggs authored
Signed-off-by: -
Ben Skeggs authored
Fences attached to deferred client work items now originate from channels belonging to the client, meaning we can be certain they've been signalled before we destroy a client. This closes a race that could happen if the dma_fence_wait_timeout() call didn't succeed. When the fence was later signalled, a use-after-free was possible. Signed-off-by: -
Ben Skeggs authored
As VMAs are per-client, unlike buffers, this allows us to avoid referencing foreign fences (those that belong to another client/driver) from the client deferred work handler, and prevent some not-fun race conditions that can be triggered when a fence stalls. Signed-off-by: -
Ben Skeggs authored
An upcoming patch will use these to fix issues related to the deferred unmapping of GEM objects. Signed-off-by: -
Ben Skeggs authored
We previously only did this for push buffers, but an upcoming patch will need to attach fences to all VMAs to resolve another issue. Signed-off-by: -
Ben Skeggs authored
Signed-off-by:
-
