Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ziqi Chen <quic_ziqichen@quicinc.com>
Cc: quic_cang@quicinc.com, bvanassche@acm.org, mani@kernel.org,
	beanhuo@micron.com, avri.altman@wdc.com,
	junwoo80.lee@samsung.com, martin.petersen@oracle.com,
	quic_nguyenb@quicinc.com, quic_nitirawa@quicinc.com,
	quic_rampraka@quicinc.com, neil.armstrong@linaro.org,
	luca.weiss@fairphone.com, konrad.dybcio@oss.qualcomm.com,
	peter.wang@mediatek.com, linux-arm-msm@vger.kernel.org,
	linux-scsi@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v4] scsi: ufs: core: Don't perform UFS clkscale if host asyn scan in progress
Date: Tue, 27 May 2025 21:58:25 -0400	[thread overview]
Message-ID: <yq1ldqhijig.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250522081233.2358565-1-quic_ziqichen@quicinc.com> (Ziqi Chen's message of "Thu, 22 May 2025 16:12:28 +0800")


Ziqi,

> When preparing for UFS clock scaling, the UFS driver will quiesce all
> sdevs queues in the UFS SCSI host tagset list and then unquiesce them
> when UFS clock scaling unpreparing. If the UFS SCSI host async scan is
> in progress at this time, some LUs may be added to the tagset list
> between UFS clkscale prepare and unprepare. This can cause two issues:

Applied to 6.16/scsi-staging, thanks!

-- 
Martin K. Petersen

  parent reply	other threads:[~2025-05-28  1:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  8:12 [PATCH v4] scsi: ufs: core: Don't perform UFS clkscale if host asyn scan in progress Ziqi Chen
2025-05-27 21:24 ` Bart Van Assche
2025-05-28  1:58 ` Martin K. Petersen [this message]
2025-06-03  2:35 ` Martin K. Petersen
2025-07-25  9:13 ` Peter Wang (王信友)
2025-07-25 14:54   ` Bart Van Assche
2025-07-28  6:34     ` Peter Wang (王信友)
2025-07-29  3:02       ` Ziqi Chen
2025-07-30 12:55         ` Peter Wang (王信友)
2025-07-30 15:37           ` Bart Van Assche
2025-07-30 15:42             ` Bart Van Assche
2025-07-30 15:50           ` Bart Van Assche
2025-08-04  7:54             ` Ziqi Chen
2025-08-04  9:41               ` Peter Wang (王信友)
2025-08-04 12:43               ` Peter Wang (王信友)
2025-08-05  6:03                 ` Ziqi Chen
2025-08-05  7:39                   ` Peter Wang (王信友)

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=yq1ldqhijig.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=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=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 \
    --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