mirror of https://lore.kernel.org/lkml/
 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>,
	<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 04/10] scsi: ufs: ufs-qcom: Limit negotiated gear to selected PHY gear
Date: Tue, 28 Nov 2023 16:05:59 +0800	[thread overview]
Message-ID: <bc69d9ef-6ddc-4389-8bf0-9405385a494b@quicinc.com> (raw)
In-Reply-To: <20231128054522.GF3088@thinkpad>

Hi Mani,

On 11/28/2023 1:45 PM, Manivannan Sadhasivam wrote:
> On Thu, Nov 23, 2023 at 12:46:24AM -0800, Can Guo wrote:
>> In the dual init scenario, the initial PHY gear is set to HS-G2, and the
>> first Power Mode Change (PMC) is meant to find the best matching PHY gear
>> for the 2nd init. However, for the first PMC, if the negotiated gear (say
>> HS-G4) is higher than the initial PHY gear, we cannot go ahead let PMC to
>> the negotiated gear happen, because the programmed UFS PHY settings may not
>> support the negotiated gear. Fix it by overwriting the negotiated gear with
>> the PHY gear.
>>
> 
> I don't quite understand this patch. If the phy_gear is G2 initially and the
> negotiated gear is G4, then as per this change,
> 
> phy_gear = G4;
> negotiated gear = G2;
> 
> Could you please explain how this make sense?

phy_gear was G2 (in the beginning) and just now changed to G4, but the 
PHY settings programmed in the beginning can only support no-G4 (not 
G4). Without this change, as the negotiated gear is G4, the power mode 
change is going to put UFS at HS-G4 mode, but the PHY settings 
programmed is no-G4. This change is to limit the negotiated gear to 
HS-G2 for the 1st init. In the 2nd init, as the new PHY gear is G4, G4 
PHY settings would be programmed, it'd be safe to put the UFS at HS-G4 mode.

Thanks,
Can Guo.
> 
> - Mani
> 
>> Signed-off-by: Can Guo <quic_cang@quicinc.com>
>> ---
>>   drivers/ufs/host/ufs-qcom.c | 7 ++++++-
>>   1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
>> index cc0eb37..d4edf58 100644
>> --- a/drivers/ufs/host/ufs-qcom.c
>> +++ b/drivers/ufs/host/ufs-qcom.c
>> @@ -920,8 +920,13 @@ static int ufs_qcom_pwr_change_notify(struct ufs_hba *hba,
>>   		 * because, the PHY gear settings are backwards compatible and we only need to
>>   		 * change the PHY gear settings while scaling to higher gears.
>>   		 */
>> -		if (dev_req_params->gear_tx > host->phy_gear)
>> +		if (dev_req_params->gear_tx > host->phy_gear) {
>> +			u32 old_phy_gear = host->phy_gear;
>> +
>>   			host->phy_gear = dev_req_params->gear_tx;
>> +			dev_req_params->gear_tx = old_phy_gear;
>> +			dev_req_params->gear_rx = old_phy_gear;
>> +		}
>>   
>>   		/* enable the device ref clock before changing to HS mode */
>>   		if (!ufshcd_is_hs_mode(&hba->pwr_info) &&
>> -- 
>> 2.7.4
>>
> 

  reply	other threads:[~2023-11-28  8:07 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 [this message]
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
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=bc69d9ef-6ddc-4389-8bf0-9405385a494b@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=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 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®