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: "hch@infradead.org" <hch@infradead.org>,
Bean Huo <beanhuo@micron.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] scsi: ufs: Remove support for old UFSHCI versions
Date: Wed, 3 Apr 2024 14:17:49 -0700 [thread overview]
Message-ID: <4b90d403-b18c-42c9-99b4-013eb7fcf8a8@acm.org> (raw)
In-Reply-To: <DM6PR04MB6575BEBF605C9095E62F49E3FC3D2@DM6PR04MB6575.namprd04.prod.outlook.com>
On 4/3/24 12:24, Avri Altman wrote:
>> On 3/27/24 00:17, 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. Thus, remove support of host controllers prior
>>> to UFS2.1.
>>
>> According to this website, Pixel 1 devices have a UFSHCI 2.0 controller:
>> https://www.gsmarena.com/google_pixel-8346.php. There may be other
>> smartphones that have a UFSHCI 2.0 controller. Hence, I'm not sure we
>> can drop support for UFSHCI 2.0 controllers from the kernel.
> Actually the Pixel 1 is an excellent example why we can and should -
> It was announced in 2016, running Android 7 with a v4.4 kernel.
> Even if you would be able to find a working specimen of that device -
> It is not realistic it would ever run a 6.10 kernel.
v4.4 is the kernel version of the kernel included in the original
software. Multiple users of older smartphones switch to alternative
distributions once their device is no longer supported by the
manufacturer. These alternatives often include a more recent kernel.
See e.g. https://en.wikipedia.org/wiki/List_of_custom_Android_distributions.
Thanks,
Bart.
next prev parent reply other threads:[~2024-04-03 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 7:17 [PATCH v2 0/1] Remove support for legacy UFS Avri Altman
2024-03-27 7:17 ` [PATCH v2 1/1] scsi: ufs: Remove support for old UFSHCI versions Avri Altman
2024-04-03 16:26 ` Bart Van Assche
2024-04-03 19:24 ` Avri Altman
2024-04-03 21:17 ` Bart Van Assche [this message]
2024-04-04 7:22 ` Avri Altman
2024-04-04 8:45 ` Bean Huo
2024-04-05 8:11 ` Bean Huo
2024-04-03 11:48 ` [PATCH v2 0/1] Remove support for legacy UFS 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=4b90d403-b18c-42c9-99b4-013eb7fcf8a8@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®