aboutsummaryrefslogtreecommitdiffstats
path: root/include/linux/mfd
diff options
context:
space:
mode:
authorStefan Wahren <stefan.wahren@i2se.com>2022-06-25 13:36:15 +0200
committerLee Jones <lee.jones@linaro.org>2022-07-04 11:42:20 +0100
commitdf76234276e22136b2468825c18407fdfbb2076a (patch)
tree6c7c78a949e81915aed41b76c3f62d53555938d0 /include/linux/mfd
parentmfd: bcm2835-pm: Use 'reg-names' to get resources (diff)
downloadlinux-dev-df76234276e22136b2468825c18407fdfbb2076a.tar.xz
linux-dev-df76234276e22136b2468825c18407fdfbb2076a.zip
mfd: bcm2835-pm: Add support for BCM2711
In BCM2711 the new RPiVid ASB took over V3D. The old ASB is still present with the ISP and H264 bits, and V3D is in the same place in the new ASB as the old one. As per the devicetree bindings, BCM2711 will provide both the old and new ASB resources, so get both of them and pass them into 'bcm2835-power,' which will take care of selecting which one to use accordingly. Since the RPiVid ASB's resources were being provided prior to formalizing the bindings[1], also support the old DT files that didn't use 'reg-names.' [1] See: 7dbe8c62ceeb ("ARM: dts: Add minimal Raspberry Pi 4 support") Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com> Reviewed-by: Peter Robinson <pbrobinson@gmail.com> Acked-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: Lee Jones <lee.jones@linaro.org> Link: https://lore.kernel.org/r/20220625113619.15944-8-stefan.wahren@i2se.com
Diffstat (limited to 'include/linux/mfd')
-rw-r--r--include/linux/mfd/bcm2835-pm.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/mfd/bcm2835-pm.h b/include/linux/mfd/bcm2835-pm.h
index ed37dc40e82a..f70a810c55f7 100644
--- a/include/linux/mfd/bcm2835-pm.h
+++ b/include/linux/mfd/bcm2835-pm.h
@@ -9,6 +9,7 @@ struct bcm2835_pm {
struct device *dev;
void __iomem *base;
void __iomem *asb;
+ void __iomem *rpivid_asb;
};
#endif /* BCM2835_MFD_PM_H */