[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<DM6PR04MB6575D506E6E426B8B57F3C2DFC3D2@DM6PR04MB6575.namprd04.prod.outlook.com>
Date: Wed, 3 Apr 2024 11:48:26 +0000
From: Avri Altman <Avri.Altman@....com>
To: Avri Altman <Avri.Altman@....com>, "James E . J . Bottomley"
<jejb@...ux.ibm.com>, "Martin K . Petersen" <martin.petersen@...cle.com>
CC: "hch@...radead.org" <hch@...radead.org>, Bart Van Assche
<bvanassche@....org>, Bean Huo <beanhuo@...ron.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 0/1] Remove support for legacy UFS
Martin hi,
Could you please take a look at this?
I have another cleanup series pending.
Thanks,
Avri
> 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.
>
> Changes from v1:
> - remove ufshcd_get_local_unipro_ver which practically mean squashing
> patch 1 & 2 into a single patch (Christoph)
> - restore an if clause to avoid functional change in
> ufshcd_compl_one_cqe (Bart)
>
>
> Avri Altman (1):
> scsi: ufs: Remove support for old UFSHCI versions
>
> drivers/ufs/core/ufshcd.c | 174 +++---------------------------------
> drivers/ufs/host/ufs-qcom.c | 3 +-
> include/ufs/ufshcd.h | 2 -
> include/ufs/ufshci.h | 7 --
> 4 files changed, 15 insertions(+), 171 deletions(-)
>
> --
> 2.42.0
Powered by blists - more mailing lists