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 2/3] scsi: ufs: modify function call name When ufs reset and restore, need to disable write booster
Date: Mon, 20 Jul 2020 19:40:12 +0900 [thread overview]
Message-ID: <98b5339dc9c5dc57ed72e83bc7c39c4211d20b6a.1595240433.git.hy50.seo@samsung.com> (raw)
In-Reply-To: <cover.1595240433.git.hy50.seo@samsung.com>
Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com>
---
drivers/scsi/ufs/ufshcd.c | 2 +-
drivers/scsi/ufs/ufshcd.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
index efa16bf4fd76..419d3dd7e183 100644
--- a/drivers/scsi/ufs/ufshcd.c
+++ b/drivers/scsi/ufs/ufshcd.c
@@ -6615,7 +6615,7 @@ static int ufshcd_reset_and_restore(struct ufs_hba *hba)
int err = 0;
int retries = MAX_HOST_RESET_RETRIES;
- ufshcd_reset_vendor(hba);
+ ufshcd_wb_reset_vendor(hba);
do {
/* Reset the attached device */
diff --git a/drivers/scsi/ufs/ufshcd.h b/drivers/scsi/ufs/ufshcd.h
index deb9577e0eaa..61ae5259c62a 100644
--- a/drivers/scsi/ufs/ufshcd.h
+++ b/drivers/scsi/ufs/ufshcd.h
@@ -1217,7 +1217,7 @@ static int ufshcd_wb_ctrl_vendor(struct ufs_hba *hba, bool enable)
return hba->wb_ops->wb_ctrl_vendor(hba, enable);
}
-static int ufshcd_reset_vendor(struct ufs_hba *hba)
+static int ufshcd_wb_reset_vendor(struct ufs_hba *hba)
{
if (!hba->wb_ops || !hba->wb_ops->wb_reset_vendor)
return -1;
--
2.26.0
next prev 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 ` [RFC PATCH v2 0/3] Support vendor specific operations for WB SEO HOYOUNG
[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 ` SEO HOYOUNG [this message]
2020-07-21 6:36 ` [RFC PATCH v2 2/3] scsi: ufs: modify function call name When ufs reset and restore, need to disable " 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=98b5339dc9c5dc57ed72e83bc7c39c4211d20b6a.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).