From: Nitin Rawat <quic_nitirawa@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.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 0/9] Refactor phy powerup sequence
Date: Fri, 11 Apr 2025 16:05:48 +0530 [thread overview]
Message-ID: <57fac14e-e4fe-41a3-a5f9-01447f2ff62d@quicinc.com> (raw)
In-Reply-To: <zzfffzclcftivaaffri6ucupyh3u5dfy7uctgw6xgid2vucusx@x542fel3qkeg>
On 4/11/2025 1:35 AM, Dmitry Baryshkov wrote:
> On Thu, Apr 10, 2025 at 02:30:53PM +0530, Nitin Rawat wrote:
>> In Current code regulators enable, clks enable, calibrating UFS PHY,
>> start_serdes and polling PCS_ready_status are part of phy_power_on.
>>
>> UFS PHY registers are retained after power collapse, meaning calibrating
>> UFS PHY, start_serdes and polling PCS_ready_status can be done only when
>> hba is powered_on, and not needed every time when phy_power_on is called
>> during resume. Hence keep the code which enables PHY's regulators & clks
>> in phy_power_on and move the rest steps into phy_calibrate function.
>>
>> Since phy_power_on is separated out from phy calibrate, make separate calls
>> to phy_power_on and phy_calibrate calls from ufs qcom driver.
>>
>> Also for better power saving, remove the phy_power_on/off calls from
>> resume/suspend path and put them to ufs_qcom_setup_clocks, so that
>> PHY's regulators & clks can be turned on/off along with UFS's clocks.
>
> Please add an explicit note that patch1 is a requirement for the rest of
> the PHY patches. It might make sense to merge it through the PHY tree
> too (or to use an immutable branch).
>
Hi Dmitry,
Thanks for the suggestion. Sure I would mention this in the cover letter
when I post next patchset.
Thanks,
Nitin
>>
>> This patch series is tested on SM8550 QRD, SM8650 MTP , SM8750 MTP.
>>
>
prev parent reply other threads:[~2025-04-11 10:36 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
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 [this message]
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=57fac14e-e4fe-41a3-a5f9-01447f2ff62d@quicinc.com \
--to=quic_nitirawa@quicinc.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bjorande@quicinc.com \
--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_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