From: Jinyoung CHOI <j-young.choi@samsung.com>
To: ALIM AKHTAR <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>
Subject: [PATCH v6 0/6] scsi: ufs: wb: Add sysfs attribute and cleanup
Date: Tue, 02 Aug 2022 17:01:46 +0900 [thread overview]
Message-ID: <20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p2> (raw)
In-Reply-To: <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p2>
This patch series is to clean up UFS's Write Booster code and
adds sysfs attribute which can control the specific feature of it.
V2:
- modify commit message
- move & modify err messages
- remove unnesscessary debug messages
V3:
- split patch (functional, non-functional)
V4:
- split patch (The number of patches from 2 to 7)
- modify dev messages
- modify commit message
V5:
- drop (scsi: ufs: wb: Move ufshcd_is_wb_allowed() to callee)
- fix condition check
- add document for sysfs attribute
- move ufshcd_is_wb_buf_flush_allowed() to ufs-priv.h
V6:
- Change the function name from ufshcd_wb_config() to
ufshcd_configure_wb()
- modify document description for wb_buf_flush_en attribute
- fix some dev_err messages
Jinyoung Choi (6):
scsi: ufs: wb: Change wb_enabled condition test
scsi: ufs: wb: Change functions name and modify parameter name
scsi: ufs: wb: Add explicit flush sysfs attribute
scsi: ufs: wb: Add ufshcd_is_wb_buf_flush_allowed()
scsi: ufs: wb: Modify messages
scsi: ufs: wb: Move the comment to the right position
Documentation/ABI/testing/sysfs-driver-ufs | 9 +++
drivers/ufs/core/ufs-sysfs.c | 47 ++++++++++++++-
drivers/ufs/core/ufshcd-priv.h | 6 ++
drivers/ufs/core/ufshcd.c | 70 ++++++++++++----------
include/ufs/ufshcd.h | 1 +
5 files changed, 99 insertions(+), 34 deletions(-)
--
2.25.1
next parent reply other threads:[~2022-08-02 8:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p2>
2022-08-02 8:01 ` Jinyoung CHOI [this message]
[not found] ` <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p3>
2022-08-02 8:03 ` [PATCH v6 1/6] scsi: ufs: wb: Change wb_enabled condition test Jinyoung CHOI
2022-08-02 8:07 ` [PATCH v6 3/6] scsi: ufs: wb: Add explicit flush sysfs attribute Jinyoung CHOI
2022-08-03 17:38 ` Bart Van Assche
[not found] ` <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p8>
2022-08-02 8:05 ` [PATCH v6 2/6] scsi: ufs: wb: Change functions name and modify parameter name Jinyoung CHOI
2022-08-03 17:35 ` Bart Van Assche
2022-08-03 4:11 ` RE:(2) [PATCH v6 5/6] scsi: ufs: wb: Modify messages Jinyoung CHOI
2022-08-03 5:34 ` (2) " Stanley Chu
[not found] ` <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p4>
2022-08-03 6:07 ` Jinyoung CHOI
[not found] ` <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p6>
2022-08-02 8:10 ` [PATCH v6 6/6] scsi: ufs: wb: Move the comment to the right position Jinyoung CHOI
2022-08-02 14:13 ` Stanley Chu
[not found] ` <CGME20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p1>
2022-08-02 8:09 ` [PATCH v6 5/6] scsi: ufs: wb: Modify messages Jinyoung CHOI
2022-08-02 14:12 ` Stanley Chu
2022-08-04 5:49 ` RE:(2) [PATCH v6 3/6] scsi: ufs: wb: Add explicit flush sysfs attribute Jinyoung CHOI
2022-08-02 8:08 ` [PATCH v6 4/6] scsi: ufs: wb: Add ufshcd_is_wb_buf_flush_allowed() Jinyoung CHOI
2022-08-02 14:12 ` Stanley Chu
2022-08-03 17:39 ` 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=20220802080146epcms2p24b86bfce3d3c09c79b91d861cb3b2cce@epcms2p2 \
--to=j-young.choi@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.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 \
/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®