Re: [PATCH] drm/panthor: Record devfreq busy as soon as a job is started

2024-07-04 Thread Steven Price
On 03/07/2024 16:56, Steven Price wrote: > 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

Re: [PATCH] drm/panthor: Record devfreq busy as soon as a job is started

2024-07-03 Thread Liviu Dudau
On Wed, Jul 03, 2024 at 04:56:46PM +0100, Steven Price wrote: > 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

Re: [PATCH] drm/panthor: Record devfreq busy as soon as a job is started

2024-07-03 Thread Boris Brezillon
On Wed, 3 Jul 2024 16:56:46 +0100 Steven Price wrote: > 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

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

2024-07-03 Thread Steven Price
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 acc