- 06 Aug, 2020 38 commits
-
-
Dave Airlie authored
Reviewed-by:
Thomas Zimmermann <tzimmermann@suse.de> Signed-off-by:
Dave Airlie <airlied@redhat.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200804025632.3868079-39-airlied@gmail.com
-
Dave Airlie authored
Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
-
Dave Airlie authored
This will allow different abstractions later. Acked-by:
Ben Skeggs <bskeggs@redhat.com> Signed-off-by:
-
Dave Airlie authored
Drivers should all be cleaning up their memory managers themselves now, so let the core just clean the system one up. Remove the legacy cleaning interface. Reviewed-by:
-
Dave Airlie authored
Now all drivers have been converted, drop the non-driver path. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by:
-
Dave Airlie authored
Reviewed-by:
Gerd Hoffmann <kraxel@redhat.com> Signed-off-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Don't bother returning EBUSY, nobody cares enough, if the driver has a problem, it should deal with it. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Allow the takedown path callback to be optional as well. v2: use fini for range manager Reviewed-by:
-
Dave Airlie authored
The disable path is just temporary for now, it will be dropped once has_type is gone in a later patch. v2: add docs. rename to ttm_mem_type_manager namespace Reviewed-by:
-
Dave Airlie authored
This makes it easier to cleanup things Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Remove the exit path, since this can't fail now. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Split out the vram thp init path vs the range manager init. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Use the new common manager init path. Reviewed-by:
-
Dave Airlie authored
Use new init calls to unwrap manager init Reviewed-by:
-
Dave Airlie authored
This lets the generic range mm manager be initialised by the driver. v2: add docs. rename api to range_man_init for now. Reviewed-by:
-
Dave Airlie authored
This will allow the driver to control the ordering here better. Eventually the old path will be removed. v2: add docs for new APIs. rename new path to ttm_mem_type_manager_init/set_used(for now) Reviewed-by:
-
Dave Airlie authored
This code was assuming there was a drm_mm here, don't do that call the correct API. v2: use the new exported interface. Reviewed-by:
-
Dave Airlie authored
v2: use the new exported interface. This code was poking inside a struct and assuming it was a drm_mm at the start. Call the proper API. Reviewed-by:
-
Dave Airlie authored
Acked-by:
-
Dave Airlie authored
Acked-by:
-
Dave Airlie authored
As suggested on review, just export the memory type debug for drivers to use, while also making the debug callback optional (don't need to test for system as it won't init it). rename it to be more consistent with object name for now. (we may rename all the objects later.) Reviewed-by:
-
Dave Airlie authored
The default path for populate/unpopulate is already this. Reviewed-by:
-
Dave Airlie authored
The pattern was repeated a few times, just make an inline for it. Reviewed-by:
-
Dave Airlie authored
Drop the WARN_ON and consolidate the two paths into one. Use the consolidate slowpath in the execbuf utils code. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Instead of rolling driver copies of them. v2: cleanup return handling (Ben) Reviewed-by:
-
Dave Airlie authored
The map one was used once, just inline it, and drop them both. Reviewed-by:
-
Dave Airlie authored
These two functions has the same code in them, create a common helper function instead. Reviewed-by:
-
- 05 Aug, 2020 2 commits
-
-
Tom Rix authored
clang static analysis reports this repesentative error pvr2fb.c:1049:2: warning: 1st function call argument is an uninitialized value [core.CallAndMessage] if (*cable_arg) ^~~~~~~~~~~~~~~ Problem is that cable_arg depends on the input loop to set the cable_arg[0]. If it does not, then some random value from the stack is used. A similar problem exists for output_arg. So initialize cable_arg and output_arg. Signed-off-by:Tom Rix <trix@redhat.com> Acked-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
Sam Ravnborg <sam@ravnborg.org> Link: https://patchwork.freedesktop.org/patch/msgid/20200720191845.20115-1-trix@redhat.com
-
Thomas Zimmermann authored
The initial value of the PCI option register got lost while refactoring the driver init code. Restore the setting. Signed-off-by:
kernel test robot <lkp@intel.com> Fixes: 2021708e ("drm/mgag200: Initialize PCI registers early during device setup") Cc: Lyude Paul <lyude@redhat.com> Cc: Dave Airlie <airlied@redhat.com> Cc: Sam Ravnborg <sam@ravnborg.org> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Gerd Hoffmann <kraxel@redhat.com> Cc: Emil Velikov <emil.velikov@collabora.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200804065158.21049-1-tzimmermann@suse.de
-
