Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Avri Altman <avri.altman@wdc.com>
To: "James E . J . Bottomley" <jejb@linux.ibm.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	Bean Huo <beanhuo@micron.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Avri Altman <avri.altman@wdc.com>
Subject: [PATCH 0/2] Remove support for legacy UFS
Date: Tue, 26 Mar 2024 10:32:48 +0200	[thread overview]
Message-ID: <20240326083253.1303-1-avri.altman@wdc.com> (raw)

UFS1.0 and UFS1.1, published in the early 2010s, were more of a proof of
concept rather than a mature functional spec. Toshiba was the only
device manufacturer with the most accomplished phy team to come up with
a small UFS1.0 device. Alas, there were no commercial platforms it can
be paired with. Even UFS2.0 that was published in 2013, didn't really
make it to the market: too moot to take effect. It's not until UFS2.1
that was published in 2016, were a myriad of devices and platforms
flooded the market. Designated to mobile devices, dictates a rapid short
lives for those platforms. Hence, we can safely remove those pre-UFS2.1
pieces of code.

Avri Altman (2):
  scsi: ufs: Remove support for old UFSHCI versions
  scsi: ufs: Remove legacy tuning calls

 drivers/ufs/core/ufshcd.c   | 169 ++++--------------------------------
 drivers/ufs/host/ufs-qcom.c |   3 +-
 include/ufs/ufshci.h        |   7 --
 3 files changed, 16 insertions(+), 163 deletions(-)

-- 
2.42.0


             reply	other threads:[~2024-03-26  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  8:32 Avri Altman [this message]
2024-03-26  8:32 ` [PATCH 1/2] scsi: ufs: Remove support for old UFSHCI versions Avri Altman
2024-03-26 17:20   ` Bart Van Assche
2024-03-26 17:22     ` Christoph Hellwig
2024-03-26 18:09       ` Avri Altman
2024-03-26 18:09     ` Avri Altman
2024-03-26  8:32 ` [PATCH 2/2] scsi: ufs: Remove legacy tuning calls Avri Altman

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=20240326083253.1303-1-avri.altman@wdc.com \
    --to=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.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