[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e23410b-7c79-4df7-acf8-32d2b1af6bee@acm.org>
Date: Tue, 20 Aug 2024 14:33:45 -0700
From: Bart Van Assche <bvanassche@....org>
To: Manish Pandey <quic_mapa@...cinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: linux-arm-msm@...r.kernel.org, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, quic_cang@...cinc.com,
quic_nguyenb@...cinc.com, quic_nitirawa@...cinc.com,
quic_bhaskarv@...cinc.com, quic_narepall@...cinc.com,
quic_rampraka@...cinc.com
Subject: Re: [PATCH 2/3] scsi: ufs: ufs-qcom: Add DELAY_BEFORE_LPM quirk for
Micron and Skhynix
On 8/20/24 5:37 AM, Manish Pandey wrote:
> static struct ufs_dev_quirk ufs_qcom_dev_fixups[] = {
> /* add UFS device specific quirks */
> + { .wmanufacturerid = UFS_VENDOR_MICRON,
> + .model = UFS_ANY_MODEL,
> + .quirk = UFS_DEVICE_QUIRK_DELAY_BEFORE_LPM },
> + { .wmanufacturerid = UFS_VENDOR_SKHYNIX,
> + .model = UFS_ANY_MODEL,
> + .quirk = UFS_DEVICE_QUIRK_DELAY_BEFORE_LPM },
> {}
> };
What makes these quirks specific for Qualcomm controllers? Are these
quirks perhaps required for all UFSHCI controllers?
Thanks,
Bart.
Powered by blists - more mailing lists