From: Manish Pandey <quic_mapa@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_cang@quicinc.com>,
<quic_nguyenb@quicinc.com>, <quic_nitirawa@quicinc.com>,
<quic_bhaskarv@quicinc.com>, <quic_narepall@quicinc.com>,
<quic_rampraka@quicinc.com>
Subject: [PATCH 0/3] add fixup_dev_quirks vops for ufs-qcom
Date: Tue, 20 Aug 2024 18:07:53 +0530 [thread overview]
Message-ID: <20240820123756.24590-1-quic_mapa@quicinc.com> (raw)
Add fixup_dev_quirk vops in QCOM UFS platforms and provide
an initial vendor-specific device quirk table.
Micron and Skhynix UFS device needs DELAY_BEFORE_LPM quirk to have a delay
before VCC is powered off. So add Micron and Skhynix vendors ID and this
quirk for both.
Toshiba UFS devices require delay after VCC power rail is turned-off in QCOM
platforms. Hence add Toshiba vendor ID and DELAY_AFTER_LPM quirk for Toshiba
UFS devices in QCOM platforms.
Manish Pandey (3):
scsi: ufs: ufs-qcom: add fixup_dev_quirks vops
scsi: ufs: ufs-qcom: Add DELAY_BEFORE_LPM quirk for Micron and Skhynix
scsi: ufs: ufs-qcom: Apply DELAY_AFTER_LPM quirk for Toshiba devices
drivers/ufs/host/ufs-qcom.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
--
2.17.1
next reply other threads:[~2024-08-20 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 12:37 Manish Pandey [this message]
2024-08-20 12:37 ` [PATCH 1/3] scsi: ufs: ufs-qcom: add fixup_dev_quirks vops Manish Pandey
2024-08-20 21:32 ` Bart Van Assche
2024-08-20 12:37 ` [PATCH 2/3] scsi: ufs: ufs-qcom: Add DELAY_BEFORE_LPM quirk for Micron and Skhynix Manish Pandey
2024-08-20 21:33 ` Bart Van Assche
2024-08-20 12:37 ` [PATCH 3/3] scsi: ufs: ufs-qcom: Apply DELAY_AFTER_LPM quirk for Toshiba devices Manish Pandey
2024-08-20 21:35 ` Bart Van Assche
2024-08-27 5:06 ` MANISH PANDEY
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=20240820123756.24590-1-quic_mapa@quicinc.com \
--to=quic_mapa@quicinc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-arm-msm@vger.kernel.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_bhaskarv@quicinc.com \
--cc=quic_cang@quicinc.com \
--cc=quic_narepall@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rampraka@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®