linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Eric Chanudet <echanude@redhat.com>
Cc: Can Guo <quic_cang@quicinc.com>,
	bvanassche@acm.org, adrian.hunter@intel.com, cmd4@qualcomm.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,
	"Bao D. Nguyen" <quic_nguyenb@quicinc.com>,
	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 v6 10/10] scsi: ufs: ufs-qcom: Add support for UFS device version detection
Date: Thu, 30 Nov 2023 12:58:59 +0530	[thread overview]
Message-ID: <20231130072859.GJ3043@thinkpad> (raw)
In-Reply-To: <rgn6deseihby3wuwqll5qkephtzthcpxvoel6fpf6baxwjabjb@3fnuzl7bhako>

On Wed, Nov 29, 2023 at 02:04:35PM -0500, Eric Chanudet wrote:
> On Wed, Nov 29, 2023 at 12:28:35AM -0800, Can Guo wrote:
> > From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
> > 
> > A spare register in UFS host controller is used to indicate the UFS device
> > version. The spare register is populated by bootloader for now, but in
> > future it will be populated by HW automatically during link startup with
> > its best efforts in any boot stages prior to Linux.
> > 
> > During host driver init, read the spare register, if it is not populated
> > with a UFS device version, go ahead with the dual init mechanism. If a UFS
> > device version is in there, use the UFS device version together with host
> > controller's HW version to decide the proper PHY gear which should be used
> > to configure the UFS PHY without going through the second init.
> > 
> > Signed-off-by: Bao D. Nguyen <quic_nguyenb@quicinc.com>
> > Signed-off-by: Can Guo <quic_cang@quicinc.com>
> > ---
> >  drivers/ufs/host/ufs-qcom.c | 23 ++++++++++++++++++-----
> >  drivers/ufs/host/ufs-qcom.h |  2 ++
> >  2 files changed, 20 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
> > index 9c0ebbc..e94dea2 100644
> > --- a/drivers/ufs/host/ufs-qcom.c
> > +++ b/drivers/ufs/host/ufs-qcom.c
> > @@ -1068,15 +1068,28 @@ static void ufs_qcom_advertise_quirks(struct ufs_hba *hba)
> >  static void ufs_qcom_set_phy_gear(struct ufs_qcom_host *host)
> >  {
> >  	struct ufs_host_params *host_params = &host->host_params;
> > +	u32 val, dev_major = 0;
> >  
> >  	host->phy_gear = host_params->hs_tx_gear;
> >  
> > -	/*
> > -	 * Power up the PHY using the minimum supported gear (UFS_HS_G2).
> > -	 * Switching to max gear will be performed during reinit if supported.
> > -	 */
> > -	if (host->hw_ver.major < 0x4)
> > +	if (host->hw_ver.major < 0x4) {
> > +		/*
> > +		 * Power up the PHY using the minimum supported gear (UFS_HS_G2).
> > +		 * Switching to max gear will be performed during reinit if supported.
> > +		 */
> >  		host->phy_gear = UFS_HS_G2;
> > +	} else {
> > +		val = ufshcd_readl(host->hba, REG_UFS_DEBUG_SPARE_CFG);
> > +		dev_major = FIELD_GET(GENMASK(7, 4), val);
> > +
> > +		/* UFS device version populated, no need to do init twice */
> 
> This change documents the content of the register as "UFS device
> version", both inline in the code and in the commit description. Earlier
> in this series[1], Mani mentioned it was the gear info:
> > > [...]populating a spare register in the bootloader with the max gear
> > > info that the bootloader has already found[...]
> 
> Is it the gear number as in HS-G4? Or the version as in UFS controller
> revision 3.1?
> 

That was a mistake from my end, apologies. The register has the device version
only and the driver uses both device and host controller's version info to
decide the initial gear.

- Mani

> [1] https://lore.kernel.org/all/20231018124741.GA47321@thinkpad/
> 
> > +		if (dev_major != 0)
> > +			host->hba->quirks &= ~UFSHCD_QUIRK_REINIT_AFTER_MAX_GEAR_SWITCH;
> > +
> > +		/* For UFS 3.1 and older, apply HS-G4 PHY gear to save power */
> > +		if (dev_major < 0x4 && dev_major > 0)
> > +			host->phy_gear = UFS_HS_G4;
> > +	}
> >  }
> >  
> >  static void ufs_qcom_set_host_params(struct ufs_hba *hba)
> > diff --git a/drivers/ufs/host/ufs-qcom.h b/drivers/ufs/host/ufs-qcom.h
> > index 11419eb..d12fc5a 100644
> > --- a/drivers/ufs/host/ufs-qcom.h
> > +++ b/drivers/ufs/host/ufs-qcom.h
> > @@ -54,6 +54,8 @@ enum {
> >  	UFS_AH8_CFG				= 0xFC,
> >  
> >  	REG_UFS_CFG3				= 0x271C,
> > +
> > +	REG_UFS_DEBUG_SPARE_CFG			= 0x284C,
> >  };
> >  
> >  /* QCOM UFS host controller vendor specific debug registers */
> > -- 
> > 2.7.4
> > 
> > 
> 
> -- 
> Eric Chanudet
> 
> 

-- 
மணிவண்ணன் சதாசிவம்

  reply	other threads:[~2023-11-30  7:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  8:28 [PATCH v6 00/10] Enable HS-G5 support on SM8550 Can Guo
2023-11-29  8:28 ` [PATCH v6 01/10] scsi: ufs: host: Rename structure ufs_dev_params to ufs_host_params Can Guo
2023-11-29 18:11   ` Bart Van Assche
2023-11-29  8:28 ` [PATCH v6 02/10] scsi: ufs: ufs-qcom: No need to set hs_rate after ufshcd_init_host_param() Can Guo
2023-11-29 20:48   ` Andrew Halaney
2023-11-29  8:28 ` [PATCH v6 03/10] scsi: ufs: ufs-qcom: Setup host power mode during init Can Guo
2023-11-29  8:28 ` [PATCH v6 04/10] scsi: ufs: ufs-qcom: Allow the first init start with the maximum supported gear Can Guo
2023-11-30  6:42   ` Manivannan Sadhasivam
2023-11-30  7:44     ` Can Guo
2023-11-29  8:28 ` [PATCH v6 05/10] scsi: ufs: ufs-qcom: Limit HS-G5 Rate-A to hosts with HW version 5 Can Guo
2023-11-29  8:28 ` [PATCH v6 06/10] scsi: ufs: ufs-qcom: Set initial PHY gear to max HS gear for HW ver 4 and newer Can Guo
2023-11-30  5:52   ` Nitin Rawat
2023-11-30  6:47   ` Manivannan Sadhasivam
2023-11-30  7:49     ` Can Guo
2023-11-29  8:28 ` [PATCH v6 07/10] phy: qualcomm: phy-qcom-qmp-ufs: Rectify SM8550 UFS HS-G4 PHY Settings Can Guo
2023-11-29  8:28 ` [PATCH v6 08/10] phy: qualcomm: phy-qcom-qmp-ufs: Add High Speed Gear 5 support for SM8550 Can Guo
2023-11-30  7:12   ` Manivannan Sadhasivam
2023-11-30  8:14     ` Can Guo
2023-11-30  8:38       ` Manivannan Sadhasivam
2023-11-30  8:49         ` Can Guo
2023-11-30  9:34           ` Manivannan Sadhasivam
2023-11-30  9:35             ` Can Guo
2023-11-29  8:28 ` [PATCH v6 09/10] scsi: ufs: ufs-qcom: Check return value of phy_set_mode_ext() Can Guo
2023-11-29  8:38   ` Nitin Rawat
2023-11-30  7:16   ` Manivannan Sadhasivam
2023-11-30  8:19     ` Can Guo
2023-11-29  8:28 ` [PATCH v6 10/10] scsi: ufs: ufs-qcom: Add support for UFS device version detection Can Guo
2023-11-29 19:04   ` Eric Chanudet
2023-11-30  7:28     ` Manivannan Sadhasivam [this message]
2023-11-30  7:25   ` Manivannan Sadhasivam
2023-11-30  8:21     ` 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=20231130072859.GJ3043@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=cmd4@qualcomm.com \
    --cc=echanude@redhat.com \
    --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 \
    --cc=quic_nguyenb@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).