Re: [GIT PULL] ~RISC-V~Starfive devicetrees fixes for v7.0-rc6

[Krzysztof Kozlowski <krzk@kernel.org>]

On 27/03/2026 10:45, Conor Dooley wrote:
> 
>> The commit touches only DTS, not DTSO, so how can you claim that a DTS
>> file change breaks some completely other board (Raspberry)?
>>
>> This DTS file is nowhere included (and should not be).
>>
>> Of course maybe the true question would be why anyone described a hat as
>> DTS file...
>>
>>>
>>> E. we know that by chance you have found a base board that ignores the 
>>> standard.
>>>
>>> Your patch 4cce8b2503ab5 made my standard compliant baseboard unusable. 
>>
>> DTS of some board is a final product, so it cannot be applied to a
>> baseboard, that's pretty messed DTS tree...
> 
> The cm-lite is a rpi compute module compatible device, the base boards
> don't have any devices on them in a lot of cases and just provide
> physical connectors, so there's no point having a distinct dts for every
> baseboard of that type.
> https://www.waveshare.com/product/cm4-io-base-a.htm
> 
I saw the picture and it looked like it should never be a DTS, because
it is not usable on its own. You cannot run it.

Things which you cannot run, are not DTS. There is only one known to me
exception for SoM being a DTS - Renesas SMARC something - because Geert
explained to me that you can run that SoM without carrier board.

And because this was a DTS commit, then adding broken-cd because of
baseboard troubles is WRONG.

This is supposed to by DTSI included by carrier DTS or DTSO applied to
every carrier board.


Best regards,
Krzysztof