From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Can Guo <cang@codeaurora.org>
Cc: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, linux-scsi@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v11 0/3] Three changes related with UFS clock scaling
Date: Wed, 20 Jan 2021 22:28:06 -0500 [thread overview]
Message-ID: <yq1turbezqn.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1611137065-14266-1-git-send-email-cang@codeaurora.org> (Can Guo's message of "Wed, 20 Jan 2021 02:04:20 -0800")
Can,
> This series is made based on 5.12/scsi-queue 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 clock
> scaling which has already been invoked through devfreq sysfs nodes
> menitioned above. It means that clock scaling invoked through these
> devfreq sysfs nodes can happen at any time regardless of the state of
> UFS host and/or device. We need to control and synchronize clock
> scaling in this scenario.
Applied to 5.12/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-01-21 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 10:04 [PATCH v11 0/3] Three changes related with UFS clock scaling Can Guo
2021-01-20 10:04 ` [PATCH v11 1/3] scsi: ufs: Protect some contexts from unexpected " Can Guo
2021-01-20 13:14 ` Stanley Chu
2021-01-20 10:04 ` [PATCH v11 2/3] scsi: ufs: Refactor ufshcd_init/exit_clk_scaling/gating() Can Guo
2021-01-20 10:04 ` [PATCH v11 3/3] scsi: ufs: Revert "Make sure clk scaling happens only when HBA is runtime ACTIVE" Can Guo
2021-01-21 3:28 ` Martin K. Petersen [this message]
2021-01-23 4:22 ` [PATCH v11 0/3] Three changes related with UFS clock scaling Martin K. Petersen
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=yq1turbezqn.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=hongwus@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nguyenb@codeaurora.org \
/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