From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Nitin Rawat <quic_nitirawa@quicinc.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: Fri, 22 Aug 2025 12:19:11 +0300 [thread overview]
Message-ID: <8aa65fdc-d5a1-4a81-bcc1-8d953fa0ffa8@oss.qualcomm.com> (raw)
In-Reply-To: <9a38ec05-f7ab-4241-ba47-0d514b79e808@quicinc.com>
On 21/08/2025 19:02, Nitin Rawat wrote:
>
>
> On 8/20/2025 5:24 PM, Dmitry Baryshkov wrote:
>> On Wed, Aug 20, 2025 at 12:07:57PM +0530, Nitin Rawat wrote:
>>>
>>>
>>> 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.
>>
>> You don't need to test, finding MSM8996 or 98 might be troublesome. Just
>> fill in the values from the hardware documentation.
>
> Hi Dmitry,
>
> While implementing changes for all remaining platform, I noticed that
> the "regulator-allow-set-load" property is defined only for SM8750 and
> SM8850 within the PMIC PHY and PLL device tree nodes which means that
> even if the UFS PHY driver is updated to vote for this configuration on
> other platforms, it will have no impact.
If I remember correctly, on other platforms we don't allow setting the
load exactly because consumers were not voting on the current/power
requirements.
>
> Should I still proceed with applying the change across all platform, or
> limit it to just the SM8750 and SM8850 drivers? What’s your recommendation?
I think, we should proceed, then once all PHYs get those votes we can
enable load toggling on those platforms too.
>
> ===========================================================================
> // Device tree:
> vreg_l1j_0p91: ldo1 {
> regulator-name = "vreg_l1j_0p91";
> regulator-min-microvolt = <880000>;
> regulator-max-microvolt = <920000>;
> regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> regulator-allow-set-load;
> regulator-allowed-modes = <RPMH_REGULATOR_MODE_LPM
> RPMH_REGULATOR_MODE_HPM>;
> };
>
> ===========================================================================
> drivers/regulator/of_regulator.c
>
>
> if (of_property_read_bool(np, "regulator-allow-set-load"))
> constraints->valid_ops_mask |= REGULATOR_CHANGE_DRMS;
>
> ===========================================================================
> //drivers/regulator/core.c
> static int drms_uA_update(struct regulator_dev *rdev)
> {
> ...
> if (!regulator_ops_is_valid(rdev, REGULATOR_CHANGE_DRMS)) {
> rdev_dbg(rdev, "DRMS operation not allowed\n");
> return 0;
> }
> ...
> }
>
>
> Regards,
> Nitin
>
>
>
>
>>
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2025-08-22 9:19 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
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 [this message]
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=8aa65fdc-d5a1-4a81-bcc1-8d953fa0ffa8@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=andersson@kernel.org \
--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=quic_nitirawa@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®