[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP2JTQJaYKoYANe6C68HnkVzT6eYUq9wJQxuy71LqQ72dacv_w@mail.gmail.com>
Date: Mon, 4 Jun 2018 20:11:19 +0900
From: Kyuho Choi <chlrbgh0@...il.com>
To: Evan Green <evgreen@...omium.org>
Cc: Vinayak Holikatti <vinholikatti@...il.com>,
"James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Stanislav Nijnikov <stanislav.nijnikov@....com>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
Gwendal Grignou <gwendal@...omium.org>
Subject: Re: [PATCH 0/7] Enable UFS provisioning via Linux
Hi Evan,
I've some question about end user's provisioning.
On 5/30/18, Evan Green <evgreen@...omium.org> wrote:
> This series enables provisioning UFS devices using the existing sysfs
> interface. This functionality is primarily useful along the assembly
> line, but might also be useful for end users that receive devices that
> aren't locked down.
As we knew, ufs are mainly adopted to boot device like mobile phone.
Usally after provisioning operation, every data in ufs (eg. Android :
system, userdata, boot info and etc) would be removed. How end user
download and flash all data to ufs?. dd or another download tools?.
>
> Evan Green (7):
> scsi: ufs: Add Configuration Descriptor to sysfs
> scsi: ufs: Add config descriptor documentation
> scsi: ufs: Make sysfs attributes writable
> scsi: ufs: sysfs: Document attribute writability
> scsi: ufs: Refactor descriptor read for write
> scsi: ufs: Enable writing config descriptor
> scsi: ufs: Update config descriptor documentation
>
> Documentation/ABI/testing/sysfs-driver-ufs | 174 ++++++++++++++++++++---
> drivers/scsi/ufs/ufs-sysfs.c | 217
> ++++++++++++++++++++++++++---
> drivers/scsi/ufs/ufs.h | 29 ++++
> drivers/scsi/ufs/ufshcd.c | 89 ++++++++----
> drivers/scsi/ufs/ufshcd.h | 16 ++-
> 5 files changed, 458 insertions(+), 67 deletions(-)
>
> --
> 2.13.5
>
>
Powered by blists - more mailing lists