linux-kernel - Re: [PATCH v3 3/3] arm64: qcom: sc7280: Move phy, perst to root port node

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: <ba107a41-5520-47fa-9943-6e33946f50b1@kernel.org>
Date: Mon, 2 Jun 2025 15:01:48 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
 Rob Herring <robh@...nel.org>,
 Krishna Chaitanya Chundru <krishna.chundru@....qualcomm.com>
Cc: Lorenzo Pieralisi <lpieralisi@...nel.org>,
 Krzysztof Wilczyński <kw@...ux.com>,
 Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
 Bjorn Helgaas <bhelgaas@...gle.com>, Krzysztof Kozlowski
 <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
 Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, cros-qcom-dts-watchers@...omium.org,
 linux-arm-msm@...r.kernel.org, linux-pci@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 quic_vbadigan@...cinc.com, quic_mrana@...cinc.com
Subject: Re: [PATCH v3 3/3] arm64: qcom: sc7280: Move phy, perst to root port
 node

On 08/05/2025 16:26, Konrad Dybcio wrote:
> On 4/23/25 5:37 PM, Rob Herring wrote:
>> On Sat, Apr 19, 2025 at 10:49:26AM +0530, Krishna Chaitanya Chundru wrote:
>>> There are many places we agreed to move the wake and perst gpio's
>>> and phy etc to the pcie root port node instead of bridge node[1].
>>>
>>> So move the phy, phy-names, wake-gpio's in the root port.
>>> There is already reset-gpio defined for PERST# in pci-bus-common.yaml,
>>> start using that property instead of perst-gpio.
>>
>> Moving the properties will break existing kernels. If that doesn't 
>> matter for these platforms, say so in the commit msg.
> 
> I don't think we generally guarantee *forward* dt compatibility though, no?
We do not guarantee, comment was not about this, but we expect. This DTS
is supposed and is used by other projects. There was entire complain
last DT BoF about kernel breaking DTS users all the time.

Best regards,
Krzysztof