diff options
| author | Maíra Canal <mcanal@igalia.com> | 2026-09-15 17:51:24 -0300 |
|---|---|---|
| committer | Maíra Canal <mcanal@igalia.com> | 2026-09-18 15:23:24 -0300 |
| commit | fb825a46e7982460bd620f5e6a71924c647f4280 (patch) | |
| tree | afef44cf872709a0030d13a23f7cd1668a278517 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 2e854d0fca8ce9682566826a0c81e8d53f37611d (diff) | |
| download | linux-fb825a46e7982460bd620f5e6a71924c647f4280.tar.gz linux-fb825a46e7982460bd620f5e6a71924c647f4280.zip | |
drm/vc4: Drop the undocumented brcm,vc4-v3d compatible
"brcm,vc4-v3d" is the compatible string V3D support originally shipped
with in commit d3f5168a0810 ("drm/vc4: Bind and initialize the V3D
engine."). Commit 90d7116061f8 ("drm/vc4: Recognize a more specific
compatible string for V3D.") added "brcm,bcm2835-v3d" in v4.6 and kept
the original one around, because the Raspberry Pi firmware was shipping
device trees that used it.
That string was never part of the binding: the documentation added in
commit 4653f22e9ab0 ("dt-bindings: Add binding docs for V3D.") describes
only "brcm,bcm2835-v3d", and no upstream device tree has ever used
"brcm,vc4-v3d": the first in-tree V3D node, from commit 49ac67e0c39c
("ARM: bcm2835: Add VC4 to the device tree."), already carried the
specific name. The firmware device trees the compatible was kept for
predate v4.6, released in 2016.
Drop it from both match tables.
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://patch.msgid.link/20260915-vc4-reset-control-v2-1-cb3a25b07822@igalia.com
Signed-off-by: Maíra Canal <mcanal@igalia.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions