Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Caleb Connolly <caleb@connolly.tech>
To: Christoph Hellwig <hch@lst.de>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	ejb@linux.ibm.com, stanley.chu@mediatek.com, cang@codeaurora.org,
	beanhuo@micron.com, jaegeuk@kernel.org, asutoshd@codeaurora.org,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] scsi: ufshcd: switch to a version macro
Date: Mon, 08 Mar 2021 10:42:43 +0000	[thread overview]
Message-ID: <0c6cff2b-8d56-2b34-837d-b3d8f1fa5ad9@connolly.tech> (raw)
In-Reply-To: <20210308080013.GE983@lst.de>

Hi Christoph,

On 08/03/2021 8:00 am, Christoph Hellwig wrote:
> This looks like a really nice improvement!
>
> A bunch of comments below:
>
>> @@ -696,10 +685,21 @@ static inline u32 ufshcd_get_intr_mask(struct ufs_hba *hba)
>>    */
>>   static inline u32 ufshcd_get_ufs_version(struct ufs_hba *hba)
>>   {
>> +	u32 ufshci_ver;
> missing eempty line after the declaration.
>
>>   	if (hba->quirks & UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION)
>> +		ufshci_ver = ufshcd_vops_get_ufs_hci_version(hba);
>> +	else
>> +		ufshci_ver = ufshcd_readl(hba, REG_UFS_VERSION);
>>
>> +	/*
>> +	 * UFSHCI v1.x uses a different version scheme, in order
>> +	 * to allow the use of comparisons with the UFSHCI_VER
>> +	 * macro, we convert it to the same scheme as ufs 2.0+.
>> +	 */
>> +	if (ufshci_ver & 0x00010000)
>> +		ufshci_ver = UFSHCI_VER(1, ufshci_ver & 0x00000100);
>> +
>> +	return ufshci_ver;
> I'd use early returns here to clean this up a bit:
>
>   	if (hba->quirks & UFSHCD_QUIRK_BROKEN_UFS_HCI_VERSION)
> 		ufshci_ver = ufshcd_vops_get_ufs_hci_version(hba);
>
> 	...
> 	ufshci_ver = ufshcd_readl(hba, REG_UFS_VERSION);
> 	if (ufshci_ver & 0x00010000)
> 		return UFSHCI_VER(1, ufshci_ver & 0x00000100);
> 	return ufshci_ver;
>
>> +#define UFSHCI_VER(major, minor) \
>> +	((major << 8) + (minor << 4))
> This needs braces around major and minor.  Or better just convert it
> to an inline function (and use a lower case name).

Other (similar) implementations, like NVME_VS() use a macro here, is an 
inline function just personal preference?

I'm perfectly happy either way, so I'll switch to your suggestion.

Thanks for the review.

Regards,

Caleb




  reply	other threads:[~2021-03-08 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08  0:58 scsi: ufshcd: use a macro for UFS versions Caleb Connolly
2021-03-08  0:58 ` [PATCH 1/3] scsi: ufshcd: switch to a version macro Caleb Connolly
2021-03-08  8:00   ` Christoph Hellwig
2021-03-08 10:42     ` Caleb Connolly [this message]
2021-03-09  9:32       ` Christoph Hellwig
2021-03-08  0:58 ` [PATCH 2/3] scsi: ufs: qcom: use UFSHCI_VER macro Caleb Connolly
2021-03-08  0:59 ` [PATCH 3/3] scsi: ufshcd: remove version check Caleb Connolly

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=0c6cff2b-8d56-2b34-837d-b3d8f1fa5ad9@connolly.tech \
    --to=caleb@connolly.tech \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=cang@codeaurora.org \
    --cc=ejb@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --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 \
    /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