27ab05e1b7
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>
30 lines
586 B
Plaintext
30 lines
586 B
Plaintext
// SPDX-License-Identifier: GPL-2.0
|
|
/*
|
|
* This include file covers the common peripherals and configuration between
|
|
* bcm2835, bcm2836 and bcm2837 implementations that interact with RPi's
|
|
* firmware interface.
|
|
*/
|
|
|
|
#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>;
|
|
};
|