From: Can Guo <cang@codeaurora.org>
To: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, rnayak@codeaurora.org,
linux-scsi@vger.kernel.org, kernel-team@android.com,
saravanak@google.com, salyzyn@google.com, cang@codeaurora.org
Subject: [PATCH v10 0/7] UFS driver general fixes bundle 4
Date: Mon, 10 Feb 2020 19:40:43 -0800 [thread overview]
Message-ID: <1581392451-28743-1-git-send-email-cang@codeaurora.org> (raw)
This bundle includes 7 general fixes for UFS driver.
Changes since v9:
- Incoperated comments from Hongwu to add a space btw switch and parenthesis in patch #3
Changes since v8:
- Incoperated comments from Arvi to add "Fixes" to commit message of patch #5
- Switched the order of patch #3 and #4 to reflect the dependency.
Changes since v7:
- Incoperated comments from Bjorn and Arvi.
- Removed patch #8.
Changes since v6:
- Incoperated Avri's comment.
Changes since v5:
- Incoperated Stanley's suggestions to make the extra delay added up to bRefClkGatingWaitTime as vendor specific
Changes since v4:
- Rebased this series
Changes since v3:
- Fixed patch #8
Changes since v2:
- Move the ref clk gating wait delay to ufs-qcom.c
- Added one more change to select INITIAL adapt for HS G4
Changes since v1:
- Fixed minor typo
Asutosh Das (1):
scsi: ufs: set load before setting voltage in regulators
Can Guo (5):
scsi: ufs-qcom: Adjust bus bandwidth voting and unvoting
scsi: ufs: Remove the check before call setup clock notify vops
scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic
scsi: ufs: Add dev ref clock gating wait time support
scsi: ufs-qcom: Delay specific time before gate ref clk
Sayali Lokhande (1):
scsi: ufs: Flush exception event before suspend
drivers/scsi/ufs/ufs-qcom.c | 100 +++++++++++++++++++++++++++++++-------------
drivers/scsi/ufs/ufs.h | 3 ++
drivers/scsi/ufs/ufshcd.c | 96 +++++++++++++++++++++++++++++-------------
3 files changed, 143 insertions(+), 56 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2020-02-11 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 3:40 Can Guo [this message]
2020-02-11 3:40 ` [PATCH v10 1/7] scsi: ufs: Flush exception event before suspend Can Guo
2020-02-14 2:48 ` hongwus
2020-02-11 3:40 ` [PATCH v10 2/7] scsi: ufs: set load before setting voltage in regulators Can Guo
2020-02-11 3:40 ` [PATCH v10 3/7] scsi: ufs-qcom: Adjust bus bandwidth voting and unvoting Can Guo
2020-02-11 3:40 ` [PATCH v10 4/7] scsi: ufs: Remove the check before call setup clock notify vops Can Guo
2020-02-11 3:40 ` [PATCH v10 5/7] scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic Can Guo
2020-02-11 3:40 ` [PATCH v10 6/7] scsi: ufs: Add dev ref clock gating wait time support Can Guo
2020-02-11 3:40 ` [PATCH v10 7/7] scsi: ufs-qcom: Delay specific time before gate ref clk Can Guo
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=1581392451-28743-1-git-send-email-cang@codeaurora.org \
--to=cang@codeaurora.org \
--cc=asutoshd@codeaurora.org \
--cc=hongwus@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nguyenb@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.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).