- 06 Aug, 2020 40 commits
-
-
Dave Airlie authored
This name better reflects what the object does. I didn't rename all the pointers it seemed too messy. Signed-off-by:
Dave Airlie <airlied@redhat.com> Acked-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Ben Skeggs <bskeggs@redhat.com> Signed-off-by:
-
Dave Airlie authored
This name makes a lot more sense, since these are about managing driver resources rather than just memory ranges. Acked-by:
-
Dave Airlie authored
The generic manager is called the range manager now, rename the file and some internals. Reviewed-by:
-
Dave Airlie authored
This converts vmwgfx over to using an interface to set the in use and check the in use flag. Reviewed-by:
-
Dave Airlie authored
under driver control, this flag isn't needed anymore, remove the API that used to access it, and consoldiate with the used api. Reviewed-by:
-
Dave Airlie authored
The driver now controls these, the core just controls the system memory one. v2: init sysman explicitly and assign it as a driver manager to simplify the lookup sequence. Reviewed-by:
-
Dave Airlie authored
This link isn't needed anymore, drop it from the init interface. Reviewed-by:
-
Dave Airlie authored
Just store the device in the private so the link can be removed from the manager Reviewed-by:
-
Dave Airlie authored
This isn't needed anymore by any drivers. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
This makes it easier to move these to a driver allocated system Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
This will get removed eventually and all drivers will use this. Reviewed-by:
-
Dave Airlie authored
Other users of this should notice this change and switch to wrapper. Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
Gerd Hoffmann <kraxel@redhat.com> Signed-off-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
Reviewed-by:
Thomas Zimmermann <tzimmermann@suse.de> Signed-off-by:
-
Dave Airlie authored
Reviewed-by:
-
Dave Airlie authored
This will allow different abstractions later. Acked-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:
-
Dave Airlie authored
Reviewed-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:
-
