Hi,
Over the years, the differences between the Pi0-3 and the Pi4 created a bunch
of issues in the KMS driver that trace back to the policy differences between
the clk-bcm2835 and clk-raspberrypi drivers.
Instead of piling hacks over hacks to work around those differences, let's just
follow what downstream is doing and use the clk-raspberrypi for all the KMS
related devices.
Let me know what you think,
Maxime
To: Rob Herring <robh+dt@xxxxxxxxxx>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@xxxxxxxxxx>
To: Florian Fainelli <f.fainelli@xxxxxxxxx>
To: Broadcom internal kernel review list <bcm-kernel-feedback-list@xxxxxxxxxxxx>
To: Ray Jui <rjui@xxxxxxxxxxxx>
To: Scott Branden <sbranden@xxxxxxxxxxxx>
Cc: Dave Stevenson <dave.stevenson@xxxxxxxxxxxxxxx>
Cc: Dom Cobley <dom@xxxxxxxxxxxxxxx>
Cc: Phil Elwell <phil@xxxxxxxxxxxxxxx>
Cc: devicetree@xxxxxxxxxxxxxxx
Cc: linux-rpi-kernel@xxxxxxxxxxxxxxxxxxx
Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
Cc: linux-kernel@xxxxxxxxxxxxxxx
Signed-off-by: Maxime Ripard <maxime@xxxxxxxxxx>
---
Maxime Ripard (2):
ARM: dts: bcm283x: Remove bcm2835-rpi-common.dtsi from SoC DTSI
ARM: dts: bcm2835-rpi: Use firmware clocks for display
arch/arm/boot/dts/bcm2835-rpi-a-plus.dts | 1 +
arch/arm/boot/dts/bcm2835-rpi-a.dts | 1 +
arch/arm/boot/dts/bcm2835-rpi-b-plus.dts | 1 +
arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts | 1 +
arch/arm/boot/dts/bcm2835-rpi-b.dts | 1 +
arch/arm/boot/dts/bcm2835-rpi-cm1.dtsi | 1 +
arch/arm/boot/dts/bcm2835-rpi-common.dtsi | 17 +++++++++++++++++
arch/arm/boot/dts/bcm2835-rpi-zero-w.dts | 1 +
arch/arm/boot/dts/bcm2835-rpi-zero.dts | 1 +
arch/arm/boot/dts/bcm2835.dtsi | 1 -
arch/arm/boot/dts/bcm2836-rpi.dtsi | 1 +
arch/arm/boot/dts/bcm2836.dtsi | 1 -
arch/arm/boot/dts/bcm2837.dtsi | 1 -
13 files changed, 26 insertions(+), 3 deletions(-)
---
base-commit: 5398aeb71349b5e67658d51f46e12117060d867d
change-id: 20221026-rpi-display-fw-clk-0382f7afa5e8
Best regards,
--
Maxime Ripard <maxime@xxxxxxxxxx>
