mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "avri.altman@wdc.com" <avri.altman@wdc.com>,
	"quic_cang@quicinc.com" <quic_cang@quicinc.com>,
	"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
	"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
	"manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"beanhuo@micron.com" <beanhuo@micron.com>,
	"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 v1 2/2] scsi: ufs: core: Reduce the sleep before vcc can be powered on
Date: Fri, 3 Oct 2025 03:11:03 +0000	[thread overview]
Message-ID: <4943d9d6e31b2993ee0563722b8bc38c3b1ef069.camel@mediatek.com> (raw)
In-Reply-To: <a1eaae1e-3e10-4512-bc83-ae25eacc43d6@quicinc.com>

On Thu, 2025-10-02 at 12:00 -0700, Bao D. Nguyen wrote:
> 
> Hi Peter,
> I have discussed with the major ufs vendors (Samsung, Kioxia, Micron,
> and SK Hynix) via emails. They are all in agreement that 2ms is good.
> I
> did check the current device's datasheets and 1ms is what their
> specifications require. I admit that I may have missed some very old
> ufs
> device's datasheets. However, I take the words of the ufs vendor's
> engineering teams and the current device's datasheets that the 2ms is
> good for their devices and try to improve the potentially
> conservative
> 5ms delay parameter.
> 
> Thanks, Bao
> 
> 
> 

Hi Bao,

Yes, I am concerned that legacy UFS devices may encounter errors
when upgrading the kernel if the delay is not sufficient.

Furthermore, the vendor claims that 2ms is sufficient. Is this
based on a typical scenario? or should we be concerned about 
the worst-case scenario? I am also worried that the worst-case
delay may not be enough.

Thanks
Peter


  reply	other threads:[~2025-10-03  3:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 20:57 [PATCH v1 0/2] *** Remove UFS_DEVICE_QUIRK_DELAY_AFTER_LPM quirk *** Bao D. Nguyen
2025-10-01 20:57 ` [PATCH v1 1/2] scsi: ufs: core: Remove UFS_DEVICE_QUIRK_DELAY_AFTER_LPM quirk Bao D. Nguyen
2025-10-02  7:57   ` Peter Wang (王信友)
2025-10-02 18:48     ` Bao D. Nguyen
2025-10-03  3:10       ` Peter Wang (王信友)
2025-10-03 21:11         ` Bao D. Nguyen
2025-10-07  7:02           ` Peter Wang (王信友)
2025-10-01 20:57 ` [PATCH v1 2/2] scsi: ufs: core: Reduce the sleep before vcc can be powered on Bao D. Nguyen
2025-10-02  7:59   ` Peter Wang (王信友)
2025-10-02 19:00     ` Bao D. Nguyen
2025-10-03  3:11       ` Peter Wang (王信友) [this message]
2025-10-03 21:27         ` Bao D. Nguyen
2025-10-07  7:04           ` Peter Wang (王信友)
2025-10-07 16:19             ` Bart Van Assche
2025-10-08  0:10               ` Bao D. Nguyen
2025-10-08  6:09                 ` Peter Wang (王信友)
2025-10-08  6:08               ` 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=4943d9d6e31b2993ee0563722b8bc38c3b1ef069.camel@mediatek.com \
    --to=peter.wang@mediatek.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=quic_cang@quicinc.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=quic_nitirawa@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®