Re: [PATCH v2 3/6] arm64: dts: qcom: lemans-evk: fix SerDes PHY regulator supplies

From: Bartosz Golaszewski

Date: Mon Aug 10 2026 - 07:18:21 EST


On Mon, 3 Aug 2026 21:27:59 +0200, Mohd Ayaan Anwar
<mohd.anwar@xxxxxxxxxxxxxxxx> said:
> The SerDes PHY nodes were configured with 'phy-supply = <&vreg_l5a>',
> which was incorrect on two counts: vreg_l5a is not a supply the PHY
> requires, and only one rail was described whereas the hardware needs
> two.
>
> The PHY requires vdda-0p9 (vreg_l4a) and vdda-1p2 (vreg_l1c). Replace
> the incorrect phy-supply with these two named properties on both the
> base EVK node and the IFP mezzanine overlay.
>
> Fixes: 71ee90ed1756 ("arm64: dts: qcom: lemans-evk: Enable 2.5G Ethernet interface")
> Signed-off-by: Mohd Ayaan Anwar <mohd.anwar@xxxxxxxxxxxxxxxx>
> ---
> arch/arm64/boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso | 3 ++-
> arch/arm64/boot/dts/qcom/lemans-evk.dts | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso b/arch/arm64/boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso
> index 6cfa0bc1440e91d32df0695ae4059050e4e20b56..8651c412d0288fcf2ab69fbfaed86f68fb2b4fc5 100644
> --- a/arch/arm64/boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso
> +++ b/arch/arm64/boot/dts/qcom/lemans-evk-ifp-mezzanine.dtso
> @@ -291,7 +291,8 @@ pcie@0,1 {
> };
>
> &serdes1 {
> - phy-supply = <&vreg_l5a>;
> + vdda-0p9-supply = <&vreg_l4a>;
> + vdda-1p2-supply = <&vreg_l1c>;
>
> status = "okay";
> };
> diff --git a/arch/arm64/boot/dts/qcom/lemans-evk.dts b/arch/arm64/boot/dts/qcom/lemans-evk.dts
> index 0c53640c42a65c62375e71f7ae79cbc834a05888..5c046b9bfb3cdec59cffc1dfdbf9f2a51dc9721b 100644
> --- a/arch/arm64/boot/dts/qcom/lemans-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/lemans-evk.dts
> @@ -978,7 +978,8 @@ &sdhc {
> };
>
> &serdes0 {
> - phy-supply = <&vreg_l5a>;
> + vdda-0p9-supply = <&vreg_l4a>;
> + vdda-1p2-supply = <&vreg_l1c>;
>
> status = "okay";
> };
>
> --
> 2.34.1
>
>

Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxxxxxxxx>
Tested-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxxxxxxxx>