Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "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>,
	"quic_ziqichen@quicinc.com" <quic_ziqichen@quicinc.com>,
	"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, 14 May 2025 09:05:09 +0000	[thread overview]
Message-ID: <f092c7a563f2f2b70ccb43340b95819adacb2ad6.camel@mediatek.com> (raw)
In-Reply-To: <486616b7-9400-4288-b4b4-c56ec628b0f3@quicinc.com>

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



  reply	other threads:[~2025-05-14  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  9:38 [PATCH v3] scsi: ufs: core: skip UFS clkscale if host asynchronous scan in progress 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 (王信友) [this message]
2025-05-21  8:56           ` Ziqi Chen

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=f092c7a563f2f2b70ccb43340b95819adacb2ad6.camel@mediatek.com \
    --to=peter.wang@mediatek.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=quic_cang@quicinc.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=quic_nitirawa@quicinc.com \
    --cc=quic_rampraka@quicinc.com \
    --cc=quic_ziqichen@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