Commit 131b820c authored by Krzysztof Kozlowski's avatar Krzysztof Kozlowski Committed by Bjorn Andersson

arm64: dts: qcom: sm6115p-j606f: correct UFS pad supply

The Qualcomm UFS phy switched from dedicated driver to QMP phy driver.
Eventually the old driver was removed in commit 02dca8c9 ("phy:
qcom: remove ufs qmp phy driver").  The original driver and its binding
used vddp-ref-clk regulator supply, but the new one did not and left the
supply unused.

The Qualcomm UFS phy bindings were also migrated to newer ones and
dropped support for vddp-ref-clk regulator in commit dc5cb635
("dt-bindings: phy: migrate QMP UFS PHY bindings to
qcom,sc8280xp-qmp-ufs-phy.yaml").

It turns out that this regulator, although with inaccurate name
vddp-ref-clk, is actually needed to provide supply for VDD_PX10 (or
similar, depending on the SoC) used by UFS controller.

Bring back handling of this supply by using more appropriate regulator -
UFS controller host supply.  This also fixes dtbs_check warning:

  sm6115p-lenovo-j606f.dtb: phy@4807000: 'vddp-ref-clk-supply' does not match any of the regexes: 'pinctrl-[0-9]+'
Signed-off-by: default avatarKrzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: default avatarKonrad Dybcio <konrad.dybcio@linaro.org>
Link: https://lore.kernel.org/r/20230905161920.252013-5-krzysztof.kozlowski@linaro.orgSigned-off-by: default avatarBjorn Andersson <andersson@kernel.org>
parent 69a9275a
...@@ -344,13 +344,13 @@ &ufs_mem_hc { ...@@ -344,13 +344,13 @@ &ufs_mem_hc {
vcc-max-microamp = <600000>; vcc-max-microamp = <600000>;
vccq2-supply = <&pm6125_l11>; vccq2-supply = <&pm6125_l11>;
vccq2-max-microamp = <600000>; vccq2-max-microamp = <600000>;
vdd-hba-supply = <&pm6125_l18>;
status = "okay"; status = "okay";
}; };
&ufs_mem_phy { &ufs_mem_phy {
vdda-phy-supply = <&pm6125_l4>; vdda-phy-supply = <&pm6125_l4>;
vdda-pll-supply = <&pm6125_l12>; vdda-pll-supply = <&pm6125_l12>;
vddp-ref-clk-supply = <&pm6125_l18>;
status = "okay"; status = "okay";
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment