[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240626103033.2332-1-quic_rampraka@quicinc.com>
Date: Wed, 26 Jun 2024 16:00:31 +0530
From: Ram Prakash Gupta <quic_rampraka@...cinc.com>
To: "James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: Alim Akhtar <alim.akhtar@...sung.com>, Avri Altman <avri.altman@....com>,
Bart Van Assche <bvanassche@....org>, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
quic_cang@...cinc.com, quic_nguyenb@...cinc.com,
quic_rampraka@...cinc.com, quic_pragalla@...cinc.com,
quic_nitirawa@...cinc.com
Subject: [PATCH V1 0/2] Suspend clk scaling when there is no request
Currently ufs clk scaling is getting suspended only when the
clks are scaled down, but next when high load is generated its
adding a huge amount of latency in scaling up the clk and complete
the request post that.
Now if the scaling is suspended in its existing state, and when high
load is generated it is helping improve the random performance KPI by
28%. So suspending the scaling when there is no request. And the clk
would be put in low scaled state when the actual request load is low.
Making this change as optional for other vendor by having the check
enabled using vops as for some vendor suspending without bringing the
clk in low scaled state might have impact on power consumption on the
SoC.
Ram Prakash Gupta (2):
scsi: ufs: Suspend clk scaling on no request
scsi: ufs: qcom: Enable suspending clk scaling on no request
drivers/ufs/core/ufshcd.c | 3 ++-
drivers/ufs/host/ufs-qcom.c | 2 ++
include/ufs/ufshcd.h | 1 +
3 files changed, 5 insertions(+), 1 deletion(-)
--
2.17.1
Powered by blists - more mailing lists