From: Can Guo <quic_cang@quicinc.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: <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 16:21:39 +0800 [thread overview]
Message-ID: <a8eef2d5-5ac5-45bb-97ba-1d6acd5a6a5c@quicinc.com> (raw)
In-Reply-To: <20231130072529.GI3043@thinkpad>
On 11/30/2023 3:25 PM, Manivannan Sadhasivam 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;
>
> No need to initialize dev_major.
True.
>
>>
>> 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 {
>
> Can you please add a comment here to describe what is happening?
Will do.
>
>> + val = ufshcd_readl(host->hba, REG_UFS_DEBUG_SPARE_CFG);
>> + dev_major = FIELD_GET(GENMASK(7, 4), val);
>
> It'd be good to add a macro for GENMASK().
OK
>
>> +
>> + /* UFS device version populated, no need to do init twice */
>
> "Since the UFS device version is populated, let's remove the REINIT quirk as the
> negotiated gear won't change during boot. So there is no need to do reinit."
>
Nice comment.
>> + if (dev_major != 0)
>
> 0x0
Done
>
>> + 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)
>
> if (dev_major > 0x0 && dev_major < 0x4)
>
Sure.
Thanks,
Can Guo.
> - Mani
>
>> + 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
>>
>>
>
prev parent reply other threads:[~2023-11-30 8:22 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
2023-11-30 7:25 ` Manivannan Sadhasivam
2023-11-30 8:21 ` Can Guo [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=a8eef2d5-5ac5-45bb-97ba-1d6acd5a6a5c@quicinc.com \
--to=quic_cang@quicinc.com \
--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=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=mani@kernel.org \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®