The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: vkoul@kernel.org, kishon@kernel.org, mani@kernel.org,
	conor+dt@kernel.org, bvanassche@acm.org, andersson@kernel.org,
	neil.armstrong@linaro.org, dmitry.baryshkov@oss.qualcomm.com,
	konradybcio@kernel.org, krzk+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V1 2/4] arm64: dts: qcom: sm8750: add max-microamp for UFS PHY and PLL supplies
Date: Fri, 8 Aug 2025 10:58:20 +0200	[thread overview]
Message-ID: <9af71063-0629-4ccc-bc76-3fb588677bf4@oss.qualcomm.com> (raw)
In-Reply-To: <20250808-calm-boa-of-swiftness-a4a7ce@kuoka>

On 8/8/25 9:29 AM, Krzysztof Kozlowski wrote:
> On Wed, Aug 06, 2025 at 09:13:38PM +0530, Nitin Rawat wrote:
>> Add `vdda-phy-max-microamp` and `vdda-pll-max-microamp` properties to
>> the UFS PHY node in the device tree.
>>
>> These properties define the maximum current (in microamps) expected
>> from the PHY and PLL regulators. This allows the PHY driver to
>> configure regulator load accurately and ensure proper regulator
>> mode based on load requirements.
> 
> That's not the property of phy, but regulator.
> 
> Also reasoning is here incomplete - you just post downstream code. :/

The reason for this change is good, but perhaps not explained clearly

All of these values refer to the maximum current draw that needs to be
allocated on a shared voltage supply for this peripheral (because the
supply's capabilities change depending on the maximum potential load
at any given time, which the regulator driver must be aware of)

This is a property of a regulator *consumer*, i.e. if we had a chain
of LEDs hanging off of this supply, we'd need to specify NUM_LEDS * 
MAX_CURR under the "led chain" device, to make sure that if the
aggregated current requirements go over a certain threshold (which is
unknown to Linux and hidden in RPMh fw), the regulator can be
reconfigured to allow for a higher current draw (likely at some
downgrade to efficiency)

Konrad

  reply	other threads:[~2025-08-08  8:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 15:43 [PATCH V1 0/4] Add support to configure regulator load for UFS QMP PHY Nitin Rawat
2025-08-06 15:43 ` [PATCH V1 1/4] dt-bindings: phy: Add max-microamp properties for PHY and PLL supplies Nitin Rawat
2025-08-08  7:28   ` Krzysztof Kozlowski
2025-08-11 15:20   ` Bjorn Andersson
2025-08-06 15:43 ` [PATCH V1 2/4] arm64: dts: qcom: sm8750: add max-microamp for UFS " Nitin Rawat
2025-08-08  7:29   ` Krzysztof Kozlowski
2025-08-08  8:58     ` Konrad Dybcio [this message]
2025-08-08  9:39       ` Krzysztof Kozlowski
2025-08-08 15:19         ` Nitin Rawat
2025-08-09 11:07           ` Manivannan Sadhasivam
2025-08-11 19:55             ` Nitin Rawat
2025-08-12 10:52               ` Dmitry Baryshkov
2025-08-12 11:38                 ` 回复: " yizhijiao2025
2025-08-13 20:47                 ` Nitin Rawat
2025-08-11 15:25   ` Bjorn Andersson
2025-08-06 15:43 ` [PATCH V1 3/4] arm64: dts: qcom: sm8650: " Nitin Rawat
2025-08-06 15:43 ` [PATCH V1 4/4] phy: qcom-qmp-ufs: read max-microamp values from device tree Nitin Rawat
2025-08-06 15:58   ` Konrad Dybcio
2025-08-06 16:51     ` Mark Brown
2025-08-07 13:06       ` Konrad Dybcio
2025-08-07 13:44         ` Mark Brown
2025-08-07 15:42           ` Nitin Rawat
2025-08-07 17:26             ` Mark Brown
2025-08-07 17:35               ` Nitin Rawat
2025-08-07 17:43                 ` Mark Brown
2025-08-07 17:56                   ` Nitin Rawat
2025-08-07 18:45                     ` Mark Brown
2025-08-07 20:45                       ` Nitin Rawat
2025-08-08  7:25                         ` Krzysztof Kozlowski
2025-08-07 17:43               ` Konrad Dybcio
2025-08-07 18:09                 ` Nitin Rawat
2025-08-07 19:09                 ` Mark Brown
2025-08-11 15:50                   ` Bjorn Andersson
2025-08-11 16:14                     ` Mark Brown
2025-08-11 19:48                     ` Nitin Rawat
2025-08-13 21:01                       ` Nitin Rawat
2025-08-08 12:33   ` Manivannan Sadhasivam
2025-08-09  7:30   ` Dmitry Baryshkov
2025-08-11 19:49     ` 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=9af71063-0629-4ccc-bc76-3fb588677bf4@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=kishon@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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=neil.armstrong@linaro.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