From: ebiederm@xmission.com (Eric W. Biederman)
To: Stanislav Nijnikov <stanislav.nijnikov@wdc.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, jaegeuk@kernel.org,
alex.lemberg@wdc.com
Subject: Re: [PATCH v4 00/10] ufs: sysfs: read-only access to device descriptors, attributes and flags
Date: Thu, 01 Feb 2018 10:48:53 -0600 [thread overview]
Message-ID: <87y3kck64q.fsf@xmission.com> (raw)
In-Reply-To: <1517501746-19075-1-git-send-email-stanislav.nijnikov@wdc.com> (Stanislav Nijnikov's message of "Thu, 1 Feb 2018 18:15:36 +0200")
Can you please clarify the naming, at least as far as saying scsi/ufs.
Universal Flash Storage is not the same thing as all as the Unix File
System which has been using the acronym ufs for much longer.
I saw this patchset and I was wondering what in the world does a
filesystem need with sysfs entries.
Eric
Stanislav Nijnikov <stanislav.nijnikov@wdc.com> writes:
> This patch introduces sysfs entries that will provide read-only access to
> device management data that could be received with UFS query requests.
> User-space applications will be able to read UFS device descriptors,
> flags and attributes. This will allow to get full UFS device configuration
> and its status. The descriptors are provided as set of files representing
> its parameters. The flags are using "true"/"false" representation of
> their value. The attributes are shown as hexadecimal value. The
> descriptors, attributes and flags are placed in separate subfolders under
> the UFS device sysfs entry (/sys/bus/platform/drivers/ufshcd/*/). The
> string descriptor subfolder contains five string descriptors defined by
> UFS specification 2.1. The LUN specific descriptor and attribute are
> placed under corresponding SCSI device sysfs entries
> (/sys/class/scsi_device/*/device/).
> In addition the patch presents an additional field in the
> scsi_host_template structure - struct attribute_group **sdev_group.
> This field allows to define groups of attributes. It will provide an
> ability to use binary attributes in addition to device attributes and
> to group them under subfolders if necessary.
>
> Changelog:
> v3 -> v4
> Additional patch the introduces default attributes group for the
> existing ufs sysfs entries (rpm_lvl and spm_lvl)
> The ufs_sysfs_read_desc_param function calls to ufshcd_read_desc_param
> insted of ufshcd_query_descriptor_retry to avoid code duplication.
> The code was updated to remove the checkpatch error "ERROR: Macros
> with complex values should be enclosed in parentheses"
> Added "_" to macros parameters to remove "#undef DEVICE_CLASS"
> The legal information was updated to satisfy the SPDX requirements
> The date in Documentation/ABI/testing/sysfs-driver-ufs was updated.
>
> v2 -> v3
> The Makefile is updated to make ufs-sysfs.c part of the ufshcd module.
> The unnecessary EXPORT_SYMBOL were removed
> Added a legal info header to the new files
> The date in Documentation/ABI/testing/sysfs-driver-ufs was updated.
>
> v1 -> v2
> Provided additional description for the changes
>
> Stanislav Nijnikov (10):
> ufs: sysfs: attribute group for existing sysfs entries.
> ufs: sysfs: device descriptor
> ufs: sysfs: interconnect descriptor
> ufs: sysfs: geometry descriptor
> ufs: sysfs: health descriptor
> ufs: sysfs: power descriptor
> ufs: sysfs: string descriptors
> ufs: sysfs: unit descriptor
> ufs: sysfs: flags
> ufs: sysfs: attributes
>
> Documentation/ABI/testing/sysfs-driver-ufs | 804 +++++++++++++++++++++++++++++
> drivers/scsi/scsi_sysfs.c | 14 +
> drivers/scsi/ufs/Makefile | 3 +-
> drivers/scsi/ufs/ufs-sysfs.c | 757 +++++++++++++++++++++++++++
> drivers/scsi/ufs/ufs-sysfs.h | 25 +
> drivers/scsi/ufs/ufs.h | 115 ++++-
> drivers/scsi/ufs/ufshcd.c | 218 ++------
> drivers/scsi/ufs/ufshcd.h | 34 ++
> include/scsi/scsi_host.h | 6 +
> 9 files changed, 1785 insertions(+), 191 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-ufs
> create mode 100644 drivers/scsi/ufs/ufs-sysfs.c
> create mode 100644 drivers/scsi/ufs/ufs-sysfs.h
prev parent reply other threads:[~2018-02-01 16:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 16:15 [PATCH v4 00/10] ufs: sysfs: read-only access to device descriptors, attributes and flags Stanislav Nijnikov
2018-02-01 16:15 ` [PATCH v4 01/10] ufs: sysfs: attribute group for existing sysfs entries Stanislav Nijnikov
2018-02-01 16:59 ` Greg KH
2018-02-04 12:29 ` Stanislav Nijnikov
2018-02-04 12:33 ` Greg KH
2018-02-04 13:09 ` Stanislav Nijnikov
2018-02-04 13:15 ` Greg KH
2018-02-01 16:15 ` [PATCH v4 02/10] ufs: sysfs: device descriptor Stanislav Nijnikov
2018-02-01 17:00 ` Greg KH
2018-02-02 0:25 ` Bart Van Assche
2018-02-02 7:17 ` gregkh
2018-02-02 16:32 ` Bart Van Assche
2018-02-04 9:03 ` Stanislav Nijnikov
2018-02-04 10:44 ` gregkh
2018-02-02 0:29 ` Bart Van Assche
2018-02-01 16:15 ` [PATCH v4 03/10] ufs: sysfs: interconnect descriptor Stanislav Nijnikov
2018-02-01 17:01 ` Greg KH
2018-02-01 16:15 ` [PATCH v4 04/10] ufs: sysfs: geometry descriptor Stanislav Nijnikov
2018-02-01 16:15 ` [PATCH v4 05/10] ufs: sysfs: health descriptor Stanislav Nijnikov
2018-02-01 16:15 ` [PATCH v4 06/10] ufs: sysfs: power descriptor Stanislav Nijnikov
2018-02-01 16:15 ` [PATCH v4 07/10] ufs: sysfs: string descriptors Stanislav Nijnikov
2018-02-01 16:15 ` [PATCH v4 08/10] ufs: sysfs: unit descriptor Stanislav Nijnikov
2018-02-02 0:38 ` Bart Van Assche
2018-02-01 16:15 ` [PATCH v4 09/10] ufs: sysfs: flags Stanislav Nijnikov
2018-02-01 16:15 ` [PATCH v4 10/10] ufs: sysfs: attributes Stanislav Nijnikov
2018-02-01 17:03 ` Greg KH
2018-02-01 16:48 ` Eric W. Biederman [this message]
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=87y3kck64q.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=alex.lemberg@wdc.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stanislav.nijnikov@wdc.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).