From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ram Prakash Gupta <quic_rampraka@quicinc.com>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_cang@quicinc.com,
quic_nguyenb@quicinc.com, quic_pragalla@quicinc.com,
quic_nitirawa@quicinc.com
Subject: Re: [PATCH V2 0/2] Suspend clk scaling when there is no request
Date: Thu, 04 Jul 2024 22:48:58 -0400 [thread overview]
Message-ID: <yq18qygblkd.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240627083756.25340-1-quic_rampraka@quicinc.com> (Ram Prakash Gupta's message of "Thu, 27 Jun 2024 14:07:54 +0530")
Ram,
> 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.
Applied to 6.11/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-07-05 2:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 8:37 [PATCH V2 0/2] Suspend clk scaling when there is no request Ram Prakash Gupta
2024-06-27 8:37 ` [PATCH v2 1/2] scsi: ufs: Suspend clk scaling on " Ram Prakash Gupta
2024-06-27 16:35 ` Bart Van Assche
2024-06-27 16:59 ` Ram Prakash Gupta
2024-06-27 8:37 ` [PATCH v2 2/2] scsi: ufs: qcom: Enable suspending " Ram Prakash Gupta
2024-06-27 16:36 ` [PATCH V2 0/2] Suspend clk scaling when there is " Bart Van Assche
2024-06-27 17:06 ` Ram Prakash Gupta
2024-06-28 19:34 ` Bart Van Assche
2024-07-05 2:48 ` Martin K. Petersen [this message]
2024-07-11 3:08 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq18qygblkd.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_pragalla@quicinc.com \
--cc=quic_rampraka@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox