diff options
| author | Peter Wang <[email protected]> | 2023-08-31 21:08:24 +0800 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2023-10-13 13:16:09 -0400 |
| commit | 1d969731b87f122108c50a64acfdbaa63486296e (patch) | |
| tree | 24a2e18e59edcc7d59ef5aa2244f6b4412f62fc3 | |
| parent | b6f2e063017b92491976a40c32a0e4b3c13e7d2f (diff) | |
scsi: ufs: core: Only suspend clock scaling if scaling down
If clock scale up and suspend clock scaling, ufs will keep high
performance/power mode but no read/write requests on going. It is logic
wrong and have power concern.
Signed-off-by: Peter Wang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Bart Van Assche <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
| -rw-r--r-- | drivers/ufs/core/ufshcd.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c index c45737c5adb9..c6c53bdd3e43 100644 --- a/drivers/ufs/core/ufshcd.c +++ b/drivers/ufs/core/ufshcd.c @@ -1430,7 +1430,7 @@ static int ufshcd_devfreq_target(struct device *dev, ktime_to_us(ktime_sub(ktime_get(), start)), ret); out: - if (sched_clk_scaling_suspend_work) + if (sched_clk_scaling_suspend_work && !scale_up) queue_work(hba->clk_scaling.workq, &hba->clk_scaling.suspend_work); |