summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/imx6sll-kobo-clarahd.dts
diff options
context:
space:
mode:
authorMaxime Ripard <maxime@cerno.tech>2022-10-26 16:17:38 +0300
committerFlorian Fainelli <f.fainelli@gmail.com>2022-11-10 21:15:08 +0300
commit9d9491b6411903703a9e20d9e5c1a74861a8fbb2 (patch)
treea96c28232c19156e663265a69a22d1a2ee2aed7a /arch/arm/boot/dts/imx6sll-kobo-clarahd.dts
parent9f66e1dd82e3186aee95282657512ca2aef1afe0 (diff)
downloadlinux-9d9491b6411903703a9e20d9e5c1a74861a8fbb2.tar.xz
ARM: dts: bcm283x: Remove bcm2835-rpi-common.dtsi from SoC DTSI
According to the commit log of the commit 3ac395a5b3f3 ("ARM: dts: bcm283x: Use firmware PM driver for V3D"), the initial intent behind the bcm2835-rpi-common DTSI was to share data between the RaspberryPies based on the BCM2835, 36 and 37. However, it was included by these SoCs' main DTSI. This is creating an improper layering. On top of that, bcm2835.dtsi is being included by bcm2711.dtsi, which means that, even though the bcm2835-rpi-common DTSI wasn't actually meant to contain data for the BCM2711, it actually leaks into the BCM2711 DTSI. In order to remove both issues, let's remove the include of bcm2835-rpi-common.dtsi from bcm283{5-7}.dtsi and put them into the bcm283{6,7}-rpi.dtsi. BCM2835 has to be handled with special care due to the fact that bcm2835.dtsi is being included by bcm2711.dtsi. Thus, we chose to include bcm2835-rpi-common.dtsi directly into the board DTS. This will be more error-prone, but given that it's a fairly old SoC by now, the chance that we will get more BCM2835 boards is fairly low. BCM2711 isn't modified since the content of bcm2835-rpi-common.dtsi was only a power-domain for the v3d that was overridden anyway. Signed-off-by: Maxime Ripard <maxime@cerno.tech> Link: https://lore.kernel.org/r/20221026-rpi-display-fw-clk-v1-1-5c29b7a3d8b0@cerno.tech Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Diffstat (limited to 'arch/arm/boot/dts/imx6sll-kobo-clarahd.dts')
0 files changed, 0 insertions, 0 deletions