[PATCH v1 1/1] arm64: dts: qcom: hamoa: Move PCIe PERST and Wake GPIOs to port nodes

Krzysztof Kozlowski krzk at kernel.org
Thu Mar 19 06:12:03 PDT 2026


On 19/03/2026 06:28, Manivannan Sadhasivam wrote:
>>  If it only affects developers who generated DTs based
>> on 960609b22be5 for internal testing, we should say that so it's clear
>> that no end users will see any regressions or boot failures.
>>
> 
> Whoever have included commit 960609b22be5 in their kernel and using the above
> mentioned machines will see the failure. But looks like no one really tested
> v7.0-rcS on these machines as we haven't gotten any reports so far.
> 
>> Is there some way to verify that after this patch, none of the
>> generated DTBs are in this half-baked situation?  Some kind of
>> automated DTB checker?
> 
> I sent out a DT binding series [1] that was supposed to catch these issues
> during DTB validation phase, but unfortunately it got stuck in the review. I'll
> try to stir things up.
> 

What about other projects which use this DTB directly (e.g. OpenBSD)?
Are they considered broken with 960609b22be5?

Best regards,
Krzysztof



More information about the linux-phy mailing list