On Wed, Oct 4, 2023 at 2:25 PM <peter.wang@xxxxxxxxxxxx> wrote: > > From: Peter Wang <peter.wang@xxxxxxxxxxxx> > > If dev command timeout, clk_scaling.active_reqs is not decrease > and cause clock scaling framework abnormal. But it is complicated to > handle different dev command timeout case in legacy mode or mcq mode. > Besides, dev cmd is rare used and busy time is short. > So remove clock scaling busy window for dev cmd is properly. > Same as uic or tm cmd which doesn't update busy window too. > > Signed-off-by: Peter Wang <peter.wang@xxxxxxxxxxxx> It makes sense to me since clock scaling is aimed at balancing performance and power consumption for different workloads, which should be data workloads rather than device commands. Reviewed-by: Stanley Chu <stanley.chu@xxxxxxxxxxxx>
