linux-kernel - Re: [PATCH v11 3/4] arm64: dts: qcom: qcs615-ride: Fix USB PHY label reference

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: <753fc364-3b32-496d-89f8-d9330d980f45@gmail.com>
Date: Wed, 14 Jan 2026 10:53:29 +0530
From: tessolveupstream@...il.com
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>, andersson@...nel.org,
 konradybcio@...nel.org
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v11 3/4] arm64: dts: qcom: qcs615-ride: Fix USB PHY label
 reference



On 09-01-2026 15:29, Konrad Dybcio wrote:
> On 1/9/26 10:52 AM, Sudarshan Shetty wrote:
>> Update the USB high-speed PHY label from 'usb_1_hsphy' to
>> 'usb_hsphy_1' to maintain consistency with the naming
>> convention used in talos.dtsi, where the second PHY is
>> labeled 'usb_hsphy_2'.
>>
>> No functional changes, only label renaming.
>>
>> Signed-off-by: Sudarshan Shetty <tessolveupstream@...il.com>
>> ---
>>  arch/arm64/boot/dts/qcom/qcs615-ride.dts | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs615-ride.dts b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>> index be67eb173046..0ca6b50a6de1 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>> +++ b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>> @@ -609,7 +609,7 @@ bluetooth {
>>  	};
>>  };
>>  
>> -&usb_1_hsphy {
>> +&usb_hsphy_1 {
>>  	vdd-supply = <&vreg_l5a>;
>>  	vdda-pll-supply = <&vreg_l12a>;
>>  	vdda-phy-dpdm-supply = <&vreg_l13a>;
> 
> This must be squashed with patch 2, otherwise patch 2 is going to
> cause a build failure which must not happen at any point in the
> git history (to make bisecting possible)
> 

Okay, I will squash these changes with patch 2 in the next patch 
series.
> Konrad