>
> On 09/15/18 23:41, Avri Altman wrote:
> >> Since this patch series does not touch any include/uapi header and since no
> >> uapi UFS header files already exist, how is user space software expected to
> >> know which message format it should use for communicating over the UFS
> BSG
> >> endpoin
On 09/15/18 23:41, Avri Altman wrote:
Since this patch series does not touch any include/uapi header and since no
uapi UFS header files already exist, how is user space software expected to
know which message format it should use for communicating over the UFS BSG
endpoint? I don't think that "re
Hi Bart,
> Since this patch series does not touch any include/uapi header and since no
> uapi UFS header files already exist, how is user space software expected to
> know which message format it should use for communicating over the UFS BSG
> endpoint? I don't think that "read the source" is an a
On Fri, 2018-09-07 at 12:49 +0300, Avri Altman wrote:
> drivers/scsi/ufs/Kconfig | 19 +++
> drivers/scsi/ufs/Makefile | 3 +
> drivers/scsi/ufs/ufs.h | 30
> drivers/scsi/ufs/ufs_bsg.c | 327
> drivers/scsi/ufs/ufs_bsg.h | 67 +
>
Here is a proposal to use a bsg endpoint to manage ufs devices.
We will do that by adding a bsg device node to the ufs driver,
and use it to send UPIU transactions to the ufs device.
It will serve as a ufs device management infrastructure,
for device configuration, provisioning, testing and valid
5 matches
Mail list logo
