public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: nitirawa@codeaurora.org
To: Bean Huo <huobean@gmail.com>
Cc: cang@codeaurora.org, asutoshd@codeaurora.org,
	stummala@codeaurora.org, vbadigan@codeaurora.org,
	alim.akhtar@samsung.com, avri.altman@wdc.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com, stanley.chu@mediatek.com,
	beanhuo@micron.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, nitirawa@codeaurora.org
Subject: Re: [PATCH V2] scsi: ufs: Add UFS3.0 in ufs HCI version check
Date: Mon, 01 Feb 2021 14:32:26 +0530	[thread overview]
Message-ID: <d1b23943b6b3ae6c1f6af041cc592932@codeaurora.org> (raw)
In-Reply-To: <63f00f514f1e912b8fb1d0c183e9167b60b3a5dc.camel@gmail.com>

On 2021-01-30 00:55, Bean Huo wrote:
> On Tue, 2021-01-19 at 17:37 +0530, Nitin Rawat wrote:
>> As per JESD223D UFS HCI v3.0 spec, HCI version 3.0
>> is also supported. Hence Adding UFS3.0 in UFS HCI
>> version check to avoid logging of the error message.
>> 
>> Signed-off-by: Nitin Rawat <nitirawa@codeaurora.org>
>> ---
>>  drivers/scsi/ufs/ufshcd.c | 5 +++--
>>  drivers/scsi/ufs/ufshci.h | 1 +
>>  2 files changed, 4 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
>> index 82ad317..54ca765 100644
>> --- a/drivers/scsi/ufs/ufshcd.c
>> +++ b/drivers/scsi/ufs/ufshcd.c
>> @@ -9255,8 +9255,9 @@ int ufshcd_init(struct ufs_hba *hba, void
>> __iomem *mmio_base, unsigned int irq)
>>         if ((hba->ufs_version != UFSHCI_VERSION_10) &&
>>             (hba->ufs_version != UFSHCI_VERSION_11) &&
>>             (hba->ufs_version != UFSHCI_VERSION_20) &&
>> -           (hba->ufs_version != UFSHCI_VERSION_21))
>> -               dev_err(hba->dev, "invalid UFS version 0x%x\n",
>> +           (hba->ufs_version != UFSHCI_VERSION_21) &&
>> +           (hba->ufs_version != UFSHCI_VERSION_30))
>> +               dev_err(hba->dev, "invalid UFS HCI version 0x%x\n",
>>                         hba->ufs_version);
> 
> Hi Nitin
> Except HCI 1.0 / 1.1 / 2.0 / 2.1 / 3.0, do you have the other UFS HCI
> version? if no, current driver supports all of them,  instead of
> scaling these check, and avoid logging of the error message, I suggest
> you can directly delete these redundant checkup.
> 
> If there is a weird HCI version that not supported by the current
> driver, you can only add an unsupported checkup list. thus, you don't
> need to scale this useless checkup.
> 
> Bean

Hi Bean,
That's a good suggestion. If nobody has any concern, i will
post new patchset by removing these redundant check.

Regards,
Nitin

      reply	other threads:[~2021-02-01  9:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 12:07 [PATCH V2] scsi: ufs: Add UFS3.0 in ufs HCI version check Nitin Rawat
2021-01-19 12:08 ` Can Guo
2021-01-29 18:27 ` Martin K. Petersen
2021-01-29 19:25 ` Bean Huo
2021-02-01  9:02   ` nitirawa [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=d1b23943b6b3ae6c1f6af041cc592932@codeaurora.org \
    --to=nitirawa@codeaurora.org \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=cang@codeaurora.org \
    --cc=huobean@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanley.chu@mediatek.com \
    --cc=stummala@codeaurora.org \
    --cc=vbadigan@codeaurora.org \
    /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