All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/2] Two changes related with UFS clock scaling
Date: Wed,  9 Dec 2020 05:35:39 -0800	[thread overview]
Message-ID: <1607520942-22254-1-git-send-email-cang@codeaurora.org> (raw)

This series is made based on 5.11/scsi-fixes branch.
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.

Change since v1:
- Updated the 2nd change

Can Guo (2):
  scsi: ufs: Protect some contexts from unexpected clock scaling
  scsi: ufs: Clean up ufshcd_exit_clk_scaling/gating()

 drivers/scsi/ufs/ufshcd.c | 116 ++++++++++++++++++++++++++--------------------
 drivers/scsi/ufs/ufshcd.h |   6 +++
 2 files changed, 71 insertions(+), 51 deletions(-)

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.


             reply	other threads:[~2020-12-09 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 13:35 Can Guo [this message]
2020-12-09 13:35 ` [PATCH 1/2] scsi: ufs: Protect some contexts from unexpected clock scaling Can Guo
2020-12-10 17:34   ` Bean Huo
2020-12-11  1:09     ` Can Guo
2020-12-11  1:36     ` Can Guo
2020-12-11 11:13       ` Can Guo
2020-12-09 13:35 ` [PATCH 2/2] scsi: ufs: Clean up ufshcd_exit_clk_scaling/gating() Can Guo
2020-12-10 18:03   ` Bean Huo
2020-12-11  1:11     ` 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=1607520942-22254-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.