From: Daniil Lunev <dlunev@chromium.org>
To: Adrian Hunter <adrian.hunter@intel.com>,
Bart Van Assche <bvanassche@acm.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Daniil Lunev <dlunev@chromium.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Andy Gross <agross@kernel.org>, Avri Altman <avri.altman@wdc.com>,
Bean Huo <beanhuo@micron.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Can Guo <cang@codeaurora.org>,
Daejun Park <daejun7.park@samsung.com>,
Eric Biggers <ebiggers@google.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mike Snitzer <snitzer@redhat.com>,
Sohaib Mohamed <sohaib.amhmd@gmail.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: [PATCH v3 0/2] Expose UFSHCD capabilities in sysfs.
Date: Fri, 29 Jul 2022 12:05:06 +1000 [thread overview]
Message-ID: <20220729020508.4147751-1-dlunev@chromium.org> (raw)
The patchset introduces new sysfs nodes, which userspace can check to
determine support for certain capabilities. Specifically the patchset
exposes Clock Scaling, Write Booster, and Inline Crypto Engine
capabilities.
Changes in v3:
* Expose each capability as an individual node
* Add preleminary CL to align checking for capabilities
* Modify documentation to represent new scheme
Changes in v2:
* Add documentation entry for the new sysfs node.
Daniil Lunev (2):
ufs: add function to check CRYPTO capability
ufs: core: print UFSHCD capabilities in controller's sysfs node
Documentation/ABI/testing/sysfs-driver-ufs | 39 ++++++++++++++++++++
drivers/ufs/core/ufs-sysfs.c | 41 ++++++++++++++++++++++
drivers/ufs/core/ufshcd-crypto.c | 8 ++---
drivers/ufs/host/ufs-mediatek.c | 2 +-
drivers/ufs/host/ufs-qcom-ice.c | 4 +--
drivers/ufs/host/ufshcd-pci.c | 2 +-
include/ufs/ufshcd.h | 5 +++
7 files changed, 93 insertions(+), 8 deletions(-)
--
2.31.0
next reply other threads:[~2022-07-29 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 2:05 Daniil Lunev [this message]
2022-07-29 2:05 ` [PATCH v3 1/2] ufs: add function to check CRYPTO capability Daniil Lunev
2022-07-29 8:10 ` Greg Kroah-Hartman
2022-07-29 8:37 ` Daniil Lunev
2022-07-29 2:05 ` [PATCH v3 2/2] ufs: core: print UFSHCD capabilities in controller's sysfs node Daniil Lunev
2022-07-29 4:02 ` Eric Biggers
2022-07-29 8:12 ` Greg Kroah-Hartman
2022-07-29 8:29 ` Daniil Lunev
2022-07-29 8:32 ` Greg Kroah-Hartman
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=20220729020508.4147751-1-dlunev@chromium.org \
--to=dlunev@chromium.org \
--cc=adrian.hunter@intel.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bjorn.andersson@linaro.org \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=daejun7.park@samsung.com \
--cc=ebiggers@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=snitzer@redhat.com \
--cc=sohaib.amhmd@gmail.com \
--cc=stanley.chu@mediatek.com \
--cc=ulf.hansson@linaro.org \
/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
all inboxes | Powered by JetHome®