drm/panthor: Record devfreq busy as soon as a job is started

[ Upstream commit 896868eded ]

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: de85488138 ("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
Signed-off-by: Sasha Levin <sashal@kernel.org>

This commit is contained in:

Steven Price

2024-07-03 16:56:46 +01:00

committed by

Greg Kroah-Hartman

parent 8b833796fa

commit 35f45d148d

1 changed files with 1 additions and 0 deletions

									
										drivers/gpu/drm/panthor/panthor_sched.c
									
		+1
		
												View File
												
				@@ -2939,6 +2939,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);

					}

					/* Update the last fence. */