From: SEO HOYOUNG <hy50.seo@samsung.com>
To: linux-scsi@vger.kernel.org, alim.akhtar@samsung.com,
avri.altman@wdc.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, beanhuo@micron.com,
asutoshd@codeaurora.org, cang@codeaurora.org, bvanassche@acm.org,
grant.jung@samsung.com
Cc: SEO HOYOUNG <hy50.seo@samsung.com>
Subject: [RFC PATCH v2 0/3] Support vendor specific operations for WB
Date: Mon, 20 Jul 2020 19:40:10 +0900 [thread overview]
Message-ID: <cover.1595240433.git.hy50.seo@samsung.com> (raw)
In-Reply-To: <n>
Hi all,
Here is v2 of the patchset.
This patchs for supporting WB of vendor specific.
- when UFS reset and restore, need to cleare WB buffer.
- need to check WB buffer and flush operate before enter suspend
- do not enable WB with UFS probe.
[v1 -> v2]
- The ufshcd_reset_vendor() fuction for WB reset.
So I modified function name.
- uploade vendor wb code.
SEO HOYOUNG (3):
scsi: ufs: modify write booster
scsi: ufs: modify function call name When ufs reset and restore, need
to disable write booster
scsi: ufs: add vendor specific write booster To support the fuction of
writebooster by vendor. The WB behavior that the vendor wants is
slightly different. But we have to support it
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-exynos.c | 6 +
drivers/scsi/ufs/ufs_ctmwb.c | 279 ++++++++++++++++++++++++++++++++++
drivers/scsi/ufs/ufs_ctmwb.h | 27 ++++
drivers/scsi/ufs/ufshcd.c | 23 ++-
drivers/scsi/ufs/ufshcd.h | 43 ++++++
6 files changed, 374 insertions(+), 5 deletions(-)
create mode 100644 drivers/scsi/ufs/ufs_ctmwb.c
create mode 100644 drivers/scsi/ufs/ufs_ctmwb.h
--
2.26.0
next parent reply other threads:[~2020-07-20 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200720103946epcas2p46e38e8d585d2882d167e5aa548e53217@epcas2p4.samsung.com>
2020-07-20 10:40 ` SEO HOYOUNG [this message]
[not found] ` <CGME20200720103949epcas2p4a49b245d9cebf0478d42fb6c607fc236@epcas2p4.samsung.com>
2020-07-20 10:40 ` [RFC PATCH v2 1/3] scsi: ufs: modify write booster SEO HOYOUNG
2020-07-20 16:46 ` Asutosh Das (asd)
2020-07-21 9:26 ` 서호영
[not found] ` <CGME20200720103950epcas2p16278643a6f62b446b653c834de448543@epcas2p1.samsung.com>
2020-07-20 10:40 ` [RFC PATCH v2 2/3] scsi: ufs: modify function call name When ufs reset and restore, need to disable " SEO HOYOUNG
2020-07-21 6:36 ` Avri Altman
[not found] ` <CGME20200720103951epcas2p246072985a70a459f0acb31d339298a47@epcas2p2.samsung.com>
2020-07-20 10:40 ` [RFC PATCH v2 3/3] scsi: ufs: add vendor specific write booster To support the fuction of writebooster by vendor. The WB behavior that the vendor wants is slightly different. But we have to support it SEO HOYOUNG
2020-07-20 16:55 ` Asutosh Das (asd)
2020-07-21 9:47 ` 서호영
2020-07-21 16:18 ` Asutosh Das (asd)
2020-07-24 9:42 ` 서호영
2020-07-24 15:57 ` Asutosh Das (asd)
2020-07-21 6:37 ` Avri Altman
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=cover.1595240433.git.hy50.seo@samsung.com \
--to=hy50.seo@samsung.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=grant.jung@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).