diff options
| author | Steven Price <steven.price@arm.com> | 2024-07-03 16:56:46 +0100 |
|---|---|---|
| committer | Steven Price <steven.price@arm.com> | 2024-07-04 09:29:55 +0100 |
| commit | 896868eded124059023be0af92d68cdaf9b4de70 (patch) | |
| tree | a7d2b522a7bd169b2a597f476c5f48c81961855d /drivers/gpu/drm | |
| parent | 685505219723147b10353b9018ab0c8706934290 (diff) | |
| download | linux-896868eded124059023be0af92d68cdaf9b4de70.tar.gz linux-896868eded124059023be0af92d68cdaf9b4de70.tar.bz2 linux-896868eded124059023be0af92d68cdaf9b4de70.zip | |
drm/panthor: Record devfreq busy as soon as a job is started
If a queue is already assigned to the hardware, then a newly submitted
job can start straight away without waiting for the tick. However in
this case the devfreq infrastructure isn't notified that the GPU is
busy. By the time the tick happens the job might well have finished and
no time will be accounted for the GPU being busy.
Fix this by recording the GPU as busy directly in queue_run_job() in the
case where there is a CSG assigned and therefore we just ring the
doorbell.
Fixes: de8548813824 ("drm/panthor: Add the scheduler logical block")
Signed-off-by: Steven Price <steven.price@arm.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240703155646.80928-1-steven.price@arm.com
Diffstat (limited to 'drivers/gpu/drm')
| -rw-r--r-- | drivers/gpu/drm/panthor/panthor_sched.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c index 79ffcbc41d78..42929e147107 100644 --- a/drivers/gpu/drm/panthor/panthor_sched.c +++ b/drivers/gpu/drm/panthor/panthor_sched.c @@ -2926,6 +2926,7 @@ queue_run_job(struct drm_sched_job *sched_job) pm_runtime_get(ptdev->base.dev); sched->pm.has_ref = true; } + panthor_devfreq_record_busy(sched->ptdev); } done_fence = dma_fence_get(job->done_fence); |