From: Francesco Dolcini <francesco@dolcini.it>
To: trini@konsulko.com, Stefan Eichenberger <eichest@gmail.com>
Cc: stefan.eichenberger@toradex.com, s-k6@ti.com, w.egorov@phytec.de,
n-francis@ti.com, emanuele.ghidoli@toradex.com,
francesco.dolcini@toradex.com, u-boot@lists.denx.de
Subject: Re: [PATCH v1] common/memsize.c: Fix get_ram_size() original data restore
Date: Thu, 26 Feb 2026 08:05:02 +0100 [thread overview]
Message-ID: <20260226070502.GA6701@francesco-nb> (raw)
In-Reply-To: <20250314100734.23777-1-eichest@gmail.com>
Hello Tom,
On Fri, Mar 14, 2025 at 11:06:49AM +0100, Stefan Eichenberger wrote:
> From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
>
> The get_ram_size() function fails to restore the original RAM data when
> the data cache is enabled. This issue was observed on an AM625 R5 SPL
> with 512MB of RAM and is a regression that became visible with
> commit bc07851897bd ("board: ti: Pull redundant DDR functions to a common
> location and Fixup DDR size when ECC is enabled").
>
> Observed boot failure messages:
> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
> Authentication passed
> Starting ATF on ARM64 core...
>
> The system then hangs. This indicates that without a data cache flush,
> data in the cache is not coherent with RAM, preventing the system from
> booting. This was verified by printing the content of this address when
> the issue occurs.
>
> Add a data cache flush after each restore operation to resolve this
> issue.
>
> Fixes: bc07851897bd ("board: ti: Pull redundant DDR functions to a common location and Fixup DDR size when ECC is enabled")
> Fixes: 1c64b98c1ec4 ("common/memsize.c: Fix get_ram_size() when cache is enabled")
> Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
Tom, can we merge this?
This is the last bit to solve the regression reported here,
https://lore.kernel.org/all/20260224152405.GD340942@francesco-nb/
Thanks,
Francesco
next prev parent reply other threads:[~2026-02-26 7:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 10:06 [PATCH v1] common/memsize.c: Fix get_ram_size() original data restore Stefan Eichenberger
2025-03-14 13:28 ` Francesco Dolcini
2025-03-14 16:34 ` Tom Rini
2025-03-17 14:25 ` Stefan Eichenberger
2026-02-26 7:05 ` Francesco Dolcini [this message]
2026-02-26 14:23 ` Tom Rini
2026-02-26 16:11 ` Francesco Dolcini
2026-02-26 16:30 ` Stefan Eichenberger
2026-02-26 16:31 ` Tom Rini
2026-02-27 10:13 ` Francis, Neha
2026-02-27 10:39 ` Emanuele Ghidoli
2026-02-27 17:39 ` Tom Rini
2026-03-02 11:13 ` Emanuele Ghidoli
2026-02-27 10:40 ` Francesco Dolcini
2026-03-02 7:41 ` Francesco Dolcini
2026-03-02 22:10 ` 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=20260226070502.GA6701@francesco-nb \
--to=francesco@dolcini.it \
--cc=eichest@gmail.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=n-francis@ti.com \
--cc=s-k6@ti.com \
--cc=stefan.eichenberger@toradex.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=w.egorov@phytec.de \
/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