public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: trini@konsulko.com, vigneshr@ti.com, srk@ti.com,
	r-gunasekaran@ti.com, s-vadapalli@ti.com, u-boot@lists.denx.de
Subject: Re: [PATCH v3 4/4] arm: dts: k3-am64: Sync DT with Linux v6.5-rc1
Date: Thu, 3 Aug 2023 15:39:23 +0300	[thread overview]
Message-ID: <493abcbf-fbe3-5651-ce7a-ee844f7d4818@kernel.org> (raw)
In-Reply-To: <20230802213716.sohjkswusmtajy2a@overhear>

Hi Nishanth,

On 03/08/2023 00:37, Nishanth Menon wrote:
> On 20:18-20230802, Roger Quadros wrote:
>> Sync all am642-evm/am642-sk related DT files
>> with Linux v6.5-rc1.
>>
>> - drop timer1 in favor of main_timer0 in am64-main.dtsi.
>> Need to delete clock & power domain properties of
>> main_timer1 in -r5.dts else won't boot. This is because
>> timer_init is done during rproc_start to start System Firmware,
>> but we can't do any clock/power-domain operations before
>> System Firmware starts.
> 
> if that is the argument for main_uart0 and main_i2c0 main_gpio0 etc.
> - please document in the r5.dts as well as to why we are
> /delete-property/ power-domains. I think we feed in boardconfig etc by
> the time we get around to this, correct? if not, we might need to state
> that information - that without boardconfig being fed to the sysfw pm
> functions are'nt active.
> 
> 
> Otherwise, this is coming along just right.
> 
>> - drop cpsw3g custom DT property 'mac_efuse' and custom
>> DT node cpsw-phy-sel as driver picks these from standard
>> property/node.
>> - include board dts file in -r5 dts file to avoid duplication
>> of nodes. Include -u-boot.dtsi on top.
>> - drop duplicate nodes in -r5 dts and -u-boot.dtsi
>>
>> Signed-off-by: Roger Quadros <rogerq@kernel.org>
>> ---
>>  arch/arm/dts/k3-am64-main.dtsi        | 171 ++++++++++++++++++++-
>>  arch/arm/dts/k3-am64-mcu.dtsi         |  53 ++++++-
>>  arch/arm/dts/k3-am64-thermal.dtsi     |  33 ++++
>>  arch/arm/dts/k3-am64.dtsi             |  22 +--
>>  arch/arm/dts/k3-am642-evm-u-boot.dtsi |  67 +++++----
>>  arch/arm/dts/k3-am642-evm.dts         | 173 ++++++++++++++++-----
>>  arch/arm/dts/k3-am642-r5-evm.dts      | 202 +++----------------------
>>  arch/arm/dts/k3-am642-r5-sk.dts       | 209 +++-----------------------
>>  arch/arm/dts/k3-am642-sk-u-boot.dtsi  |  59 ++++----
>>  arch/arm/dts/k3-am642-sk.dts          | 166 ++++++++++++++------
>>  arch/arm/dts/k3-am642.dtsi            |   1 +
>>  11 files changed, 613 insertions(+), 543 deletions(-)
>>  create mode 100644 arch/arm/dts/k3-am64-thermal.dtsi
>>
>> diff --git a/arch/arm/dts/k3-am64-main.dtsi b/arch/arm/dts/k3-am64-main.dtsi

<snip>

>> diff --git a/arch/arm/dts/k3-am642-r5-evm.dts b/arch/arm/dts/k3-am642-r5-evm.dts
>> index b49064181a..240278dd53 100644
>> --- a/arch/arm/dts/k3-am642-r5-evm.dts
>> +++ b/arch/arm/dts/k3-am642-r5-evm.dts
>> @@ -1,19 +1,17 @@
>>  // SPDX-License-Identifier: GPL-2.0
>>  /*
>> - * Copyright (C) 2020-2021 Texas Instruments Incorporated - https://www.ti.com/
>> + * Copyright (C) 2020-2023 Texas Instruments Incorporated - https://www.ti.com/
>>   */
>>  
>> -/dts-v1/;
>> -
>> -#include "k3-am642.dtsi"
>> +#include "k3-am642-evm.dts"
>>  #include "k3-am64-evm-ddr4-1600MTs.dtsi"
>>  #include "k3-am64-ddr.dtsi"
>> -#include "k3-am64x-binman.dtsi"
>> +
>> +#include "k3-am642-evm-u-boot.dtsi"
>>  
>>  / {
>>  	chosen {
>>  		stdout-path = "serial2:115200n8";
>> -		tick-timer = &timer1;
>>  	};
> 
> Drop the entire chosen - comes in from u-boot.dtsi
> 
>>  
>>  	aliases {
>> @@ -21,14 +19,6 @@
>>  		remoteproc1 = &a53_0;
>>  	};
>>  
>> -	memory@80000000 {
>> -		device_type = "memory";
>> -		/* 2G RAM */
>> -		reg = <0x00000000 0x80000000 0x00000000 0x80000000>;
>> -
>> -		bootph-pre-ram;
>> -	};
>> -
>>  	a53_0: a53@0 {
>>  		compatible = "ti,am654-rproc";
>>  		reg = <0x00 0x00a90000 0x00 0x10>;
>> @@ -46,34 +36,12 @@
>>  		bootph-pre-ram;
>>  	};
>>  
> 
> Can you also look at the &memory_controller {
> } node?
> 
> I think vtt_supply already points to the DDR vtt pinmux? so, a bit
> confused why we would point the pinctrl-0 to the same pinmux again?
> 

Right. Also vtt_supply is always-on fixed regulator.
So will drop vtt-supply property from memory_controller node.

<snip>

>> -#include "k3-am642-evm-u-boot.dtsi"
>> diff --git a/arch/arm/dts/k3-am642-r5-sk.dts b/arch/arm/dts/k3-am642-r5-sk.dts
>> index 32d4c31728..9dbd444d6d 100644
>> --- a/arch/arm/dts/k3-am642-r5-sk.dts
>> +++ b/arch/arm/dts/k3-am642-r5-sk.dts
>> @@ -3,19 +3,15 @@
>>   * Copyright (C) 2021 Texas Instruments Incorporated - https://www.ti.com/
>>   */
>>  
>> -/dts-v1/;
>> -
>> -#include <dt-bindings/mux/ti-serdes.h>
>> -#include <dt-bindings/phy/phy.h>
>> -#include <dt-bindings/net/ti-dp83867.h>
>> -#include "k3-am642.dtsi"
>> +#include "k3-am642-sk.dts"
>>  #include "k3-am64-sk-lp4-1600MTs.dtsi"
>>  #include "k3-am64-ddr.dtsi"
>>  
>> +#include "k3-am642-sk-u-boot.dtsi"
>> +
>>  / {
>>  	chosen {
>>  		stdout-path = "serial2:115200n8";
>> -		tick-timer = &timer1;
>>  	};
> Drop entire chosen?

OK.

> 
>>  
>>  	aliases {
>> @@ -23,13 +19,6 @@
>>  		remoteproc1 = &a53_0;
>>  	};
>>  
>> -	memory@80000000 {
>> -		device_type = "memory";
>> -		/* 2G RAM */
>> -		reg = <0x00000000 0x80000000 0x00000000 0x80000000>;
>> -		bootph-pre-ram;
>> -	};
>> -
>>  	a53_0: a53@0 {
>>  		compatible = "ti,am654-rproc";
>>  		reg = <0x00 0x00a90000 0x00 0x10>;
>> @@ -47,18 +36,6 @@
>>  		bootph-pre-ram;
>>  	};
>>  
>> -	reserved-memory {
>> -		#address-cells = <2>;
>> -		#size-cells = <2>;
>> -		ranges;
>> -
>> -		secure_ddr: optee@9e800000 {
>> -			reg = <0x00 0x9e800000 0x00 0x01800000>; /* for OP-TEE */
>> -			alignment = <0x1000>;
>> -			no-map;
>> -		};
>> -	};
>> -
>>  	clk_200mhz: dummy-clock-200mhz {
>>  		compatible = "fixed-clock";
>>  		#clock-cells = <0>;
>> @@ -76,110 +53,6 @@
>>  	};
>>  };
>>  
>> -&cbass_main {
>> -	main_esm: esm@420000 {
>> -		compatible = "ti,j721e-esm";
>> -		reg = <0x0 0x420000 0x0 0x1000>;
>> -		ti,esm-pins = <160>, <161>;
>> -		bootph-pre-ram;
>> -	};
>> -};
> 
> please add for r5-sk:
> &main_esm {
>         bootph-pre-ram;
> };
> 
> &mcu_esm {
>         bootph-pre-ram;
> };
> 

I added them in -u-boot.dtsi along with cbass_main and cbass_mcu.
Should I move them to -r5-sk instead?

<snip>

-- 
cheers,
-roger

  reply	other threads:[~2023-08-03 12:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 17:18 [PATCH v3 0/4] arm: dts: k3-am64: Sync DT with Linux Roger Quadros
2023-08-02 17:18 ` [PATCH v3 1/4] board: ti: am64x: Recognize AM64-HSEVM Roger Quadros
2023-08-02 17:56   ` Nishanth Menon
2023-08-02 18:49     ` Roger Quadros
2023-08-02 17:18 ` [PATCH v3 2/4] doc: board: ti: am64: Add boot flow diagram Roger Quadros
2023-08-02 17:27   ` Tom Rini
2023-08-02 17:55   ` Nishanth Menon
2023-08-02 19:06     ` Roger Quadros
2023-08-02 22:12       ` Nishanth Menon
2023-08-02 17:18 ` [PATCH v3 3/4] Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node" Roger Quadros
2023-08-02 17:18 ` [PATCH v3 4/4] arm: dts: k3-am64: Sync DT with Linux v6.5-rc1 Roger Quadros
2023-08-02 21:37   ` Nishanth Menon
2023-08-03 12:39     ` Roger Quadros [this message]
2023-08-03 12:59     ` Roger Quadros

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=493abcbf-fbe3-5651-ce7a-ee844f7d4818@kernel.org \
    --to=rogerq@kernel.org \
    --cc=nm@ti.com \
    --cc=r-gunasekaran@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox