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 v3 0/3] Three changes related with UFS clock scaling
Date: Sun, 13 Dec 2020 08:13:16 -0800 [thread overview]
Message-ID: <1607876000-3293-1-git-send-email-cang@codeaurora.org> (raw)
This series is made based on 5.10/scsi-fixes branch.
Current devfreq framework allows sysfs nodes like governor, min_freq and max_freq to be changed even after devfreq device is suspended.
Meanwhile, devfreq_suspend_device() cannot/wouldn't synchronize ongoing execution invoked through sysfs nodes menitioned above either.
It means that UFS clock scaling can be invoked at any time (clkscale_enable is same) regardless of the state of UFS host and/or device.
The 1st change allows contexts to prevent clock scaling from being invoked through sysfs nodes like clkscale_enable.
The 2nd change is just a minor code cleanup.
The 3rd change revert one old change which can be covered by the 1st change. For branches which do not have this change yet, it can be ignored.
Change since v2:
- Split the 1st change to two changes - the 1st change and the 3rd change
Change since v1:
- Updated the 2nd change
Can Guo (3):
scsi: ufs: Protect some contexts from unexpected clock scaling
scsi: ufs: Clean up ufshcd_exit_clk_scaling/gating()
scsi: ufs: Revert "Make sure clk scaling happens only when HBA is
runtime ACTIVE"
drivers/scsi/ufs/ufshcd.c | 121 +++++++++++++++++++++++++++-------------------
drivers/scsi/ufs/ufshcd.h | 6 +++
2 files changed, 76 insertions(+), 51 deletions(-)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2020-12-13 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 16:13 Can Guo [this message]
2020-12-13 16:13 ` [PATCH v3 1/3] scsi: ufs: Protect some contexts from unexpected clock scaling Can Guo
2020-12-13 16:13 ` [PATCH v3 2/3] scsi: ufs: Clean up ufshcd_exit_clk_scaling/gating() Can Guo
2020-12-13 16:13 ` [PATCH v3 3/3] scsi: ufs: Revert "Make sure clk scaling happens only when HBA is runtime ACTIVE" 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=1607876000-3293-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).