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:59:48 +0300	[thread overview]
Message-ID: <31e67cb7-0b96-21be-b354-e5b81aa7b1cb@kernel.org> (raw)
In-Reply-To: <20230802213716.sohjkswusmtajy2a@overhear>



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.
> 

I got rid of /delete-property/ for main_i2c0 and main_gpio0 and
didn't see any ill effects. So will drop them from there.
Looks like we need to have it only for main_uart0 and main_timer0.
I'll add a comment for main_uart0.

-- 
cheers,
-roger

      parent reply	other threads:[~2023-08-03 12:59 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
2023-08-03 12:59     ` Roger Quadros [this message]

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=31e67cb7-0b96-21be-b354-e5b81aa7b1cb@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