From: Tom Rini <trini@konsulko.com>
To: Nishanth Menon <nm@ti.com>
Cc: vigneshr@ti.com, m-chawdhry@ti.com, sjg@chromium.org,
jonas@kwiboo.se, afd@ti.com, bb@ti.com, praneeth@ti.com,
u-boot@lists.denx.de, Roger Quadros <rogerq@kernel.org>,
Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [PATCH] arm: dts: k3-am625-beagleplay: Fix Boot
Date: Thu, 5 Oct 2023 10:49:35 -0400 [thread overview]
Message-ID: <20231005144935.GO8465@bill-the-cat> (raw)
In-Reply-To: <20231002150053.2930710-1-nm@ti.com>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Mon, Oct 02, 2023 at 10:00:53AM -0500, Nishanth Menon wrote:
> Since commit [1] A53 u-boot proper is broken. This is because nodes
> marked as 'bootph-pre-ram' are not available at u-boot proper before
> relocation.
>
> To fix this we mark all nodes in u-boot.dtsi as 'bootph-all'.
>
> [1]
> 9e644284ab812 ("dm: core: Report bootph-pre-ram/sram node as pre-reloc after relocation")
>
> Reported-by: Roger Quadros <rogerq@kernel.org>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> Reviewed-by: Roger Quadros <rogerq@kernel.org>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-10-05 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 15:00 [PATCH] arm: dts: k3-am625-beagleplay: Fix Boot Nishanth Menon
2023-10-03 9:07 ` Roger Quadros
2023-10-05 14:49 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-29 13:46 [RESEND PATCH 0/6] arm: dts: k3-am64 / k3-am62: Fix boot Roger Quadros
2023-10-03 20:26 ` [PATCH] arm: dts: k3-am625-beagleplay: " 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=20231005144935.GO8465@bill-the-cat \
--to=trini@konsulko.com \
--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=robertcnelson@gmail.com \
--cc=rogerq@kernel.org \
--cc=sjg@chromium.org \
--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