Re: [PATCH v3 2/2] arm64: dts: broadcom: bcm2712-d-rpi-5-b: add compatible

[Stefan Wahren <wahrenst@gmx.net>]

Hi Gregor,

drop Eric and add Peter.

Am 05.08.26 um 09:27 schrieb Gregor Herburger:
> On Tue, Aug 04, 2026 at 04:57:09PM +0200, Stefan Wahren wrote:
>> Hi Gregor,
>>
>> sorry for my late reply.
>>
>> Am 04.08.26 um 15:13 schrieb Gregor Herburger:
>>> The bcm2712 found on the Raspberry Pi 5 is available in the d Stepping
>>> and in a c Stepping. There are two separate dts files. The
>>> bcm2712-rpi-5-b.dts for the c Stepping and the bcm2712-d-rpi-5-b.dts for
>>> the d Stepping. The d stepping does not set its own compatible/model
>>> string but uses "raspberrypi,5-model-b".
>> In case the SoC and not the board has a D stepping, why do just change the
>> board compatible without the SoC compatible like "brcm,bcm2712-d0"?
> You mean changing both compatible strings? Like this:
> 	compatible = "raspberrypi,5-model-b-d0", "brcm,bcm2712-d0";
I just want to mention that your explanation doesn't match to your 
changes. The first compatible represent the whole board (RPi 5) and the 
second one represent only the SoC (BCM2712). Since the SoC is different 
according your explanation, i would expect the SoC compatible needs to 
be changed. And in case the SoC changes, also the board won't be 
compatible anymore, correct?

Usually we try to avoid to model different SoC steppings in the device 
tree, because this introduce a lot of redundancy. But it seems that the 
differences are signifcant here.

In case this suggestion break something, this needs further explanation 
in the patch.

Best regards