From: Greg KH <gregkh@linuxfoundation.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>
Subject: Re: UFS utilities
Date: Mon, 27 Nov 2017 12:40:33 +0100 [thread overview]
Message-ID: <20171127114033.GA31604@kroah.com> (raw)
In-Reply-To: <c7f3d6f543ae41c1bb625b1612e47057@SIWEX5A.sing.micron.com>
On Mon, Nov 27, 2017 at 11:25:47AM +0000, Bean Huo (beanhuo) wrote:
> Hi, all
> Is there someone knows if exists one utilis dedicated to UFS device, rather than SCSI utils?
> I have tried sg3-utils, but it is not convenient for the embedded ARM-based system.
> And also it doesn't support several UFS special command.
What specific UFS commands do you need to make to the device that the
current driver does not support?
And yes, this is a trick question as there are about 4 different major
forks that I know of of the UFS driver in different vendor trees, all of
which support different types of UFS commands :(
> If we don't have this kind of tool for UFS, is it necessary for us to develop a ufs-utils?
I doubt it, what neds to happen is getting all of the functionality that
lives in these different forks all merged upstream into the in-kernel
driver. Then I bet all of the needed functionality you are looking for
will be there.
good luck!
greg k-h
next prev parent reply other threads:[~2017-11-27 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 11:25 UFS utilities Bean Huo (beanhuo)
2017-11-27 11:40 ` Greg KH [this message]
2017-11-27 19:35 ` Bart Van Assche
2017-12-04 15:20 ` [EXT] " Bean Huo (beanhuo)
2017-12-04 18:38 ` gregkh
2017-12-05 22:22 ` Bart Van Assche
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 15:39 Bean Huo (beanhuo)
2017-11-29 16:19 ` Greg KH
2017-11-29 16:20 ` James Bottomley
2017-12-04 2:47 ` Kyuho Choi
2017-12-05 15:44 Bean Huo (beanhuo)
2017-12-05 15:49 ` gregkh
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=20171127114033.GA31604@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=beanhuo@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vinholikatti@gmail.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;
as well as URLs for NNTP newsgroup(s).