From: Ziqi Chen <quic_ziqichen@quicinc.com>
To: "Peter Wang (王信友)" <peter.wang@mediatek.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"quic_rampraka@quicinc.com" <quic_rampraka@quicinc.com>,
"quic_cang@quicinc.com" <quic_cang@quicinc.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
"luca.weiss@fairphone.com" <luca.weiss@fairphone.com>,
"konrad.dybcio@oss.qualcomm.com" <konrad.dybcio@oss.qualcomm.com>,
"junwoo80.lee@samsung.com" <junwoo80.lee@samsung.com>,
"mani@kernel.org" <mani@kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"manivannan.sadhasivam@linaro.org"
<manivannan.sadhasivam@linaro.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] scsi: ufs: core: skip UFS clkscale if host asynchronous scan in progress
Date: Wed, 21 May 2025 16:56:02 +0800 [thread overview]
Message-ID: <b7b0b907-8f5c-481c-9a68-cb3e20b59cb0@quicinc.com> (raw)
In-Reply-To: <f092c7a563f2f2b70ccb43340b95819adacb2ad6.camel@mediatek.com>
On 5/14/2025 5:05 PM, Peter Wang (王信友) wrote:
> On Wed, 2025-05-14 at 15:25 +0800, Ziqi Chen wrote:
>>
>> Hi Bart,
>>
>> I tried the scan_mutex, from debugging logs, it seems okay for now.
>> I will provide to our internal test team for stability test.
>> And I will try to collect the extra time spent on clock scaling
>> path with applying scan_mutex.
>> If everything is fine, I will update a new version.
>>
>> BRs,
>> Ziqi
>>
>>
>>
>
> Hi Ziqi,
>
> Could we enable devfreq when checking if hba->luns_avail equals 1
> in ufshcd_device_configure?
> I think we can use flow to ensure correctness; it doesn't
> necessarily need to be protected by a mutex.
>
> Thanks
> Peter
Hi Peter,
Thanks for your suggestion, and sorry for the late response—I was out of
office last week.
It looks like checking hba->luns_avail == 1 in ufshcd_device_configure
before enabling devfreq can ensure correctness. But I think the
function name 'ufshcd_device_configure' suggests that enabling devfreq
inside it is not reasonable. That’s another same reason why we moved
ufshcd_devfreq_init() out of ufshcd_add_lus() in this patch.
BRs,
Ziqi
>
>
prev parent reply other threads:[~2025-05-21 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 9:38 Ziqi Chen
2025-05-08 16:06 ` Bart Van Assche
2025-05-09 5:02 ` Ziqi Chen
2025-05-12 22:31 ` Bart Van Assche
2025-05-14 7:25 ` Ziqi Chen
2025-05-14 9:05 ` Peter Wang (王信友)
2025-05-21 8:56 ` Ziqi Chen [this message]
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=b7b0b907-8f5c-481c-9a68-cb3e20b59cb0@quicinc.com \
--to=quic_ziqichen@quicinc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=junwoo80.lee@samsung.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=neil.armstrong@linaro.org \
--cc=peter.wang@mediatek.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@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
all inboxes | Powered by JetHome®