From: Bart Van Assche <bvanassche@acm.org>
To: "Peter Wang (王信友)" <peter.wang@mediatek.com>,
"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>,
"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: Tue, 7 Oct 2025 09:19:44 -0700 [thread overview]
Message-ID: <2ce08f9f-af8c-4cac-8d66-97517eb18037@acm.org> (raw)
In-Reply-To: <85bce5dc28293f48e32b64eed5591d66c54c9e69.camel@mediatek.com>
On 10/7/25 12:04 AM, Peter Wang (王信友) wrote:
> On Fri, 2025-10-03 at 14:27 -0700, Bao D. Nguyen wrote:
>> With the current or recent offerings of ufs devices in the market,
>> the requirement is 1ms. For example, the Kioxia datasheet says
>> "Vcc shall be kept less than 0.3V for at least 1ms before it goes
>> beyond 0.3V again". Similarly other vendors have this 1ms
>> requirement. So I believe this indicates the worst case scenario.
>> I understand there may be very old devices that are upgrading the
>> kernel only. In that case I don't know the specifics for these old
>> ufs parts as mentioned.
>
> Hi Bao,
>
> Please consider using module_param_cb to set the default
> delay to 2ms(or 1ms). At the same time, we should keep the
> flexibility for devices that may require a longer delay by
> allowing them to extend the delay through a module parameter.
Why a kernel module parameter? Why can't the default delay be set by
ufshcd_variant_ops.init()?
Thanks,
Bart.
next prev parent reply other threads:[~2025-10-07 16:20 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 (王信友)
2025-10-03 21:27 ` Bao D. Nguyen
2025-10-07 7:04 ` Peter Wang (王信友)
2025-10-07 16:19 ` Bart Van Assche [this message]
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=2ce08f9f-af8c-4cac-8d66-97517eb18037@acm.org \
--to=bvanassche@acm.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).