From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Nitin Rawat <quic_nitirawa@quicinc.com>,
vkoul@kernel.org, kishon@kernel.org,
manivannan.sadhasivam@linaro.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, bvanassche@acm.org,
bjorande@quicinc.com, neil.armstrong@linaro.org
Cc: quic_rdwivedi@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 V3 1/9] scsi: ufs: qcom: add a new phy calibrate API call
Date: Wed, 23 Apr 2025 12:42:14 +0200 [thread overview]
Message-ID: <3735f288-5ba2-4582-afbe-8b3f5d0f280c@oss.qualcomm.com> (raw)
In-Reply-To: <20250410090102.20781-2-quic_nitirawa@quicinc.com>
On 4/10/25 11:00 AM, 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
> to be distinct.
>
> Signed-off-by: Nitin Rawat <quic_nitirawa@quicinc.com>
> ---
> 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 1b37449fbffc..4998656e9267 100644
> --- a/drivers/ufs/host/ufs-qcom.c
> +++ b/drivers/ufs/host/ufs-qcom.c
> @@ -473,6 +473,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, "%s: Failed to calibrate PHY %d\n",
Please add a colon, so that it becomes "..PHY: %d\n"
> + __func__, ret);
Avoid __func__, this print is fine without it
Shouldn't we fail the power-on if this can't succeed?
Konrad
next prev parent reply other threads:[~2025-04-23 10:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 9:00 [PATCH V3 0/9] Refactor phy powerup sequence Nitin Rawat
2025-04-10 9:00 ` [PATCH V3 1/9] scsi: ufs: qcom: add a new phy calibrate API call Nitin Rawat
2025-04-23 10:42 ` Konrad Dybcio [this message]
2025-04-23 11:01 ` Nitin Rawat
2025-04-10 9:00 ` [PATCH V3 2/9] phy: qcom-qmp-ufs: Rename qmp_ufs_enable and qmp_ufs_power_on Nitin Rawat
2025-04-10 20:05 ` Dmitry Baryshkov
2025-04-10 9:00 ` [PATCH V3 3/9] phy: qcom-qmp-ufs: Refactor phy_power_on and phy_calibrate callbacks Nitin Rawat
2025-04-10 20:06 ` Dmitry Baryshkov
2025-04-10 9:00 ` [PATCH V3 4/9] phy: qcom-qmp-ufs: Refactor UFS PHY reset Nitin Rawat
2025-04-10 20:08 ` Dmitry Baryshkov
2025-04-11 10:50 ` Nitin Rawat
2025-04-11 11:08 ` Dmitry Baryshkov
2025-04-14 20:34 ` Nitin Rawat
2025-04-15 9:29 ` Dmitry Baryshkov
2025-04-16 9:08 ` Nitin Rawat
2025-04-16 12:13 ` Dmitry Baryshkov
2025-04-16 12:26 ` Nitin Rawat
2025-04-23 11:09 ` Konrad Dybcio
2025-04-23 11:21 ` Konrad Dybcio
2025-04-23 11:43 ` Nitin Rawat
2025-04-23 13:47 ` Konrad Dybcio
2025-04-23 13:51 ` Dmitry Baryshkov
2025-04-10 9:00 ` [PATCH V3 5/9] phy: qcom-qmp-ufs: Remove qmp_ufs_com_init() Nitin Rawat
2025-04-10 20:09 ` Dmitry Baryshkov
2025-04-11 10:42 ` Nitin Rawat
2025-04-11 10:56 ` Dmitry Baryshkov
2025-04-14 7:28 ` Nitin Rawat
2025-04-14 7:43 ` Dmitry Baryshkov
2025-04-19 20:08 ` Nitin Rawat
2025-04-23 13:34 ` Dmitry Baryshkov
2025-04-10 9:00 ` [PATCH V3 6/9] phy: qcom-qmp-ufs: Refactor qmp_ufs_exit callback Nitin Rawat
2025-04-23 11:29 ` Konrad Dybcio
2025-04-10 9:01 ` [PATCH V3 7/9] scsi: ufs: qcom : Refactor phy_power_on/off calls Nitin Rawat
2025-04-10 9:01 ` [PATCH V3 8/9] scsi: ufs: qcom : Introduce phy_power_on/off wrapper function Nitin Rawat
2025-04-10 9:01 ` [PATCH V3 9/9] scsi: ufs: qcom: Prevent calling phy_exit before phy_init Nitin Rawat
2025-04-10 20:05 ` [PATCH V3 0/9] Refactor phy powerup sequence Dmitry Baryshkov
2025-04-11 10:35 ` 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=3735f288-5ba2-4582-afbe-8b3f5d0f280c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bjorande@quicinc.com \
--cc=bvanassche@acm.org \
--cc=kishon@kernel.org \
--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_nitirawa@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