[PATCH 0/3] ARM: dts: bcm: Add support for Raspberry Pi 2 (2nd rev)

Stefan Wahren wahrenst at gmx.net
Tue Apr 22 09:51:57 PDT 2025


Am 21.04.25 um 17:07 schrieb Rob Herring (Arm):
> On Fri, 18 Apr 2025 16:33:04 +0200, Stefan Wahren wrote:
>> This series adds support for the Raspberry Pi 2 (2nd rev).
>>
>> Stefan Wahren (3):
>>    dt-bindings: arm: bcm2835: Add Raspberry Pi 2 (2nd rev)
>>    ARM: dts: bcm: Add support for Raspberry Pi 2 (2nd rev)
>>    arm64: dts: bcm: Add reference to RPi 2 (2nd rev)
>>
>>   .../devicetree/bindings/arm/bcm/bcm2835.yaml  |   1 +
>>   arch/arm/boot/dts/broadcom/Makefile           |   2 +
>>   .../arm/boot/dts/broadcom/bcm2837-rpi-2-b.dts | 130 ++++++++++++++++++
>>   arch/arm64/boot/dts/broadcom/Makefile         |   1 +
>>   .../boot/dts/broadcom/bcm2837-rpi-2-b.dts     |   2 +
>>   5 files changed, 136 insertions(+)
>>   create mode 100644 arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dts
>>   create mode 100644 arch/arm64/boot/dts/broadcom/bcm2837-rpi-2-b.dts
>>
>> --
>> 2.34.1
>>
>>
>>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
>
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
>
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
>
>    pip3 install dtschema --upgrade
>
>
> This patch series was applied (using b4) to base:
>   Base: attempting to guess base-commit...
>   Base: tags/next-20250417 (exact match)
>
> If this is not the correct base, please add 'base-commit' tag
> (or use b4 which does this automatically)
>
> New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/broadcom/' for 20250418143307.59235-1-wahrenst at gmx.net:
>
> arch/arm/boot/dts/broadcom/bcm958625-meraki-mx65w.dtb: usb at 2a000 (generic-ehci): Unevaluated properties are not allowed ('dma-coherent' was unexpected)
> 	from schema $id: http://devicetree.org/schemas/usb/generic-ehci.yaml#
this is not relevant here
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: soc (simple-bus): gpu: 'ranges' is a required property
> 	from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: soc (simple-bus): firmware: 'ranges' is a required property
> 	from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: soc (simple-bus): power: 'ranges' is a required property
> 	from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: /soc/cprman at 7e101000: failed to match any schema with compatible: ['brcm,bcm2835-cprman']
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: /soc/gpio at 7e200000: failed to match any schema with compatible: ['brcm,bcm2835-gpio']
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: /soc/i2s at 7e203000: failed to match any schema with compatible: ['brcm,bcm2835-i2s']
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: /soc/aux at 7e215000: failed to match any schema with compatible: ['brcm,bcm2835-aux']
> arch/arm/boot/dts/broadcom/bcm2837-rpi-2-b.dtb: /soc/interrupt-controller at 7e00b200: failed to match any schema with compatible: ['brcm,bcm2836-armctrl-ic']
AFAICS all of these comes from existing dtsi files. I will try to 
address some of them in a separate series as soon as my backlog is empty.

Best regards



More information about the linux-arm-kernel mailing list