From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
bvanassche@acm.org, avri.altman@wdc.com, alim.akhtar@samsung.com,
andersson@kernel.org, konrad.dybcio@linaro.org,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_cang@quicinc.com,
quic_nitirawa@quicinc.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: ufs: ufs-qcom: Update PHY settings only when scaling to higher gears
Date: Wed, 13 Sep 2023 21:21:09 -0400 [thread overview]
Message-ID: <yq1fs3heeiu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230908145329.154024-1-manivannan.sadhasivam@linaro.org> (Manivannan Sadhasivam's message of "Fri, 8 Sep 2023 20:23:28 +0530")
Manivannan,
> The "hs_gear" variable is used to program the PHY settings (submode)
> during ufs_qcom_power_up_sequence(). Currently, it is being updated
> every time the agreed gear changes. Due to this, if the gear got
> downscaled before suspend (runtime/system), then while resuming, the
> PHY settings for the lower gear will be applied first and later when
> scaling to max gear with REINIT, the PHY settings for the max gear
> will be applied.
Applied to 6.7/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2023-09-14 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:53 [PATCH 1/2] scsi: ufs: ufs-qcom: Update PHY settings only when scaling to higher gears Manivannan Sadhasivam
2023-09-08 14:53 ` [PATCH 2/2] scsi: ufs: ufs-qcom: Rename "hs_gear" to "phy_gear" Manivannan Sadhasivam
2023-09-11 5:56 ` Can Guo
2023-09-09 11:04 ` [PATCH 1/2] scsi: ufs: ufs-qcom: Update PHY settings only when scaling to higher gears Konrad Dybcio
2023-09-09 13:58 ` Manivannan Sadhasivam
2023-09-11 5:55 ` Can Guo
2023-09-14 1:21 ` Martin K. Petersen [this message]
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=yq1fs3heeiu.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_cang@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=stable@vger.kernel.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 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.