linux-kernel - Re: [PATCH 4/5] arm64: dts: qcom: ipq5018: add MDIO buses

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:
 <DS7PR19MB88838E2C42CF1EF29AD266BB9D64A@DS7PR19MB8883.namprd19.prod.outlook.com>
Date: Tue, 27 May 2025 15:23:42 +0400
From: George Moussalem <george.moussalem@...look.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
 Russell King <linux@...linux.org.uk>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Florian Fainelli <f.fainelli@...il.com>,
 Philipp Zabel <p.zabel@...gutronix.de>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>,
 Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>
Cc: netdev@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
 linux-clk@...r.kernel.org
Subject: Re: [PATCH 4/5] arm64: dts: qcom: ipq5018: add MDIO buses

Hi Konrad

On 5/27/25 15:07, Konrad Dybcio wrote:
> On 5/25/25 7:56 PM, George Moussalem via B4 Relay wrote:
>> From: George Moussalem <george.moussalem@...look.com>
>>
>> IPQ5018 contains two mdio buses of which one bus is used to control the
>> SoC's internal GE PHY, while the other bus is connected to external PHYs
>> or switches.
>>
>> There's already support for IPQ5018 in the mdio-ipq4019 driver, so let's
>> simply add the mdio nodes for them.
>>
>> Signed-off-by: George Moussalem <george.moussalem@...look.com>
>> ---
>>   arch/arm64/boot/dts/qcom/ipq5018.dtsi | 24 ++++++++++++++++++++++++
>>   1 file changed, 24 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/ipq5018.dtsi b/arch/arm64/boot/dts/qcom/ipq5018.dtsi
>> index 130360014c5e14c778e348d37e601f60325b0b14..03ebc3e305b267c98a034c41ce47a39269afce75 100644
>> --- a/arch/arm64/boot/dts/qcom/ipq5018.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/ipq5018.dtsi
>> @@ -182,6 +182,30 @@ pcie0_phy: phy@...00 {
>>   			status = "disabled";
>>   		};
>>   
>> +		mdio0: mdio@...00 {
>> +			compatible = "qcom,ipq5018-mdio";
>> +			reg = <0x00088000 0x64>;
>> +			#address-cells = <1>;
>> +			#size-cells = <0>;
>> +
>> +			clocks = <&gcc GCC_MDIO0_AHB_CLK>;
>> +			clock-names = "gcc_mdio_ahb_clk";
> 
> I see there's resets named GCC_MDIO[01]_BCR - are they related to
> these hosts?

Yes, they are specific to these mdio buses, yet not required for 
operation, just like ipq8074 and ipq6018 don't list this reset in their 
respective nodes in the dtsi.

> 
> fwiw the addressses look good
> 
> Konrad

Best regards,
George