From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <avri.altman@wdc.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Bean Huo <beanhuo@micron.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] scsi: ufs: Remove support for old UFSHCI versions
Date: Tue, 9 Apr 2024 16:27:51 -0700 [thread overview]
Message-ID: <37c51970-1408-4a71-926a-780c663e5572@acm.org> (raw)
In-Reply-To: <20240407060412.856-2-avri.altman@wdc.com>
On 4/6/24 11:04 PM, Avri Altman wrote:
> UFS spec version 2.1 was published more than 10 years ago. It is
> vanishingly unlikely that even there are out there platforms that uses
> earlier host controllers, let alone that those ancient platforms will
> ever run a V6.10 kernel. To be extra cautious, leave out support for
> UFSHCI2.0 as well, and just remove support of host controllers prior
> to UFS2.0.
>
> This patch removes some legacy tuning calls that no longer apply.
>
> Signed-off-by: Avri Altman <avri.altman@wdc.com>
> Acked-by: Bean Huo <beanhuo@micron.com>
> ---
> drivers/ufs/core/ufshcd.c | 158 +++---------------------------------
> drivers/ufs/host/ufs-qcom.c | 3 +-
> include/ufs/ufshcd.h | 2 -
> include/ufs/ufshci.h | 13 +--
> 4 files changed, 15 insertions(+), 161 deletions(-)
>
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 62c8575f2c67..c72ef87ea867 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -748,8 +748,6 @@ static int ufshcd_wait_for_register(struct ufs_hba *hba, u32 reg, u32 mask,
> */
> static inline u32 ufshcd_get_intr_mask(struct ufs_hba *hba)
> {
> - if (hba->ufs_version == ufshci_version(1, 0))
> - return INTERRUPT_MASK_ALL_VER_10;
> if (hba->ufs_version <= ufshci_version(2, 0))
> return INTERRUPT_MASK_ALL_VER_11;
Is the patch description in sync with the patch itself? The patch
description says that support for UFSHCI 2.0 is removed while the
above if-condition only evaluates to true for UFSHCI 2.0 and older
controllers.
Thanks,
Bart.
next prev parent reply other threads:[~2024-04-09 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 6:04 [PATCH v3 0/1] Remove support for legacy UFS Avri Altman
2024-04-07 6:04 ` [PATCH v3 1/1] scsi: ufs: Remove support for old UFSHCI versions Avri Altman
2024-04-09 23:27 ` Bart Van Assche [this message]
2024-04-10 7:06 ` Avri Altman
2024-04-10 17:29 ` Bart Van Assche
2024-04-10 17:31 ` Avri Altman
2024-04-10 17:33 ` Bart Van Assche
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=37c51970-1408-4a71-926a-780c663e5572@acm.org \
--to=bvanassche@acm.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=hch@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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®