[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YmQhpsmiYJzR99LK@ripper>
Date: Sat, 23 Apr 2022 08:56:22 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Bhupesh Sharma <bhupesh.sharma@...aro.org>
Cc: linux-arm-msm@...r.kernel.org, linux-phy@...ts.infradead.org,
bhupesh.linux@...il.com, agross@...nel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
robh+dt@...nel.org, vkoul@...nel.org, Rob Herring <robh@...nel.org>
Subject: Re: [PATCH v3 2/4] dt-bindings: phy: qcom,qmp: Describe
'vdda-max-microamp' & 'vdda-pll-max-microamp' properties
On Mon 18 Apr 13:55 PDT 2022, Bhupesh Sharma wrote:
> Since a few boards based on QCoM qmp phy use the
> 'vdda-max-microamp' & 'vdda-pll-max-microamp' properties to
> describe the ufs phy nodes, add them to the dt-bindings doc as well.
>
> This fixes the following '$ make dtbs_check' warning(s):
>
> sm8350-microsoft-surface-duo2.dt.yaml: phy@...7000:
> 'vdda-max-microamp', 'vdda-pll-max-microamp' do not match any of
> the regexes: '^phy@[0-9a-f]+$', 'pinctrl-[0-9]+'
>
> Cc: Bjorn Andersson <bjorn.andersson@...aro.org>
> Cc: Vinod Koul <vkoul@...nel.org>
> Acked-by: Rob Herring <robh@...nel.org>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@...aro.org>
> ---
> Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> index c39ead81ecd7..411c79dbfa15 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,qmp-phy.yaml
> @@ -90,6 +90,14 @@ properties:
> minItems: 1
> maxItems: 3
>
> + vdda-max-microamp:
> + description:
> + Specifies max. load that can be drawn from phy supply.
> +
> + vdda-pll-max-microamp:
> + description:
> + Specifies max. load that can be drawn from pll supply.
It's not clear to me what an implementation would do with this
information. As expressed here it sounds like it's a property of the
specified regulator, so the driver should just request that information
from the regulator framework.
So let's wait with introducing such properties until we know.
Thanks,
Bjorn
> +
> vdda-phy-supply:
> description:
> Phandle to a regulator supply to PHY core block.
> --
> 2.35.1
>
Powered by blists - more mailing lists