On Tue, Aug 11, 2026 at 01:23:38PM +0200, Boris Brezillon wrote: > By scheduling an immediate tick, we already force idleness re-evaluation, > which gives the scheduler the opportunity to evict idle groups > and schedule onces that have jobs pending. > > Signed-off-by: Boris Brezillon <[email protected]>
Reviewed-by: Liviu Dudau <[email protected]> Best regards, Liviu > --- > drivers/gpu/drm/panthor/panthor_sched.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/drivers/gpu/drm/panthor/panthor_sched.c > b/drivers/gpu/drm/panthor/panthor_sched.c > index 5832dccfc093..baa06731797c 100644 > --- a/drivers/gpu/drm/panthor/panthor_sched.c > +++ b/drivers/gpu/drm/panthor/panthor_sched.c > @@ -1733,8 +1733,6 @@ static void csg_slot_process_idle_event_locked(struct > panthor_device *ptdev, u32 > > lockdep_assert_held(&sched->lock); > > - sched->might_have_idle_groups = true; > - > /* Schedule a tick so we can evict idle groups and schedule non-idle > * ones. This will also update runtime PM and devfreq busy/idle states, > * so the device can lower its frequency or get suspended. > > -- > 2.55.0 > -- ==================== | I would like to | | fix the world, | | but they're not | | giving me the | \ source code! / --------------- ¯\_(ツ)_/¯
