linux-kernel - Re: [PATCH] arm64: dts: qcom: sc7280: Describe the first PCIe controller and PHY

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: <fd08bf8f-9aa7-4bd8-8618-5e4247180f2c@kernel.org>
Date: Tue, 12 Aug 2025 16:53:01 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
 Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
 cros-qcom-dts-watchers@...omium.org, Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.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] arm64: dts: qcom: sc7280: Describe the first PCIe
 controller and PHY

On 12/08/2025 16:45, Dmitry Baryshkov wrote:
> On Tue, Aug 12, 2025 at 01:34:44PM +0200, Konrad Dybcio wrote:
>> On 8/12/25 5:16 AM, Bjorn Andersson wrote:
>>> Only one PCIe controller has been described so far, but the SC7280 has
>>> two controllers/phys. Describe the second one as well.
>>>
>>> Signed-off-by: Bjorn Andersson <bjorn.andersson@....qualcomm.com>
>>> ---
>>
>> [...]
>>
>>> +		pcie0_phy: phy@...6000 {
>>> +			compatible = "qcom,sm8250-qmp-gen3x1-pcie-phy";
>>
>> :(
>>
>> BTW I noticed that Krishna also tackled the same issue just yesterday
>> on the internal mailing list.. would you prefer him to take it, or do
>> you want me to review this patch instead?
> 
> That means one thing: a lot of our engineers don't need to post patches
> to the internal ML.


Or waiting between v1 and v2 could be shortened to less than 2 years.

Best regards,
Krzysztof