- 07 Aug, 2020 14 commits
-
-
Navid Emamdoost authored
in panfrost_perfcnt_enable_locked, pm_runtime_get_sync is called which increments the counter even in case of failure, leading to incorrect ref count. In case of failure, decrement the ref count before returning. Acked-by:
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Signed-off-by:
Navid Emamdoost <navid.emamdoost@gmail.com> Signed-off-by:
Rob Herring <robh@kernel.org> Link: https://patchwork.freedesktop.org/patch/msgid/20200614063619.44944-1-navid.emamdoost@gmail.com
-
Clément Péron authored
Some OPP tables specify voltage for each frequency. Devfreq can handle these regulators but they should be get only 1 time to avoid issue and know who is in charge. If OPP table is probe don't init regulator. Reviewed-by:
Steven Price <steven.price@arm.com> Reviewed-by:
Clément Péron <peron.clem@gmail.com> Signed-off-by:
-
Clément Péron authored
We will later introduce regulators managed by OPP. Only alloc regulators when it's needed. This also help use to release the regulators only when they are allocated. Reviewed-by:
-
Clément Péron authored
Later we will introduce devfreq probing regulator if they are present. As regulator should be probe only one time we need to get this logic in the device_init(). panfrost_device is already taking care of devfreq_resume() and devfreq_suspend(), so it's not totally illogic to move the devfreq_init() and devfreq_fini() here. Reviewed-by:
-
Clément Péron authored
Rename goto labels in device_init it will be easier to maintain. Reviewed-by:
-
Clément Péron authored
Introduce a boolean to know if opp table has been added. With this, we can call panfrost_devfreq_fini() in case of error and release what has been initialised. Reviewed-by:
-
Clément Péron authored
Convert busy_count to a simple int protected by spinlock. Reviewed-by:
-
Clément Péron authored
Introduce a proper panfrost_devfreq to deal with devfreq variables. Reviewed-by:
-
Clément Péron authored
This use devfreq variable that will be lock with spinlock in future patches. We should either introduce a function to access this one but as devfreq is optional let's just remove it. Reviewed-by:
-
Clément Péron authored
Don't include not required headers and sort them. Reviewed-by:
-
Clément Péron authored
This declaration can be avoided so change it. Reviewed-by:
-
Tomeu Vizoso authored
Mesa now supports some Bifrost devices, so enable it. Tested-by:
Heiko Stuebner <heiko@sntech.de> Reviewed-by:
Tomeu Vizoso <tomeu.vizoso@collabora.com> Signed-off-by:
-
Tomeu Vizoso authored
Bifrost devices do support the flush reduction feature, so on first job submit we were trying to read the register while still powered off. If the GPU is powered off, the feature doesn't bring any benefit, so don't try to read. Tested-by:
-
Christian König authored
We need to allocate that manually now. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Michel Dänzer <mdaenzer@redhat.com> Tested-by:
-
- 06 Aug, 2020 26 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:
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:
-
