diff options
Diffstat (limited to 'target/linux/brcm2708/patches-4.19/950-0643-overlays-dpi18-and-dpi24-vc4-compatibility.patch')
| -rw-r--r-- | target/linux/brcm2708/patches-4.19/950-0643-overlays-dpi18-and-dpi24-vc4-compatibility.patch | 52 |
1 files changed, 52 insertions, 0 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0643-overlays-dpi18-and-dpi24-vc4-compatibility.patch b/target/linux/brcm2708/patches-4.19/950-0643-overlays-dpi18-and-dpi24-vc4-compatibility.patch new file mode 100644 index 0000000000..0b3e8ec079 --- /dev/null +++ b/target/linux/brcm2708/patches-4.19/950-0643-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 { |