From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "beanhuo@micron.com" <beanhuo@micron.com>,
"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>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>
Subject: Re: UFS utilities
Date: Mon, 27 Nov 2017 19:35:25 +0000 [thread overview]
Message-ID: <1511811323.2993.13.camel@wdc.com> (raw)
In-Reply-To: <c7f3d6f543ae41c1bb625b1612e47057@SIWEX5A.sing.micron.com>
On Mon, 2017-11-27 at 11:25 +0000, Bean Huo (beanhuo) wrote:
> 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.
Hello Bean,
Please be more specific. What is inconvenient about sg3_utils on embedded
ARM systems?
> And also it doesn't support several UFS special command.
Are you referring to SCSI commands or rather to UFS commands that fall
outside the SCSI spec? Anyway, an approach that is used by many SCSI drivers
to export information to user space that falls outside the SCSI spec is to
create additional sysfs attributes. See also the sdev_attrs and shost_attrs
members of struct scsi_host_template.
Bart.
next prev parent reply other threads:[~2017-11-27 19:35 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
2017-11-27 19:35 ` Bart Van Assche [this message]
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=1511811323.2993.13.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=beanhuo@micron.com \
--cc=gregkh@linuxfoundation.org \
--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).