> On 8/31/23 06:08, peter.wang@xxxxxxxxxxxx wrote: >> When ufshcd_clk_scaling_suspend_work(Thread A) running and new command >> coming, ufshcd_clk_scaling_start_busy(Thread B) may get host_lock >> after Thread A first time release host_lock. Then Thread A second time >> get host_lock will set clk_scaling.window_start_t = 0 which scale up >> clock abnormal next polling_ms time. >> Also inlines another __ufshcd_suspend_clkscaling calls. > > Reviewed-by: Bart Van Assche <bvanassche@xxxxxxx> Applied 1-3 to 6.7/scsi-staging, thanks! -- Martin K. Petersen Oracle Linux Engineering
