All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: trini@konsulko.com, nm@ti.com
Cc: vigneshr@ti.com, m-chawdhry@ti.com, sjg@chromium.org,
	jonas@kwiboo.se, srk@ti.com, afd@ti.com, bb@ti.com,
	praneeth@ti.com, u-boot@lists.denx.de,
	Roger Quadros <rogerq@kernel.org>
Subject: [RESEND PATCH 0/6] arm: dts: k3-am64 / k3-am62: Fix boot
Date: Fri, 29 Sep 2023 16:46:40 +0300	[thread overview]
Message-ID: <20230929134646.214781-1-rogerq@kernel.org> (raw)

Hi,

(Apologies for resend as I missed the u-boot list the last time.
Thanks Vignesh for catching this :) )
    
Since commit [1] A53 u-boot proper is broken.
This is because nodes marked as 'bootph-pre-ram' are
not availble at u-boot proper before relocation.

To fix this we mark all nodes in sk-u-boot.dtsi as
'bootph-all'.

Move cbass_mcu node to -r5-sk.dts as it is only required
for R5 SPL.

[1]
9e644284ab812 ("dm: core: Report bootph-pre-ram/sram node as pre-reloc after relocation")

In addition to this we also fix some dts warnings related
to CPSW nodes in R5 SPL DTBs.

cheers,
-roger

Roger Quadros (6):
  arm: dts: k3-am64-evm: Fix boot
  arm: dts: k3-am64-evm: Mark dependent nodes for pre-relocation phase
  arm: dts: k3-am642-sk: Fix boot
  arm: dts: k3-am642-sk: Mark dependent nodes for pre-relocation phase
  arm: dts: k3-am625-sk: Fix boot
  arm: dts: k3-am625-sk: Mark dependent nodes for pre-relocation phase

 arch/arm/dts/k3-am625-sk-u-boot.dtsi  |  93 ++++++++++++++-------
 arch/arm/dts/k3-am642-evm-u-boot.dtsi | 104 ++++++++++++++++--------
 arch/arm/dts/k3-am642-r5-evm.dts      |  16 ++++
 arch/arm/dts/k3-am642-r5-sk.dts       |   4 +
 arch/arm/dts/k3-am642-sk-u-boot.dtsi  | 112 +++++++++++++++++---------
 5 files changed, 230 insertions(+), 99 deletions(-)


base-commit: 90c81f407dd4a7747385b10f9b8f732202c45cde
-- 
2.34.1


             reply	other threads:[~2023-09-29 13:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 13:46 Roger Quadros [this message]
2023-09-29 13:46 ` [PATCH 1/6] arm: dts: k3-am64-evm: Fix boot Roger Quadros
2023-10-02 15:19   ` Nishanth Menon
2023-10-02 16:14     ` Roger Quadros
2023-10-02 16:19       ` Nishanth Menon
2023-10-05 14:49   ` Tom Rini
2023-09-29 13:46 ` [PATCH 2/6] arm: dts: k3-am64-evm: Mark dependent nodes for pre-relocation phase Roger Quadros
2023-10-02 15:20   ` Nishanth Menon
2023-09-29 13:46 ` [PATCH 3/6] arm: dts: k3-am642-sk: Fix boot Roger Quadros
2023-10-02 15:20   ` Nishanth Menon
2023-09-29 13:46 ` [PATCH 4/6] arm: dts: k3-am642-sk: Mark dependent nodes for pre-relocation phase Roger Quadros
2023-10-02 15:20   ` Nishanth Menon
2023-09-29 13:46 ` [PATCH 5/6] arm: dts: k3-am625-sk: Fix boot Roger Quadros
2023-10-02 15:20   ` Nishanth Menon
2023-09-29 13:46 ` [PATCH 6/6] arm: dts: k3-am625-sk: Mark dependent nodes for pre-relocation phase Roger Quadros
2023-10-02 15:20   ` Nishanth Menon
2023-10-03 20:26 ` [PATCH] arm: dts: k3-am625-beagleplay: Fix boot Jan Kiszka
2023-10-04 10:01   ` Roger Quadros
2023-10-04 12:15   ` Nishanth Menon
2023-10-05  4:18     ` Jan Kiszka
2023-10-05 11:27       ` Nishanth Menon
2023-10-05 14:49       ` Tom Rini
2023-10-05 14:52         ` Tom Rini

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=20230929134646.214781-1-rogerq@kernel.org \
    --to=rogerq@kernel.org \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=jonas@kwiboo.se \
    --cc=m-chawdhry@ti.com \
    --cc=nm@ti.com \
    --cc=praneeth@ti.com \
    --cc=sjg@chromium.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.