[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b95bdfa9-4373-8f54-677e-4a764061c61c@acm.org>
Date: Wed, 6 Apr 2022 13:20:58 -0700
From: Bart Van Assche <bvanassche@....org>
To: Bean Huo <huobean@...il.com>,
Alex Bennée <alex.bennee@...aro.org>
Cc: linux-kernel@...r.kernel.org, maxim.uvarov@...aro.org,
joakim.bech@...aro.org, ulf.hansson@...aro.org,
ilias.apalodimas@...aro.org, arnd@...aro.org,
ruchika.gupta@...aro.org, tomas.winkler@...el.com,
yang.huang@...el.com, bing.zhu@...el.com,
Matti.Moell@...nsynergy.com, hmo@...nsynergy.com,
linux-mmc@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH v2 0/4] rpmb subsystem, uapi and virtio-rpmb driver
On 4/6/22 11:12, Bean Huo wrote:
> It is from the ufs-utils.
>
> So, do you vote to add the UFS RPMB driver based on this new framework
> to resolve this conflict?
Are any applications using the RPMB code from ufs-utils? It seems to me
that the ufs-utils code doe not handle SCSI unit attentions correctly.
If a POWER ON unit attention is received as reply to a SECURITY PROTOCOL
OUT transaction, the write counter should be reread instead of retrying
the SECURITY PROTOCOL OUT command with the same write counter.
Regarding adding a UFS RPMB driver: that seems useful to me since
multiple applications make use of the UFS RPMB functionality. My
understanding is that currently storageproxyd multiplexes UFS RPMB
accesses in Android.
Thanks,
Bart.
Powered by blists - more mailing lists