diff options
Diffstat (limited to 'target/linux/brcm2708/patches-4.4/0464-BCM270X-Connect-V3D-to-its-power-domain.patch')
| -rw-r--r-- | target/linux/brcm2708/patches-4.4/0464-BCM270X-Connect-V3D-to-its-power-domain.patch | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/target/linux/brcm2708/patches-4.4/0464-BCM270X-Connect-V3D-to-its-power-domain.patch b/target/linux/brcm2708/patches-4.4/0464-BCM270X-Connect-V3D-to-its-power-domain.patch deleted file mode 100644 index 28784beaa0..0000000000 --- a/target/linux/brcm2708/patches-4.4/0464-BCM270X-Connect-V3D-to-its-power-domain.patch +++ /dev/null @@ -1,23 +0,0 @@ -From 788b6642156c9128a640bb1cc7d14625a0ab6caa Mon Sep 17 00:00:00 2001 -From: Eric Anholt <eric@anholt.net> -Date: Fri, 12 Aug 2016 10:15:34 -0700 -Subject: [PATCH] BCM270X: Connect V3D to its power domain. - -We were doing this with manual firmware calls before, but to backport -runtime PM we want to be using a proper power domain. - -Signed-off-by: Eric Anholt <eric@anholt.net> ---- - arch/arm/boot/dts/bcm2708_common.dtsi | 1 + - 1 file changed, 1 insertion(+) - ---- a/arch/arm/boot/dts/bcm2708_common.dtsi -+++ b/arch/arm/boot/dts/bcm2708_common.dtsi -@@ -366,6 +366,7 @@ - v3d: v3d@7ec00000 { - compatible = "brcm,vc4-v3d"; - reg = <0x7ec00000 0x1000>; -+ power-domains = <&power RPI_POWER_DOMAIN_V3D>; - status = "disabled"; - }; - |