Received-SPF: pass (google.com: domain of linux-kernel+bounces-118551-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
IronPort-SDR: 3Bp5sqZG2tGrfTjcBo3vuK/zcntrqHwUuoVUQ8m5LN83IezjhlFuwmJMhuLDdDjiftcnKOOPTy
 D5RDeoGF2P6g==
IronPort-SDR: 1all28SjAlzNAWcIc9eIcOQqSKdriePZ4touIxj2Ab+pE7cRKsNbKX+PVTPeoqUiyHkpWdr1Z5
 oFCp0mXoidJw==
WDCIronportException: Internal
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
Message-ID: <20240326083253.1303-1-avri.altman@wdc.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

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