[PATCH v5 0/3] drm/vc4: Fixup DT and DT binding issues from recent patchset
Rob Herring
robh at kernel.org
Mon Dec 1 04:59:34 PST 2025
On Fri, Dec 20, 2024 at 06:11:10PM +0000, Dave Stevenson wrote:
> I missed the DT errors from the recent patchset[1] (DT patches
> in linux-next via Florian, DRM bindings patches on dri-misc-next)
> as Rob's bot report got spam filtered, so this is a fixup set.
>
> Largely it was changes to number of interrupts or clocks in the
> bindings, so those are now covered.
>
> I've fixed up the missing "interrupt-controller" flags for 2711
> and 2712 whilst here.
I found this is still warning a year later, so I fixed up the commit
messages and applied.
The comments were a bit nitpicky for a v5 version IMO. However, you went
to the trouble of preparing 5 versions of the series and we spent our
time reviewing them, so why abandon them?
It would be nice if the Broadcom folks spent some effort fixing the
remaining DT warnings. I see little progress.
>
> I can't get my head around what is meant to happen with ranges:
> "soc at 107c000000: firmware: 'ranges' is a required property"
> The meaning seems obvious.
Adding "ranges" is probably not correct. Generally, 'firmware' is not
MMIO and should not be under an MMIO bus (i.e. simple-bus).
>
> However if I add it then I get:
> "firmware: '#address-cells', '#size-cells', 'dma-ranges', 'ranges' do
> not match any of the regexes: 'pinctrl-[0-9]+'
> from schema $id: http://devicetree.org/schemas/arm/bcm/raspberrypi,bcm2835-firmware.yaml#
If you add properties to the 'firmware' node, then you need to add those
properties to its schema.
>
> There's obviously some other flag I need to set in the bindings,
> but I can't work it out. We have similar errors for all the Pi
> platforms for one or more nodes.
> Please advise and I'll happily fix them all.
More information about the linux-arm-kernel
mailing list