linux-kernel - Re: [PATCH 2/2] arm64: dts: qcom: sc8280xp-crd: Fix naming of regulators

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8b8c35ba-e495-6363-e8fd-65e60bc6e879@linaro.org>
Date:   Tue, 20 Jun 2023 22:42:12 +0200
From:   Konrad Dybcio <konrad.dybcio@...aro.org>
To:     Bjorn Andersson <quic_bjorande@...cinc.com>,
        Bjorn Andersson <andersson@...nel.org>,
        Johan Hovold <johan+linaro@...nel.org>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sc8280xp-crd: Fix naming of
 regulators

On 20.06.2023 22:39, Bjorn Andersson wrote:
> The external regulators in the CRD seems to have inherited their names
> from the X13s DeviceTree, correct them.
> 
> Signed-off-by: Bjorn Andersson <quic_bjorande@...cinc.com>
> ---
Please also update the node names to match.

Konrad
>  arch/arm64/boot/dts/qcom/sc8280xp-crd.dts | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-crd.dts b/arch/arm64/boot/dts/qcom/sc8280xp-crd.dts
> index b21b41a066b6..678cdf253f2e 100644
> --- a/arch/arm64/boot/dts/qcom/sc8280xp-crd.dts
> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-crd.dts
> @@ -133,7 +133,7 @@ vreg_edp_3p3: regulator-edp-3p3 {
>  	vreg_edp_bl: regulator-edp-bl {
>  		compatible = "regulator-fixed";
>  
> -		regulator-name = "VBL9";
> +		regulator-name = "VREG_EDP_BL";
>  		regulator-min-microvolt = <3600000>;
>  		regulator-max-microvolt = <3600000>;
>  
> @@ -149,7 +149,7 @@ vreg_edp_bl: regulator-edp-bl {
>  	vreg_nvme: regulator-nvme {
>  		compatible = "regulator-fixed";
>  
> -		regulator-name = "VCC3_SSD";
> +		regulator-name = "VREG_NVME_3P3";
>  		regulator-min-microvolt = <3300000>;
>  		regulator-max-microvolt = <3300000>;
>  
> @@ -163,7 +163,7 @@ vreg_nvme: regulator-nvme {
>  	vreg_misc_3p3: regulator-misc-3p3 {
>  		compatible = "regulator-fixed";
>  
> -		regulator-name = "VCC3B";
> +		regulator-name = "VREG_MISC_3P3";
>  		regulator-min-microvolt = <3300000>;
>  		regulator-max-microvolt = <3300000>;
>  
> @@ -180,7 +180,7 @@ vreg_misc_3p3: regulator-misc-3p3 {
>  	vreg_wlan: regulator-wlan {
>  		compatible = "regulator-fixed";
>  
> -		regulator-name = "VCC_WLAN_3R9";
> +		regulator-name = "VPH_PWR_WLAN";
>  		regulator-min-microvolt = <3900000>;
>  		regulator-max-microvolt = <3900000>;
>  
> @@ -196,7 +196,7 @@ vreg_wlan: regulator-wlan {
>  	vreg_wwan: regulator-wwan {
>  		compatible = "regulator-fixed";
>  
> -		regulator-name = "VCC3B_WAN";
> +		regulator-name = "SDX_VPH_PWR";
>  		regulator-min-microvolt = <3300000>;
>  		regulator-max-microvolt = <3300000>;
>