All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	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 04/10] scsi: ufs: ufs-qcom: Allow the first init start with the maximum supported gear
Date: Thu, 30 Nov 2023 15:44:09 +0800	[thread overview]
Message-ID: <df573678-3ca0-4e7e-af73-efa674be7090@quicinc.com> (raw)
In-Reply-To: <20231130064221.GE3043@thinkpad>



On 11/30/2023 2:42 PM, Manivannan Sadhasivam wrote:
> On Wed, Nov 29, 2023 at 12:28:29AM -0800, Can Guo wrote:
>> During host driver init, the phy_gear is set to the minimum supported gear
>> (HS_G2). Then, during the first power mode change, the negotiated gear, say
>> HS-G4, is updated to the phy_gear variable so that in the second init the
>> updated phy_gear can be used to program the PHY.
>>
>> But the current code only allows update the phy_gear to a higher value. If
>> one wants to start the first init with the maximum support gear, say HS-G4,
>> the phy_gear is not updated to HS-G3 if the device only supports HS-G3.
>>
>> The original check added there is intend to make sure the phy_gear won't be
>> updated when gear is scaled down (during clock scaling). Update the check
>> so that one can start the first init with the maximum support gear without
>> breaking the original fix by checking the ufshcd_state, that is, allow
>> update to phy_gear only if power mode change is invoked from
>> ufshcd_probe_hba().
>>
>> This change is a preparation patch for the next patches in the same series.
> 
> If you happen to respin the series, please remove this line. When the patches
> get merged, there will be no concept of patches/series as all will be git
> commits.
> 
> You can have this information in the comment section (below --- line) though.
> 

Sure, will remove it in next version.

Thanks,
Can Guo.

>>
>> Signed-off-by: Can Guo <quic_cang@quicinc.com>
> 
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> 
> - Mani
> 
>> ---
>>   drivers/ufs/host/ufs-qcom.c | 9 +++++----
>>   1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
>> index 9a90019..81056b9 100644
>> --- a/drivers/ufs/host/ufs-qcom.c
>> +++ b/drivers/ufs/host/ufs-qcom.c
>> @@ -916,11 +916,12 @@ static int ufs_qcom_pwr_change_notify(struct ufs_hba *hba,
>>   		}
>>   
>>   		/*
>> -		 * Update phy_gear only when the gears are scaled to a higher value. This is
>> -		 * because, the PHY gear settings are backwards compatible and we only need to
>> -		 * change the PHY gear settings while scaling to higher gears.
>> +		 * During UFS driver probe, always update the PHY gear to match the negotiated
>> +		 * gear, so that, if quirk UFSHCD_QUIRK_REINIT_AFTER_MAX_GEAR_SWITCH is enabled,
>> +		 * the second init can program the optimal PHY settings. This allows one to start
>> +		 * the first init with either the minimum or the maximum support gear.
>>   		 */
>> -		if (dev_req_params->gear_tx > host->phy_gear)
>> +		if (hba->ufshcd_state == UFSHCD_STATE_RESET)
>>   			host->phy_gear = dev_req_params->gear_tx;
>>   
>>   		/* enable the device ref clock before changing to HS mode */
>> -- 
>> 2.7.4
>>
>>
> 

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

Thread overview: 42+ 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 ` 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  8:28   ` Can Guo
2023-11-29 18:11   ` Bart Van Assche
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 [this message]
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   ` 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-29  8:28   ` Can Guo
2023-11-30  7:12   ` Manivannan Sadhasivam
2023-11-30  7:12     ` Manivannan Sadhasivam
2023-11-30  8:14     ` Can Guo
2023-11-30  8:14       ` Can Guo
2023-11-30  8:38       ` Manivannan Sadhasivam
2023-11-30  8:38         ` Manivannan Sadhasivam
2023-11-30  8:49         ` Can Guo
2023-11-30  8:49           ` Can Guo
2023-11-30  9:34           ` Manivannan Sadhasivam
2023-11-30  9:34             ` Manivannan Sadhasivam
2023-11-30  9:35             ` Can Guo
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

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=df573678-3ca0-4e7e-af73-efa674be7090@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 \
    /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.