linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: nicolas saenz julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	soc@kernel.org, Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 3/6] ARM: dts: Move BCM2711 RPi specific into separate dtsi
Date: Tue, 1 Jun 2021 20:51:22 +0200	[thread overview]
Message-ID: <320c7299-3f89-861c-6a80-043b209e79e1@i2se.com> (raw)
In-Reply-To: <86a7cded6e3e17b0ab347e55b38a44e10bc4e46a.camel@kernel.org>

Hi Nicolas,

Am 01.06.21 um 12:03 schrieb nicolas saenz julienne:
> Hi Stefan,
> Thanks for having a go at this.
>
> On Sun, 2021-05-30 at 11:26 +0200, Stefan Wahren wrote:
>> There is a lot of Raspberry Pi specific stuff (neither SoC or board
>> specific) for the BCM2711 which is currently in the RPi 4 B dts. In order
>> to avoid copy & paste for every new BCM2711 based Raspberry Pi, move it
>> into a separate dtsi.
>>
>> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
>> ---
>>  arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 62 +----------------------------
>>  arch/arm/boot/dts/bcm2711-rpi.dtsi    | 75 +++++++++++++++++++++++++++++++++++
>>  2 files changed, 76 insertions(+), 61 deletions(-)
>>  create mode 100644 arch/arm/boot/dts/bcm2711-rpi.dtsi
>>
>> diff --git a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
>> index 3b4ab94..78142a0 100644
>> --- a/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
>> +++ b/arch/arm/boot/dts/bcm2711-rpi-4-b.dts
>> @@ -1,11 +1,9 @@
>>  // SPDX-License-Identifier: GPL-2.0
>>  /dts-v1/;
>>  #include "bcm2711.dtsi"
>> -#include "bcm2835-rpi.dtsi"
>> +#include "bcm2711-rpi.dtsi"
>>  #include "bcm283x-rpi-usb-peripheral.dtsi"
>>  
>>
>> -#include <dt-bindings/reset/raspberrypi,firmware-reset.h>
>> -
>>  / {
>>  	compatible = "raspberrypi,4-model-b", "brcm,bcm2711";
>>  	model = "Raspberry Pi 4 Model B";
>> @@ -22,10 +20,7 @@
>>  	};
>>  
>>
>>  	aliases {
>> -		emmc2bus = &emmc2bus;
>>  		ethernet0 = &genet;
> Why not picking this one? nor the relevant DT nodes? I belive it's available on
> all the bcm2711 based boards.
While i agree that most of the boards [1] support Ethernet, the PHY
stuff is almost board specific.
>
>> -		pcie0 = &pcie0;
>> -		blconfig = &blconfig;
>>  	};
>>  
>>
>>  	leds {
>> @@ -80,11 +75,6 @@
>>  };
>>  
>>
>>  &firmware {
>> -	firmware_clocks: clocks {
>> -		compatible = "raspberrypi,firmware-clocks";
>> -		#clock-cells = <1>;
>> -	};
>> -
>>  	expgpio: gpio {
> Why not taking this one too and letting each dts file define its own
> 'gpio-line-names'?
Agree
>
>>  		compatible = "raspberrypi,firmware-gpio";
>>  		gpio-controller;
>> @@ -99,11 +89,6 @@
>>  				  "";
>>  		status = "okay";
>>  	};
>> -
>> -	reset: reset {
>> -		compatible = "raspberrypi,firmware-reset";
>> -		#reset-cells = <1>;
>> -	};
>>  };
>>  
>>
>>  &gpio {
>> @@ -180,23 +165,13 @@
>>  };
>>  
>>
>>  &hdmi0 {
>> -	clocks = <&firmware_clocks 13>, <&firmware_clocks 14>, <&dvp 0>, <&clk_27MHz>;
>> -	clock-names = "hdmi", "bvb", "audio", "cec";
>> -	wifi-2.4ghz-coexistence;
>>  	status = "okay";
>>  };
>>  
>>
>>  &hdmi1 {
>> -	clocks = <&firmware_clocks 13>, <&firmware_clocks 14>, <&dvp 1>, <&clk_27MHz>;
>> -	clock-names = "hdmi", "bvb", "audio", "cec";
>> -	wifi-2.4ghz-coexistence;
>>  	status = "okay";
>>  };
>>  
>>
>> -&hvs {
>> -	clocks = <&firmware_clocks 4>;
>> -};
>> -
>>  &pixelvalve0 {
>>  	status = "okay";
>>  };
>> @@ -219,22 +194,6 @@
>>  	status = "okay";
>>  };
>>  
>>
>> -&rmem {
>> -	/*
>> -	 * RPi4's co-processor will copy the board's bootloader configuration
>> -	 * into memory for the OS to consume. It'll also update this node with
>> -	 * its placement information.
>> -	 */
>> -	blconfig: nvram@0 {
>> -		compatible = "raspberrypi,bootloader-config", "nvmem-rmem";
>> -		#address-cells = <1>;
>> -		#size-cells = <1>;
>> -		reg = <0x0 0x0 0x0>;
>> -		no-map;
>> -		status = "disabled";
>> -	};
>> -};
>> -
>>  /* SDHCI is used to control the SDIO for wireless */
>>  &sdhci {
>>  	#address-cells = <1>;
>> @@ -273,21 +232,6 @@
>>  	};
>>  };
>>  
>>
>> -&pcie0 {
>> -	pci@1,0 {
>> -		#address-cells = <3>;
>> -		#size-cells = <2>;
>> -		ranges;
>> -
>> -		reg = <0 0 0 0 0>;
>> -
>> -		usb@1,0 {
>> -			reg = <0x10000 0 0 0 0>;
>> -			resets = <&reset RASPBERRYPI_FIRMWARE_RESET_ID_USB>;
>> -		};
>> -	};
>> -};
>> -
> This is not relevant to CM4, maybe we should leave it in the .dts
Okay
>
>>  /* uart0 communicates with the BT module */
>>  &uart0 {
> What about 'uart1'? I belive the configuration is the same for all boards. pwm1
> also comes to mind.

I wouldn't include pinmux dependent stuff here, because this is very
specific to the board and use case [1].

But there is a trick for the Pi 400, which is very similiar to the Pi 4
B. We could include the pi4.dts in the pi400.dts. Additional i would
keep this patch for CM4 and co.

Regards
Stefan

[1] -
https://afterhourscoding.wordpress.com/2021/02/21/a-list-of-raspberry-pi-compute-module-carrier-boards-and-devices/

>
> Regards,
> Nicolas
>
>


  parent reply	other threads:[~2021-06-01 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30  9:26 [PATCH 0/6] ARM: dts: Add Raspberry Pi 400 support Stefan Wahren
2021-05-30  9:26 ` [PATCH 1/6] ARM: dts: bcm283x: Fix up MMC node names Stefan Wahren
2021-05-30  9:26 ` [PATCH 2/6] watchdog: bcm2835_wdt: consider system-power-controller property Stefan Wahren
2021-06-02 10:37   ` Guenter Roeck
     [not found]   ` <e61ba6f5b906fd26a61e9c79ef4dcf4792a364d7.camel@kernel.org>
2021-06-02 10:40     ` Guenter Roeck
2021-05-30  9:26 ` [PATCH 3/6] ARM: dts: Move BCM2711 RPi specific into separate dtsi Stefan Wahren
     [not found]   ` <86a7cded6e3e17b0ab347e55b38a44e10bc4e46a.camel@kernel.org>
2021-06-01 18:51     ` Stefan Wahren [this message]
2021-05-30  9:26 ` [PATCH 4/6] dt-bindings: arm: bcm2835: Add Raspberry Pi 400 to DT schema Stefan Wahren
2021-06-04 21:31   ` Rob Herring
2021-05-30  9:26 ` [PATCH 5/6] ARM: dts: Add Raspberry Pi 400 support Stefan Wahren
2021-05-30  9:26 ` [PATCH 6/6] arm64: dts: broadcom: Add reference to RPi 400 Stefan Wahren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=320c7299-3f89-861c-6a80-043b209e79e1@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=nsaenz@kernel.org \
    --cc=olof@lixom.net \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=soc@kernel.org \
    --cc=wim@linux-watchdog.org \
    --subject='Re: [PATCH 3/6] ARM: dts: Move BCM2711 RPi specific into separate dtsi' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).