mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: MANISH PANDEY <quic_mapa@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	<linux-arm-msm@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <quic_nitirawa@quicinc.com>,
	<quic_bhaskarv@quicinc.com>, <quic_narepall@quicinc.com>,
	<quic_rampraka@quicinc.com>, <quic_cang@quicinc.com>,
	<quic_nguyenb@quicinc.com>
Subject: Re: [PATCH V2] scsi: ufs: ufs-qcom: add fixup_dev_quirks vops
Date: Tue, 3 Sep 2024 18:48:34 +0530	[thread overview]
Message-ID: <de730f33-b311-4a13-a56a-fa8643e02d2f@quicinc.com> (raw)
In-Reply-To: <20240828140805.zhvand7q3wbdmfrt@thinkpad>



On 8/28/2024 7:38 PM, Manivannan Sadhasivam wrote:
> On Wed, Aug 28, 2024 at 07:10:32PM +0530, Manish Pandey wrote:
>> Add fixup_dev_quirk vops in QCOM UFS platforms and provide an initial
>> vendor-specific device quirk table to add UFS device specific quirks
>> which are enabled only for specified UFS devices.
>>
> 
> Why the quirks are enabled only for Qcom platforms? If these are required by the
> UFS device, then they should be added to ufs_fixups[] in ufshcd.c.
> 
As of now, we are not sure if the same would be applicable to other 
vendors as well, so avoiding to add in ufs_fixups[].

>> Micron and Skhynix UFS device needs DELAY_BEFORE_LPM quirk to have a
>> delay before VCC is powered off.
>>
> 
> Micron fix is already part of ufs_fixups[].
Thanks for guidance, will take care in next patch set.
> 
>> 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.
>>
> 
> This sounds like the issue is specific to Qcom platforms only.
> 
Not sure, if for other vendors it is required. Hence adding for Qcom only.
>> Signed-off-by: Manish Pandey <quic_mapa@quicinc.com>
>> ---
> 
> Where is the changelog?
> 
> - Mani
> 
>>   drivers/ufs/host/ufs-qcom.c | 20 ++++++++++++++++++++
>>   1 file changed, 20 insertions(+)
>>
>> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
>> index 810e637047d0..9dbfbe643e5e 100644
>> --- a/drivers/ufs/host/ufs-qcom.c
>> +++ b/drivers/ufs/host/ufs-qcom.c
>> @@ -834,6 +834,25 @@ static int ufs_qcom_apply_dev_quirks(struct ufs_hba *hba)
>>   	return err;
>>   }
>>   
>> +/* UFS device-specific quirks */
>> +static struct ufs_dev_quirk ufs_qcom_dev_fixups[] = {
>> +	{ .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 },
>> +	{ .wmanufacturerid = UFS_VENDOR_TOSHIBA,
>> +	  .model = UFS_ANY_MODEL,
>> +	  .quirk = UFS_DEVICE_QUIRK_DELAY_AFTER_LPM },
>> +	{}
>> +};
>> +
>> +static void ufs_qcom_fixup_dev_quirks(struct ufs_hba *hba)
>> +{
>> +	ufshcd_fixup_dev_quirks(hba, ufs_qcom_dev_fixups);
>> +}
>> +
>>   static u32 ufs_qcom_get_ufs_hci_version(struct ufs_hba *hba)
>>   {
>>   	return ufshci_version(2, 0);
>> @@ -1798,6 +1817,7 @@ static const struct ufs_hba_variant_ops ufs_hba_qcom_vops = {
>>   	.link_startup_notify    = ufs_qcom_link_startup_notify,
>>   	.pwr_change_notify	= ufs_qcom_pwr_change_notify,
>>   	.apply_dev_quirks	= ufs_qcom_apply_dev_quirks,
>> +	.fixup_dev_quirks       = ufs_qcom_fixup_dev_quirks,
>>   	.suspend		= ufs_qcom_suspend,
>>   	.resume			= ufs_qcom_resume,
>>   	.dbg_register_dump	= ufs_qcom_dump_dbg_regs,
>> -- 
>> 2.17.1
>>
> 

      reply	other threads:[~2024-09-03 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 13:40 Manish Pandey
2024-08-28 14:08 ` Manivannan Sadhasivam
2024-09-03 13:18   ` MANISH PANDEY [this message]

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=de730f33-b311-4a13-a56a-fa8643e02d2f@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®