From: Manivannan Sadhasivam <mani@kernel.org>
To: Can Guo <quic_cang@quicinc.com>
Cc: bvanassche@acm.org, adrian.hunter@intel.com, beanhuo@micron.com,
avri.altman@wdc.com, junwoo80.lee@samsung.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 06/10] scsi: ufs: ufs-qcom: Limit HS-G5 Rate-A to hosts with HW version 5
Date: Tue, 28 Nov 2023 16:25:06 +0530 [thread overview]
Message-ID: <20231128105506.GO3088@thinkpad> (raw)
In-Reply-To: <4648b6a0-92cb-4411-9b58-03219962505d@quicinc.com>
On Tue, Nov 28, 2023 at 03:48:02PM +0800, Can Guo wrote:
> Hi Mani,
>
> On 11/28/2023 1:55 PM, Manivannan Sadhasivam wrote:
> > On Thu, Nov 23, 2023 at 12:46:26AM -0800, Can Guo wrote:
> > > Qcom UFS hosts, with HW ver 5, can only support up to HS-G5 Rate-A due to
> > > HW limitations. If the HS-G5 PHY gear is used, update host_params->hs_rate
> > > to Rate-A, so that the subsequent power mode changes shall stick to Rate-A.
> > >
> > > Signed-off-by: Can Guo <quic_cang@quicinc.com>
> >
> > Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> >
> > One question below...
> >
> > > ---
> > > drivers/ufs/host/ufs-qcom.c | 18 +++++++++++++++++-
> > > 1 file changed, 17 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
> > > index 9613ad9..6756f8d 100644
> > > --- a/drivers/ufs/host/ufs-qcom.c
> > > +++ b/drivers/ufs/host/ufs-qcom.c
> > > @@ -442,9 +442,25 @@ static u32 ufs_qcom_get_hs_gear(struct ufs_hba *hba)
> > > static int ufs_qcom_power_up_sequence(struct ufs_hba *hba)
> > > {
> > > struct ufs_qcom_host *host = ufshcd_get_variant(hba);
> > > + struct ufs_host_params *host_params = &host->host_params;
> > > struct phy *phy = host->generic_phy;
> > > + enum phy_mode mode;
> > > int ret;
> > > + /*
> > > + * HW ver 5 can only support up to HS-G5 Rate-A due to HW limitations.
> > > + * If the HS-G5 PHY gear is used, update host_params->hs_rate to Rate-A,
> > > + * so that the subsequent power mode change shall stick to Rate-A.
> > > + */
> > > + if (host->hw_ver.major == 0x5) {
> > > + if (host->phy_gear == UFS_HS_G5)
> > > + host_params->hs_rate = PA_HS_MODE_A;
> > > + else
> > > + host_params->hs_rate = PA_HS_MODE_B;
> >
> > Is this 'else' part really needed? Since there wouldn't be any 2nd init, I think
> > we can skip that.
>
> We need it because, even there is only one init, if a UFS3.1 device is
> attached, phy_gear is given as UFS_HS_G4 in ufs_qcom_set_phy_gear(), hence
> we need to put the UFS at HS-G4 Rate B, not Rate A.
>
But the default hs_rate is PA_HS_MODE_B only and the else condition would be not
needed for the 1st init.
- Mani
> Thanks,
> Can Guo.
>
> >
> > - Mani
> >
> > > + }
> > > +
> > > + mode = host_params->hs_rate == PA_HS_MODE_B ? PHY_MODE_UFS_HS_B : PHY_MODE_UFS_HS_A;
> > > +
> > > /* Reset UFS Host Controller and PHY */
> > > ret = ufs_qcom_host_reset(hba);
> > > if (ret)
> > > @@ -459,7 +475,7 @@ static int ufs_qcom_power_up_sequence(struct ufs_hba *hba)
> > > return ret;
> > > }
> > > - phy_set_mode_ext(phy, PHY_MODE_UFS_HS_B, host->phy_gear);
> > > + phy_set_mode_ext(phy, mode, host->phy_gear);
> > > /* power on phy - start serdes and phy's power and clocks */
> > > ret = phy_power_on(phy);
> > > --
> > > 2.7.4
> > >
> >
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-11-28 10:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 8:46 [PATCH v5 00/10] Enable HS-G5 support on SM8550 Can Guo
2023-11-23 8:46 ` [PATCH v5 01/10] scsi: ufs: host: Rename structure ufs_dev_params to ufs_host_params Can Guo
2023-11-28 5:19 ` Manivannan Sadhasivam
2023-11-28 5:31 ` Manivannan Sadhasivam
2023-11-28 7:49 ` Can Guo
2023-11-28 5:31 ` Nitin Rawat
2023-11-23 8:46 ` [PATCH v5 02/10] scsi: ufs: ufs-qcom: No need to set hs_rate after ufshcd_init_host_param() Can Guo
2023-11-28 5:10 ` Nitin Rawat
2023-11-28 5:22 ` Manivannan Sadhasivam
2023-11-23 8:46 ` [PATCH v5 03/10] scsi: ufs: ufs-qcom: Setup host power mode during init Can Guo
2023-11-28 5:06 ` Nitin Rawat
2023-11-28 5:24 ` Manivannan Sadhasivam
2023-11-23 8:46 ` [PATCH v5 04/10] scsi: ufs: ufs-qcom: Limit negotiated gear to selected PHY gear Can Guo
2023-11-28 5:45 ` Manivannan Sadhasivam
2023-11-28 8:05 ` Can Guo
2023-11-28 10:52 ` Manivannan Sadhasivam
2023-11-28 11:03 ` Can Guo
2023-11-28 11:20 ` Manivannan Sadhasivam
2023-11-23 8:46 ` [PATCH v5 05/10] scsi: ufs: ufs-qcom: Allow the first init start with the maximum supported gear Can Guo
2023-11-23 8:46 ` [PATCH v5 06/10] scsi: ufs: ufs-qcom: Limit HS-G5 Rate-A to hosts with HW version 5 Can Guo
2023-11-28 5:15 ` Nitin Rawat
2023-11-28 5:55 ` Manivannan Sadhasivam
2023-11-28 7:48 ` Can Guo
2023-11-28 10:55 ` Manivannan Sadhasivam [this message]
2023-11-28 10:59 ` Can Guo
2023-11-28 11:24 ` Manivannan Sadhasivam
2023-11-23 8:46 ` [PATCH v5 07/10] scsi: ufs: ufs-qcom: Set initial PHY gear to max HS gear for HW ver 5 and newer Can Guo
2023-11-28 6:00 ` Manivannan Sadhasivam
2023-11-28 7:58 ` Can Guo
2023-11-28 10:59 ` Manivannan Sadhasivam
2023-11-28 11:01 ` Can Guo
2023-11-28 11:22 ` Manivannan Sadhasivam
2023-11-23 8:46 ` [PATCH v5 08/10] phy: qualcomm: phy-qcom-qmp-ufs: Rectify SM8550 UFS HS-G4 PHY Settings Can Guo
2023-11-27 11:07 ` Vinod Koul
2023-11-28 1:50 ` Can Guo
2023-11-28 6:02 ` Manivannan Sadhasivam
2023-11-23 8:46 ` [PATCH v5 09/10] phy: qualcomm: phy-qcom-qmp-ufs: Add High Speed Gear 5 support for SM8550 Can Guo
2023-11-23 12:35 ` Dmitry Baryshkov
2023-11-24 1:55 ` Can Guo
2023-11-28 6:47 ` Manivannan Sadhasivam
2023-11-28 9:00 ` Can Guo
2023-11-28 9:59 ` neil.armstrong
2023-11-28 10:03 ` Can Guo
2023-11-23 8:46 ` [PATCH v5 10/10] scsi: ufs: ufs-qcom: Add support for UFS device version detection 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=20231128105506.GO3088@thinkpad \
--to=mani@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=junwoo80.lee@samsung.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=martin.petersen@oracle.com \
--cc=quic_cang@quicinc.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).