From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"quic_rampraka@quicinc.com" <quic_rampraka@quicinc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
"quic_sartgarg@quicinc.com" <quic_sartgarg@quicinc.com>,
"quic_bhaskarv@quicinc.com" <quic_bhaskarv@quicinc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"quic_narepall@quicinc.com" <quic_narepall@quicinc.com>,
"quic_pragalla@quicinc.com" <quic_pragalla@quicinc.com>,
"quic_cang@quicinc.com" <quic_cang@quicinc.com>
Subject: Re: [PATCH 1/1] Revert "scsi: ufs: core: Only suspend clock scaling if scaling down"
Date: Thu, 25 Apr 2024 13:15:16 +0000 [thread overview]
Message-ID: <5e71880541ad80f545f045816ab9f13d4a89003a.camel@mediatek.com> (raw)
In-Reply-To: <2d0c0aee-0dcb-7ac3-907c-ee477d5fc376@quicinc.com>
On Wed, 2024-04-24 at 14:44 +0530, Ram Prakash Gupta wrote:
>
> Hi Peter,
>
> I tried different dvfs settings, none is helping including enlarged
> polling period time, its degrading perf numbers as its taking longer
> time to scale up when the load is high and clk is low.
>
> I checked from power side on qualcomm boards, suspending with zero
> request is not impacting power hence I am consider a vops to add
> which
> can help your use case too, I tested this vops and it works fine on
> qualcomm boards.
>
> here is a small snippet of a different approach using vops, which I
> am
> planning to push under a separate mail subject to remove this
> deadlock
> between mediatek and qualcomm, scaling config.
>
> - if (sched_clk_scaling_suspend_work && !scale_up)
> + if (sched_clk_scaling_suspend_work &&
> hba->clk_scaling.no_req_suspend)
> + queue_work(hba->clk_scaling.workq,
> + &hba->clk_scaling.suspend_work);
>
Hi Ram,
It is weird for me that if no_req_suspend is true, queue suspend work?
Dosen't "no_req_suspend" simply mean "do not suspend"?
Thanks
Peter
> + else if (sched_clk_scaling_suspend_work && !scale_up)
>
> Here no_req_suspend would be false by default, so would hit else if
> case, which is desirable for mediatek boards. For qualcomm,
> no_req_suspend would set it to true via vops. please let me know if
> this
> is ok for you.
>
> Thanks,
> Ram
next prev parent reply other threads:[~2024-04-25 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 5:34 [PATCH 1/1] Revert "scsi: ufs: core: Only suspend clock scaling if scaling down" Ram Prakash Gupta
2024-02-28 18:52 ` Bart Van Assche
2024-03-05 6:23 ` Ram Prakash Gupta
2024-02-29 7:51 ` Peter Wang (王信友)
2024-03-05 7:29 ` Ram Prakash Gupta
2024-03-05 12:55 ` Peter Wang (王信友)
2024-04-24 9:14 ` Ram Prakash Gupta
2024-04-25 13:15 ` Peter Wang (王信友) [this message]
2024-04-29 5:32 ` Ram Prakash Gupta
2024-03-03 11:53 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=5e71880541ad80f545f045816ab9f13d4a89003a.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_bhaskarv@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_narepall@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_pragalla@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=quic_sartgarg@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;
as well as URLs for NNTP newsgroup(s).