From: <peter.wang@mediatek.com>
To: <stanley.chu@mediatek.com>, <linux-scsi@vger.kernel.org>,
<martin.petersen@oracle.com>, <avri.altman@wdc.com>,
<alim.akhtar@samsung.com>, <jejb@linux.ibm.com>
Cc: <wsd_upstream@mediatek.com>, <linux-mediatek@lists.infradead.org>,
<peter.wang@mediatek.com>, <chun-hung.wu@mediatek.com>,
<alice.chao@mediatek.com>, <cc.chou@mediatek.com>,
<chaotian.jing@mediatek.com>, <jiajie.hao@mediatek.com>,
<powen.kao@mediatek.com>, <qilin.tan@mediatek.com>,
<lin.gui@mediatek.com>
Subject: [PATCH v3 0/2] ufs: allow host driver disable wb toggle druing clock scaling
Date: Tue, 2 Aug 2022 22:32:21 +0800 [thread overview]
Message-ID: <20220802143223.1276-1-peter.wang@mediatek.com> (raw)
From: Peter Wang <peter.wang@mediatek.com>
Mediatek ufs do not want to toggle write booster during clock scaling.
This patch set allow host driver disable wb toggle during clock scaling.
Peter Wang (2):
ufs: core: introduce a choice of wb toggle during clock scaling
ufs: host: support wb toggle with clock scaling
drivers/ufs/core/ufs-sysfs.c | 3 ++-
drivers/ufs/core/ufshcd.c | 8 +++++---
drivers/ufs/host/ufs-qcom.c | 2 +-
include/ufs/ufshcd.h | 7 +++++++
4 files changed, 15 insertions(+), 5 deletions(-)
--
2.18.0
next reply other threads:[~2022-08-02 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 14:32 peter.wang [this message]
2022-08-02 14:32 ` [PATCH v3 1/2] ufs: core: introduce a choice of wb toggle during clock scaling peter.wang
2022-08-02 18:44 ` Bart Van Assche
2022-08-03 2:44 ` Peter Wang
2022-08-02 14:32 ` [PATCH v3 2/2] ufs: host: support wb toggle with " peter.wang
2022-08-02 18:46 ` Bart Van Assche
2022-08-03 2:42 ` Peter Wang
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=20220802143223.1276-1-peter.wang@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=lin.gui@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=powen.kao@mediatek.com \
--cc=qilin.tan@mediatek.com \
--cc=stanley.chu@mediatek.com \
--cc=wsd_upstream@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;
as well as URLs for NNTP newsgroup(s).