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 v3 0/3] Support vendor specific operations for WB
Date: Tue, 21 Jul 2020 18:57:09 +0900 [thread overview]
Message-ID: <cover.1595325064.git.hy50.seo@samsung.com> (raw)
In-Reply-To: CGME20200721095644epcas2p4aa2e620257686679e6c9e58ccabeac34@epcas2p4.samsung.com
Hi all,
Here is v3 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.
[v2 -> v3]
modified minor details about blank, typing error etc..
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
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-exynos.c | 6 +
drivers/scsi/ufs/ufs_ctmwb.c | 270 ++++++++++++++++++++++++++++++++++
drivers/scsi/ufs/ufs_ctmwb.h | 26 ++++
drivers/scsi/ufs/ufshcd.c | 22 ++-
drivers/scsi/ufs/ufshcd.h | 43 ++++++
6 files changed, 363 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-21 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200721095644epcas2p4aa2e620257686679e6c9e58ccabeac34@epcas2p4.samsung.com>
2020-07-21 9:57 ` SEO HOYOUNG [this message]
2020-07-21 9:57 ` [RFC PATCH v3 1/3] scsi: ufs: modify write booster SEO HOYOUNG
2020-07-26 6:30 ` Avri Altman
2020-07-27 9:57 ` 서호영
2020-07-27 10:10 ` Avri Altman
2020-07-27 11:28 ` 서호영
2020-07-21 9:57 ` [RFC PATCH v3 2/3] scsi: ufs: modify function call name When ufs reset and restore, need to disable " SEO HOYOUNG
2020-07-26 6:31 ` Avri Altman
2020-07-27 10:01 ` 서호영
2020-07-27 10:12 ` Avri Altman
2020-07-27 11:27 ` 서호영
2020-07-27 11:29 ` Avri Altman
2020-07-27 11:33 ` 서호영
2020-07-21 9:57 ` [RFC PATCH v3 3/3] scsi: ufs: add vendor specific " SEO HOYOUNG
2020-07-26 6:39 ` 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.1595325064.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