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: Wed, 29 Nov 2017 16:19:33 +0000 [thread overview]
Message-ID: <20171129161933.GA19441@kroah.com> (raw)
In-Reply-To: <e8aa9f0b9e854fe6bff7cb17dc08ce8c@SIWEX5A.sing.micron.com>
On Wed, Nov 29, 2017 at 03:39:19PM +0000, Bean Huo (beanhuo) wrote:
> Hi, Greg
>
> >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?
>
>
> There are some UFS/vendor native commands. They are not SCSI based.
Exactly what ones are missing? Again, there are numerous non-scsi UFS
commands supported in sysfs files in the in-kernel, and lots in the
different forks I mentioned. I bet if you pull all of those together,
you should cover all of the ones you need, right?
> >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.
> >
> Sometimes customers tend to use user space tool to do some configuration.
> And especially, for example the UFS FFU.
Again, that's fine, have you looked at what is currently present and
what is missing?
thanks,
greg k-h
next prev parent reply other threads:[~2017-11-29 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 15:39 UFS utilities Bean Huo (beanhuo)
2017-11-29 16:19 ` Greg KH [this message]
2017-11-29 16:20 ` James Bottomley
2017-12-04 2:47 ` Kyuho Choi
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 15:44 Bean Huo (beanhuo)
2017-12-05 15:49 ` gregkh
2017-11-27 11:25 Bean Huo (beanhuo)
2017-11-27 11:40 ` Greg KH
2017-11-27 19:35 ` Bart Van Assche
2017-12-04 15:20 ` [EXT] " Bean Huo (beanhuo)
2017-12-05 22:22 ` Bart Van Assche
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=20171129161933.GA19441@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