diff options
| author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-02-08 21:58:55 +0100 |
|---|---|---|
| committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-02-14 14:10:51 +0100 |
| commit | 7d7aa2fd924c27829ec25f825481554dd81bce97 (patch) | |
| tree | 658b87b89331670266163e522ea5fb52535633cb /target/linux/bcm27xx/patches-4.19/950-0613-overlays-dpi18-and-dpi24-vc4-compatibility.patch | |
| parent | e7bfda2c243e66a75ff966ba04c28b1590b5d24c (diff) | |
| download | upstream-7d7aa2fd924c27829ec25f825481554dd81bce97.tar.gz upstream-7d7aa2fd924c27829ec25f825481554dd81bce97.tar.bz2 upstream-7d7aa2fd924c27829ec25f825481554dd81bce97.zip | |
brcm2708: rename target to bcm27xx
This change makes the names of Broadcom targets consistent by using
the common notation based on SoC/CPU ID (which is used internally
anyway), bcmXXXX instead of brcmXXXX.
This is even used for target TITLE in make menuconfig already,
only the short target name used brcm so far.
Despite, since subtargets range from bcm2708 to bcm2711, it seems
appropriate to use bcm27xx instead of bcm2708 (again, as already done
for BOARDNAME).
This also renames the packages brcm2708-userland and brcm2708-gpu-fw.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>
Diffstat (limited to 'target/linux/bcm27xx/patches-4.19/950-0613-overlays-dpi18-and-dpi24-vc4-compatibility.patch')
| -rw-r--r-- | target/linux/bcm27xx/patches-4.19/950-0613-overlays-dpi18-and-dpi24-vc4-compatibility.patch | 52 |
1 files changed, 52 insertions, 0 deletions
diff --git a/target/linux/bcm27xx/patches-4.19/950-0613-overlays-dpi18-and-dpi24-vc4-compatibility.patch b/target/linux/bcm27xx/patches-4.19/950-0613-overlays-dpi18-and-dpi24-vc4-compatibility.patch new file mode 100644 index 0000000000..0b3e8ec079 --- /dev/null +++ b/target/linux/bcm27xx/patches-4.19/950-0613-overlays-dpi18-and-dpi24-vc4-compatibility.patch @@ -0,0 +1,52 @@ +From a5e0d604116189331d5608c9d128f37df17db2e3 Mon Sep 17 00:00:00 2001 +From: Phil Elwell <phil@raspberrypi.org> +Date: Tue, 16 Jul 2019 15:24:12 +0100 +Subject: [PATCH] overlays: dpi18 and dpi24 vc4 compatibility + +The dpi overlays use the fb device tree node as a place to hang the +necessary pinctrl changes. With one of the VC4 overlays loaded, the +fb node is disabled so the changes have no effect. + +Modify the overlays to also use the vc4 node, to cover both use +cases. + +Signed-off-by: Phil Elwell <phil@raspberrypi.org> +--- + arch/arm/boot/dts/overlays/dpi18-overlay.dts | 8 ++++++++ + arch/arm/boot/dts/overlays/dpi24-overlay.dts | 8 ++++++++ + 2 files changed, 16 insertions(+) + +--- a/arch/arm/boot/dts/overlays/dpi18-overlay.dts ++++ b/arch/arm/boot/dts/overlays/dpi18-overlay.dts +@@ -17,6 +17,14 @@ + }; + + fragment@1 { ++ target = <&vc4>; ++ __overlay__ { ++ pinctrl-names = "default"; ++ pinctrl-0 = <&dpi18_pins>; ++ }; ++ }; ++ ++ fragment@2 { + target = <&gpio>; + __overlay__ { + dpi18_pins: dpi18_pins { +--- a/arch/arm/boot/dts/overlays/dpi24-overlay.dts ++++ b/arch/arm/boot/dts/overlays/dpi24-overlay.dts +@@ -17,6 +17,14 @@ + }; + + fragment@1 { ++ target = <&vc4>; ++ __overlay__ { ++ pinctrl-names = "default"; ++ pinctrl-0 = <&dpi24_pins>; ++ }; ++ }; ++ ++ fragment@2 { + target = <&gpio>; + __overlay__ { + dpi24_pins: dpi24_pins { |