From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: 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,
konrad.dybcio@oss.qualcomm.com, 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 4/9] phy: qcom-qmp-ufs: Refactor UFS PHY reset
Date: Tue, 15 Apr 2025 12:29:23 +0300 [thread overview]
Message-ID: <c2ec6b7c-421d-43c3-8c0a-de4f7bdd867c@oss.qualcomm.com> (raw)
In-Reply-To: <2820908b-4548-4e0a-94b2-6065cb5ff1f3@quicinc.com>
On 14/04/2025 23:34, Nitin Rawat wrote:
>
>
> On 4/11/2025 4:38 PM, Dmitry Baryshkov wrote:
>> On Fri, 11 Apr 2025 at 13:50, Nitin Rawat <quic_nitirawa@quicinc.com>
>> wrote:
>>>
>>>
>>>
>>> On 4/11/2025 1:38 AM, Dmitry Baryshkov wrote:
>>>> On Thu, Apr 10, 2025 at 02:30:57PM +0530, Nitin Rawat wrote:
>>>>> Refactor the UFS PHY reset handling to parse the reset logic only once
>>>>> during probe, instead of every resume.
>>>>>
>>>>> Move the UFS PHY reset parsing logic from qmp_phy_power_on to
>>>>> qmp_ufs_probe to avoid unnecessary parsing during resume.
>>>>
>>>> How did you solve the circular dependency issue being noted below?
>>>
>>> Hi Dmitry,
>>> As part of my patch, I moved the parsing logic from qmp_phy_power_on to
>>> qmp_ufs_probe to avoid unnecessary parsing during resume. I'm uncertain
>>> about the circular dependency issue and whether if it still exists.
>>
>> It surely does. The reset controller is registered in the beginning of
>> ufs_qcom_init() and the PHY is acquired only a few lines below. It
>> creates a very small window for PHY driver to probe.
>> Which means, NAK, this patch doesn't look acceptable.
>
> Hi Dmitry,
>
> Thanks for pointing this out. I agree that it leaves very little time
> for the PHY to probe, which may cause issues with targets where
> no_pcs_sw_reset is set to true.
>
> As an experiment, I kept no_pcs_sw_reset set to true for the SM8750, and
> it caused bootup probe issues in some of the iterations I ran.
>
> To address this, I propose updating the patch to move the
> qmp_ufs_get_phy_reset call to phy_calibrate, just before the
> reset_control_assert call.
Will it cause an issue if we move it to phy_init() instead of
phy_calibrate()?
>
> This change will delay the UFS PHY reset as much as possible in the
> code. Additionally, moving it from phy_power_on to calibrate will ensure
> that qmp_ufs_get_phy_reset is called only once during boot, rather than
> during each phy_power_on call.
>
> Please let me know your thoughts.
> =====================================================================================================
> static int qmp_ufs_phy_calibrate(struct phy *phy)
> {
> struct qmp_ufs *qmp = phy_get_drvdata(phy);
> @@ -1793,6 +1826,12 @@ static int qmp_ufs_phy_calibrate(struct phy *phy)
> unsigned int val;
> int ret;
>
> + pr_err("%s %d\n", __func__, __LINE__);
> +
> + ret = qmp_ufs_get_phy_reset(qmp);
> + if (ret)
> + return ret;
> +
> ret = reset_control_assert(qmp->ufs_reset);
> if (ret)
> return ret;
> @@ -1817,7 +1856,7 @@ static int qmp_ufs_phy_calibrate(struct phy *phy)
> dev_err(qmp->dev, "phy initialization timed-out\n");
> return ret;
> =====================================================================================================
>
>
> Regards.
> Nitin
>>
>>>
>>> Regards,
>>> Nitin
>>>
>>>
>>>>
>>>>>
>>>>> Co-developed-by: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
>>>>> Signed-off-by: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
>>>>> Signed-off-by: Nitin Rawat <quic_nitirawa@quicinc.com>
>>>>> ---
>>>>> drivers/phy/qualcomm/phy-qcom-qmp-ufs.c | 61 ++++++++++++
>>>>> +------------
>>>>> 1 file changed, 33 insertions(+), 28 deletions(-)
>>>>>
>>>>> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c b/drivers/phy/
>>>>> qualcomm/phy-qcom-qmp-ufs.c
>>>>> index 636dc3dc3ea8..12dad28cc1bd 100644
>>>>> --- a/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c
>>>>> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c
>>>>> @@ -1799,38 +1799,11 @@ static int qmp_ufs_com_exit(struct qmp_ufs
>>>>> *qmp)
>>>>> static int qmp_ufs_power_on(struct phy *phy)
>>>>> {
>>>>> struct qmp_ufs *qmp = phy_get_drvdata(phy);
>>>>> - const struct qmp_phy_cfg *cfg = qmp->cfg;
>>>>> int ret;
>>>>> dev_vdbg(qmp->dev, "Initializing QMP phy\n");
>>>>>
>>>>> - if (cfg->no_pcs_sw_reset) {
>>>>> - /*
>>>>> - * Get UFS reset, which is delayed until now to avoid a
>>>>> - * circular dependency where UFS needs its PHY, but
>>>>> the PHY
>>>>> - * needs this UFS reset.
>>>>> - */
>>>>> - if (!qmp->ufs_reset) {
>>>>> - qmp->ufs_reset =
>>>>> - devm_reset_control_get_exclusive(qmp-
>>>>> >dev,
>>>>> -
>>>>> "ufsphy");
>>>>> -
>>>>> - if (IS_ERR(qmp->ufs_reset)) {
>>>>> - ret = PTR_ERR(qmp->ufs_reset);
>>>>> - dev_err(qmp->dev,
>>>>> - "failed to get UFS reset: %d\n",
>>>>> - ret);
>>>>> -
>>>>> - qmp->ufs_reset = NULL;
>>>>> - return ret;
>>>>> - }
>>>>> - }
>>>>> - }
>>>>> -
>>>>> ret = qmp_ufs_com_init(qmp);
>>>>> - if (ret)
>>>>> - return ret;
>>>>> -
>>>>> - return 0;
>>>>> + return ret;
>>>>> }
>>>>>
>>>>> static int qmp_ufs_phy_calibrate(struct phy *phy)
>>>>> @@ -2088,6 +2061,34 @@ static int qmp_ufs_parse_dt(struct qmp_ufs
>>>>> *qmp)
>>>>> return 0;
>>>>> }
>>>>>
>>>>> +static int qmp_ufs_get_phy_reset(struct qmp_ufs *qmp)
>>>>> +{
>>>>> + const struct qmp_phy_cfg *cfg = qmp->cfg;
>>>>> + int ret;
>>>>> +
>>>>> + if (!cfg->no_pcs_sw_reset)
>>>>> + return 0;
>>>>> +
>>>>> + /*
>>>>> + * Get UFS reset, which is delayed until now to avoid a
>>>>> + * circular dependency where UFS needs its PHY, but the PHY
>>>>> + * needs this UFS reset.
>>>>> + */
>>>>> + if (!qmp->ufs_reset) {
>>>>> + qmp->ufs_reset =
>>>>> + devm_reset_control_get_exclusive(qmp->dev, "ufsphy");
>>>>
>>>> Strange indentation.
>>>>
>>>>> +
>>>>> + if (IS_ERR(qmp->ufs_reset)) {
>>>>> + ret = PTR_ERR(qmp->ufs_reset);
>>>>> + dev_err(qmp->dev, "failed to get PHY reset:
>>>>> %d\n", ret);
>>>>> + qmp->ufs_reset = NULL;
>>>>> + return ret;
>>>>> + }
>>>>> + }
>>>>> +
>>>>> + return 0;
>>>>> +}
>>>>> +
>>>>> static int qmp_ufs_probe(struct platform_device *pdev)
>>>>> {
>>>>> struct device *dev = &pdev->dev;
>>>>> @@ -2114,6 +2115,10 @@ static int qmp_ufs_probe(struct
>>>>> platform_device *pdev)
>>>>> if (ret)
>>>>> return ret;
>>>>>
>>>>> + ret = qmp_ufs_get_phy_reset(qmp);
>>>>> + if (ret)
>>>>> + return ret;
>>>>> +
>>>>> /* Check for legacy binding with child node. */
>>>>> np = of_get_next_available_child(dev->of_node, NULL);
>>>>> if (np) {
>>>>> --
>>>>> 2.48.1
>>>>>
>>>>
>>>
>>
>>
>
--
With best wishes
Dmitry
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-04-15 9:32 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
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 [this message]
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=c2ec6b7c-421d-43c3-8c0a-de4f7bdd867c@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bjorande@quicinc.com \
--cc=bvanassche@acm.org \
--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_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