Re: [PATCH v2 2/5] arm64: dts: qcom: Add AYN QCS8550 Common

[Krzysztof Kozlowski <krzk@kernel.org>]

On 13/03/2026 18:34, Aaron Kling wrote:
>>
>> We do not write DTS to fulfill broken Android boot process.
> 
> I have been trying rather hard to find a reasonable compromise between
> mainline requirements and a normal Android use case, something I can
> actually ship to normal users. This seemed fairly reasonable to me,
> since it can generate standalone dtb's transparently. But if my use
> case can never meet submission requirements, then why am I even here,
> getting shamed for working on Android? If I have to fork the
> device-tree anyways to fit my requirements, then there's no reason for
> me to put the time and effort in to submitting something I can't use.
> I'd be better off just keeping everything out of tree as googles
> kernel-platform supports. And never look at mainline qcom again.

In one of the previous threads there were ideas how to solve it, e.g.
chain loading bootloader or ditching ABL. The true problem is here
Google and its Android policy which hinders any real world upstream
usage. The solution is to Android to change (yeah, good luck :) ) or
ditch Android in favor of other modern solutions. I think you want to
have cookie and eat cookie...

Best regards,
Krzysztof