From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
To: <quic_cang@quicinc.com>, <quic_nitirawa@quicinc.com>,
<bvanassche@acm.org>, <avri.altman@wdc.com>,
<peter.wang@mediatek.com>, <manivannan.sadhasivam@linaro.org>,
<adrian.hunter@intel.com>, <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>,
"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"open list:ARM/Mediatek SoC support:Keyword:mediatek"
<linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support:Keyword:mediatek"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support:Keyword:mediatek"
<linux-mediatek@lists.infradead.org>
Subject: [PATCH v1 0/2] *** Remove UFS_DEVICE_QUIRK_DELAY_AFTER_LPM quirk ***
Date: Wed, 1 Oct 2025 13:57:10 -0700 [thread overview]
Message-ID: <cover.1759348507.git.quic_nguyenb@quicinc.com> (raw)
Multiple ufs device manufacturers request support for the
UFS_DEVICE_QUIRK_DELAY_AFTER_LPM quirk in the Qualcomm's platform driver.
After checking further with the major UFS manufacturers engineering teams
such as Samsung, Kioxia, SK Hynix and Micron, all the manufacturers require
this quirk. Since the quirk is needed by all the ufs device manufacturers,
remove the quirk in the ufs core driver and implement a universal delay
for all the ufs devices.
In addition to verifying with the public device's datasheets, the ufs
device manufacturer's engineering teams confirmed the required vcc
power-off time for the devices is a minimum of 1ms before vcc can be
powered on again. The existing 5ms delay implemented in the ufs core
driver seems too conservative, so reduce this time to 2ms to improve
the system resume latency.
Bao D. Nguyen (2):
scsi: ufs: core: Remove UFS_DEVICE_QUIRK_DELAY_AFTER_LPM quirk
scsi: ufs: core: Reduce the sleep before vcc can be powered on
drivers/ufs/core/ufshcd.c | 7 +++----
drivers/ufs/host/ufs-mediatek.c | 11 ++++-------
drivers/ufs/host/ufs-qcom.c | 3 ---
include/ufs/ufs_quirks.h | 7 -------
4 files changed, 7 insertions(+), 21 deletions(-)
--
2.7.4
next reply other threads:[~2025-10-01 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 20:57 Bao D. Nguyen [this message]
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
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=cover.1759348507.git.quic_nguyenb@quicinc.com \
--to=quic_nguyenb@quicinc.com \
--cc=adrian.hunter@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=quic_cang@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).