summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/bcm2835-rpi-common.dtsi
diff options
context:
space:
mode:
authorMaxime Ripard <maxime@cerno.tech>2022-10-26 16:17:39 +0300
committerFlorian Fainelli <f.fainelli@gmail.com>2022-11-10 21:15:15 +0300
commit27ab05e1b7e5c5ec9b4f658e1b2464c0908298a6 (patch)
tree6b547c1f96dd1a3c89aebcd52aeef78ecc3a84d9 /arch/arm/boot/dts/bcm2835-rpi-common.dtsi
parent9d9491b6411903703a9e20d9e5c1a74861a8fbb2 (diff)
downloadlinux-27ab05e1b7e5c5ec9b4f658e1b2464c0908298a6.tar.xz
ARM: dts: bcm2835-rpi: Use firmware clocks for display
We've experienced a number of issues around the cohabitation between the "real" clock driver in Linux and the one backed by the firmware. One solution around this is to follow what the RaspberryPi foundation in its downstream clock, which is also what we've been doing on the RaspberryPi4: to use the clocks exposed by the firmware. Link: https://lore.kernel.org/linux-clk/20221021140505.kjmw5x4s6qhnrfif@houat/ Signed-off-by: Maxime Ripard <maxime@cerno.tech> Link: https://lore.kernel.org/r/20221026-rpi-display-fw-clk-v1-2-5c29b7a3d8b0@cerno.tech Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Diffstat (limited to 'arch/arm/boot/dts/bcm2835-rpi-common.dtsi')
-rw-r--r--arch/arm/boot/dts/bcm2835-rpi-common.dtsi17
1 files changed, 17 insertions, 0 deletions
diff --git a/arch/arm/boot/dts/bcm2835-rpi-common.dtsi b/arch/arm/boot/dts/bcm2835-rpi-common.dtsi
index 8a55b6cded59..4e7b4a592da7 100644
--- a/arch/arm/boot/dts/bcm2835-rpi-common.dtsi
+++ b/arch/arm/boot/dts/bcm2835-rpi-common.dtsi
@@ -7,6 +7,23 @@
#include <dt-bindings/power/raspberrypi-power.h>
+&firmware {
+ firmware_clocks: clocks {
+ compatible = "raspberrypi,firmware-clocks";
+ #clock-cells = <1>;
+ };
+};
+
+&hdmi {
+ clocks = <&firmware_clocks 9>,
+ <&firmware_clocks 13>;
+ clock-names = "pixel", "hdmi";
+};
+
&v3d {
power-domains = <&power RPI_POWER_DOMAIN_V3D>;
};
+
+&vec {
+ clocks = <&firmware_clocks 15>;
+};