mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nitin Rawat <quic_nitirawa@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: <vkoul@kernel.org>, <kishon@kernel.org>,
	<James.Bottomley@hansenpartnership.com>,
	<martin.petersen@oracle.com>, <bvanassche@acm.org>,
	<andersson@kernel.org>, <neil.armstrong@linaro.org>,
	<dmitry.baryshkov@oss.qualcomm.com>,
	<konrad.dybcio@oss.qualcomm.com>, <quic_rdwivedi@quicinc.com>,
	<quic_cang@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
	<linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH V5 01/11] scsi: ufs: qcom: add a new phy calibrate API call
Date: Thu, 22 May 2025 03:14:39 +0530	[thread overview]
Message-ID: <5d63551f-5401-4c4a-981f-1fa71d73387f@quicinc.com> (raw)
In-Reply-To: <jnftkie5c5hi6nqhliktxqbj7gykj53lvm5gibt3fjdcq7dber@bh4fxrp3fezu>



On 5/21/2025 6:38 PM, Manivannan Sadhasivam wrote:
> On Thu, May 15, 2025 at 09:57:12PM +0530, Nitin Rawat wrote:
>> Introduce a new phy calibrate API call in the UFS Qualcomm driver to
>> separate phy calibration from phy power-on. This change is a precursor
>> to the next patchset in this series, which requires these two operations
> 
> 'next patchset in the series' wouldn't make sense once this patch gets merged.
> They all become commits. So you should mention 'successive commits'.

Sure, will address in next patchset.

> 
>> to be distinct.
>>
>> Signed-off-by: Nitin Rawat <quic_nitirawa@quicinc.com>
> 
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> 
> - Mani
> 
>> ---
>>   drivers/ufs/host/ufs-qcom.c | 6 ++++++
>>   1 file changed, 6 insertions(+)
>>
>> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
>> index 37887ec68412..23b4fc84dc8c 100644
>> --- a/drivers/ufs/host/ufs-qcom.c
>> +++ b/drivers/ufs/host/ufs-qcom.c
>> @@ -531,6 +531,12 @@ static int ufs_qcom_power_up_sequence(struct ufs_hba *hba)
>>   		goto out_disable_phy;
>>   	}
>>   
>> +	ret = phy_calibrate(phy);
>> +	if (ret) {
>> +		dev_err(hba->dev, "Failed to calibrate PHY: %d\n", ret);
>> +		goto out_disable_phy;
>> +	}
>> +
>>   	ufs_qcom_select_unipro_mode(host);
>>   
>>   	return 0;
>> -- 
>> 2.48.1
>>
> 


  reply	other threads:[~2025-05-21 21:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 16:27 [PATCH V5 00/11] Refactor ufs phy powerup sequence Nitin Rawat
2025-05-15 16:27 ` [PATCH V5 01/11] scsi: ufs: qcom: add a new phy calibrate API call Nitin Rawat
2025-05-18 22:50   ` Dmitry Baryshkov
2025-05-21 13:08   ` Manivannan Sadhasivam
2025-05-21 21:44     ` Nitin Rawat [this message]
2025-05-15 16:27 ` [PATCH V5 02/11] phy: qcom-qmp-ufs: Rename qmp_ufs_enable and qmp_ufs_power_on Nitin Rawat
2025-05-21 13:09   ` Manivannan Sadhasivam
2025-05-15 16:27 ` [PATCH V5 03/11] phy: qcom-qmp-ufs: Refactor phy_power_on and phy_calibrate callbacks Nitin Rawat
2025-05-21 13:13   ` Manivannan Sadhasivam
2025-05-15 16:27 ` [PATCH V5 04/11] phy: qcom-qmp-ufs: Refactor UFS PHY reset Nitin Rawat
2025-05-21 13:26   ` Manivannan Sadhasivam
2025-05-21 21:47     ` Nitin Rawat
2025-05-15 16:27 ` [PATCH V5 05/11] phy: qcom-qmp-ufs: Remove qmp_ufs_com_init() Nitin Rawat
2025-05-21 13:30   ` Manivannan Sadhasivam
2025-05-21 21:49     ` Nitin Rawat
2025-05-15 16:27 ` [PATCH V5 06/11] phy: qcom-qmp-ufs: Rename qmp_ufs_power_off Nitin Rawat
2025-05-18 22:47   ` Dmitry Baryshkov
2025-05-19 13:11   ` neil.armstrong
2025-05-15 16:27 ` [PATCH V5 07/11] phy: qcom-qmp-ufs: Remove qmp_ufs_exit() and Inline qmp_ufs_com_exit() Nitin Rawat
2025-05-21 13:49   ` Manivannan Sadhasivam
2025-05-21 22:19     ` Nitin Rawat
2025-05-22  8:53       ` Manivannan Sadhasivam
2025-05-22  9:20         ` Nitin Rawat
2025-05-15 16:27 ` [PATCH V5 08/11] phy: qcom-qmp-ufs: refactor qmp_ufs_power_off Nitin Rawat
2025-05-21 13:50   ` Manivannan Sadhasivam
2025-05-15 16:27 ` [PATCH V5 09/11] scsi: ufs: qcom : Refactor phy_power_on/off calls Nitin Rawat
2025-05-21 13:57   ` Manivannan Sadhasivam
2025-05-21 21:40     ` Nitin Rawat
2025-05-22  8:55       ` Manivannan Sadhasivam
2025-05-22  9:19         ` Nitin Rawat
2025-05-15 16:27 ` [PATCH V5 10/11] scsi: ufs: qcom : Introduce phy_power_on/off wrapper function Nitin Rawat
2025-05-21 14:01   ` Manivannan Sadhasivam
2025-05-21 22:18     ` Nitin Rawat
2025-05-22  9:31       ` Manivannan Sadhasivam
2025-05-22 10:26         ` Nitin Rawat
2025-05-15 16:27 ` [PATCH V5 11/11] scsi: ufs: qcom: Prevent calling phy_exit before phy_init Nitin Rawat
2025-05-21 14:05   ` Manivannan Sadhasivam
2025-05-21 22:21     ` Nitin Rawat
2025-05-21  1:45 ` [PATCH V5 00/11] Refactor ufs phy powerup sequence Martin K. Petersen
2025-05-21 13:10   ` Dmitry Baryshkov
2025-05-27 15:22     ` Nitin Rawat

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=5d63551f-5401-4c4a-981f-1fa71d73387f@quicinc.com \
    --to=quic_nitirawa@quicinc.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=andersson@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_cang@quicinc.com \
    --cc=quic_rdwivedi@quicinc.com \
    --cc=vkoul@kernel.org \
    /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®