From: Nitin Rawat <quic_nitirawa@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: <vkoul@kernel.org>, <kishon@kernel.org>, <mani@kernel.org>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-phy@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 2/2] phy: qcom-qmp-ufs: Add regulator loads for SM8650 and SM8750
Date: Wed, 20 Aug 2025 12:07:57 +0530 [thread overview]
Message-ID: <b453b8ff-a460-4ccd-9019-aed746a7d52d@quicinc.com> (raw)
In-Reply-To: <ger4kizeltjwalfuwu4dpfjiskrv2okgo5c7d6n3pb24yaxgfo@nkcndblyx3il>
On 8/20/2025 6:19 AM, Dmitry Baryshkov wrote:
> On Wed, Aug 20, 2025 at 03:58:26AM +0530, Nitin Rawat wrote:
>> Add regulator load voting support for SM8650 and SM8750 platforms by
>> introducing dedicated regulator bulk data arrays with their load
>> values.
>>
>> The load requirements are:
>> - SM8650: vdda-phy (205mA), vdda-pll (17.5mA)
>> - SM8750: vdda-phy (213mA), vdda-pll (18.3mA)
>>
>> This ensures stable operation and proper power management for these
>> platforms where regulators are shared between the QMP USB PHY and
>> other IP blocks by setting appropriate regulator load currents during PHY
>> operations.
>>
>> Configurations without specific load requirements will continue to work
>> unchanged, as init_load_uA remains zero-initialized when .init_load_uA
>> is not provided.
>
> Can we please get configuration for the rest of the platforms?
Hi Dmitry,
If you're okay with it, can I merge the configuration for the remaining
platforms in the next patch series after I complete testing on all
remaining platforms.
Regards,
Nitin
>
>>
>> Signed-off-by: Nitin Rawat <quic_nitirawa@quicinc.com>
>> ---
>> drivers/phy/qualcomm/phy-qcom-qmp-ufs.c | 19 +++++++++++++++----
>> 1 file changed, 15 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c b/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c
>> index aaa88ca0ef07..1c3ce0fa6adf 100644
>> --- a/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c
>> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-ufs.c
>> @@ -1170,6 +1170,17 @@ static const struct regulator_bulk_data qmp_phy_vreg_l[] = {
>> { .supply = "vdda-pll" },
>> };
>>
>> +/* Regulator bulk data with load values for specific configurations */
>> +static const struct regulator_bulk_data sm8650_ufsphy_vreg_l[] = {
>> + { .supply = "vdda-phy", .init_load_uA = 205000 },
>> + { .supply = "vdda-pll", .init_load_uA = 17500 },
>> +};
>> +
>> +static const struct regulator_bulk_data sm8750_ufsphy_vreg_l[] = {
>> + { .supply = "vdda-phy", .init_load_uA = 213000 },
>> + { .supply = "vdda-pll", .init_load_uA = 18300 },
>> +};
>> +
>> static const struct qmp_ufs_offsets qmp_ufs_offsets = {
>> .serdes = 0,
>> .pcs = 0xc00,
>> @@ -1638,8 +1649,8 @@ static const struct qmp_phy_cfg sm8650_ufsphy_cfg = {
>> .max_gear = UFS_HS_G5,
>> },
>>
>> - .vreg_list = qmp_phy_vreg_l,
>> - .num_vregs = ARRAY_SIZE(qmp_phy_vreg_l),
>> + .vreg_list = sm8650_ufsphy_vreg_l,
>> + .num_vregs = ARRAY_SIZE(sm8650_ufsphy_vreg_l),
>> .regs = ufsphy_v6_regs_layout,
>> };
>>
>> @@ -1676,8 +1687,8 @@ static const struct qmp_phy_cfg sm8750_ufsphy_cfg = {
>> .max_gear = UFS_HS_G5,
>> },
>>
>> - .vreg_list = qmp_phy_vreg_l,
>> - .num_vregs = ARRAY_SIZE(qmp_phy_vreg_l),
>> + .vreg_list = sm8750_ufsphy_vreg_l,
>> + .num_vregs = ARRAY_SIZE(sm8750_ufsphy_vreg_l),
>> .regs = ufsphy_v6_regs_layout,
>>
>> };
>> --
>> 2.48.1
>>
>
next prev parent reply other threads:[~2025-08-20 6:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 22:28 [PATCH V3 0/2] Add regulator load support for QMP UFS PHY Nitin Rawat
2025-08-19 22:28 ` [PATCH V3 1/2] phy: qcom-qmp-ufs: Add regulator load voting for UFS QMP PHY Nitin Rawat
2025-08-20 0:48 ` Dmitry Baryshkov
2025-08-22 8:40 ` Manivannan Sadhasivam
2025-08-19 22:28 ` [PATCH V3 2/2] phy: qcom-qmp-ufs: Add regulator loads for SM8650 and SM8750 Nitin Rawat
2025-08-20 0:49 ` Dmitry Baryshkov
2025-08-20 6:37 ` Nitin Rawat [this message]
2025-08-20 11:54 ` Dmitry Baryshkov
2025-08-21 16:02 ` Nitin Rawat
2025-08-21 19:39 ` Nitin Rawat
2025-08-22 9:19 ` Dmitry Baryshkov
2025-08-22 9:24 ` Nitin Rawat
2025-08-22 8:53 ` Manivannan Sadhasivam
2025-08-22 9:15 ` Dmitry Baryshkov
2025-08-22 9:23 ` Nitin Rawat
2025-08-22 10:56 ` Manivannan Sadhasivam
2025-08-22 11:39 ` Nitin Rawat
2025-08-22 8:51 ` Manivannan Sadhasivam
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=b453b8ff-a460-4ccd-9019-aed746a7d52d@quicinc.com \
--to=quic_nitirawa@quicinc.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mani@kernel.org \
--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®