From: Bean Huo <huobean@gmail.com>
To: alim.akhtar@samsung.com, avri.altman@wdc.com,
asutoshd@codeaurora.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, stanley.chu@mediatek.com,
beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
cang@codeaurora.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/6] Several changes for UFS WriteBooster
Date: Tue, 19 Jan 2021 17:38:41 +0100 [thread overview]
Message-ID: <20210119163847.20165-1-huobean@gmail.com> (raw)
From: Bean Huo <beanhuo@micron.com>
Changelog:
v6--v7:
1. Change wb_on sysfs documentation and add information that WriteBooster
is already enabled after power-on/reset(Incorporate Adrian Hunter's suggestion)
v5--v6:
1. Remove original patch 7/7:
"scsi: ufs: Keep device active mode only fWriteBoosterBufferFlushDuringHibernate == 1"
2. Rebased patch onto 5.12/scsi-staging
3. Add protection of PM ops and err_handler for the wb_on entry access
V4--V5:
1. Add patch "docs: ABI: Add wb_on documentation for UFS sysfs"
2. Unify WB related flags with wb_* prefix (Stanley Chu)
3. Delete d_ext_ufs_feature_sup (Stanley Chu)
4. Incorporate Stanley's suggestion to patch 6/7
5. Replace scnprintf() with sysfs_emit() in 1/7 (Greg KH)
v3--v4:
1. Rebase patch on 5.11/scsi-staging
2. Add WB cleanup patches 3/6, 4/6 adn 5/6
v2--v3:
1. Change multi-line comments style in patch 1/3 (Can Guo)
v1--v2:
1. Take is_hibern8_wb_flush checkup out from function
ufshcd_wb_need_flush() in patch 2/3
2. Add UFSHCD_CAP_CLK_SCALING checkup in patch 1/3. that means
only for the platform, which doesn't support UFSHCD_CAP_CLK_SCALING,
can control WB through "wb_on".
Bean Huo (6):
scsi: ufs: Add "wb_on" sysfs node to control WB on/off
docs: ABI: Add wb_on documentation for new entry wb_on
scsi: ufs: Changes comment in the function ufshcd_wb_probe()
scsi: ufs: Remove two WB related fields from struct ufs_dev_info
scsi: ufs: Group UFS WB related flags to struct ufs_dev_info
scsi: ufs: Cleanup WB buffer flush toggle implementation
Documentation/ABI/testing/sysfs-driver-ufs | 11 +++
drivers/scsi/ufs/ufs-sysfs.c | 46 +++++++++
drivers/scsi/ufs/ufs.h | 29 +++---
drivers/scsi/ufs/ufshcd.c | 103 ++++++++-------------
drivers/scsi/ufs/ufshcd.h | 6 +-
5 files changed, 113 insertions(+), 82 deletions(-)
--
2.17.1
next reply other threads:[~2021-01-19 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 16:38 Bean Huo [this message]
2021-01-19 16:38 ` [PATCH v7 1/6] scsi: ufs: Add "wb_on" sysfs node to control WB on/off Bean Huo
2021-01-19 16:38 ` [PATCH v7 2/6] docs: ABI: Add wb_on documentation for new entry wb_on Bean Huo
2021-01-19 16:38 ` [PATCH v7 3/6] scsi: ufs: Changes comment in the function ufshcd_wb_probe() Bean Huo
2021-01-19 16:38 ` [PATCH v7 4/6] scsi: ufs: Remove two WB related fields from struct ufs_dev_info Bean Huo
2021-01-19 16:38 ` [PATCH v7 5/6] scsi: ufs: Group UFS WB related flags to " Bean Huo
2021-01-19 16:38 ` [PATCH v7 6/6] scsi: ufs: Cleanup WB buffer flush toggle implementation Bean Huo
2021-01-21 3:15 ` [PATCH v7 0/6] Several changes for UFS WriteBooster Martin K. Petersen
2021-01-21 16:15 ` Bean Huo
2021-01-23 4:22 ` Martin K. Petersen
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=20210119163847.20165-1-huobean@gmail.com \
--to=huobean@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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).