U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Prasanth Babu Mantena <p-mantena@ti.com>
Cc: sjg@chromium.org, alpernebiyasak@gmail.com, u-boot@lists.denx.de,
	vigneshr@ti.com, u-kumar1@ti.com, n-francis@ti.com,
	vaishnav.a@ti.com
Subject: Re: [PATCH] common: spl: Enable Instruction cache after relocation in board_init_r
Date: Mon, 17 Mar 2025 09:13:18 -0600	[thread overview]
Message-ID: <20250317151318.GR2640854@bill-the-cat> (raw)
In-Reply-To: <20250317064507.1702120-1-p-mantena@ti.com>

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

On Mon, Mar 17, 2025 at 12:15:07PM +0530, Prasanth Babu Mantena wrote:

> ICACHE is enabled in board_init_f which executes only before relocation.
> Instruction cache invalidation is needed after relocation as well in the
> common spl, which is taken care in the u-boot init_sequence, but missing
> for the spl. So, enable it at the start of board_init_r for spl, which
> invalidates icache needed after instruction relocation.
> 
> Fixes: 52a86e69e20 ("arm: k3: Enable instruction cache for main domain SPL")
> Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com>
> ---
>  arch/arm/mach-k3/common.c | 1 +
>  common/spl/spl.c          | 1 +
>  2 files changed, 2 insertions(+)

What's missing from spl_enable_cache() in K3 already? And looking more
at this, since Rockchip does this slightly differently I wonder if we
need to think harder about making some of these hook points generic.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2025-03-17 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  6:45 [PATCH] common: spl: Enable Instruction cache after relocation in board_init_r Prasanth Babu Mantena
2025-03-17 15:13 ` Tom Rini [this message]
2025-03-25  5:34   ` Prasanth Mantena
2025-11-26 11:34     ` Ernest Van Hoecke
2025-11-26 13:04       ` Kumar, Udit
2025-11-28 19:24         ` Ernest Van Hoecke
2025-11-29  4:26           ` Kumar, Udit
2025-12-01 10:06             ` Ernest Van Hoecke

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=20250317151318.GR2640854@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=n-francis@ti.com \
    --cc=p-mantena@ti.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=vaishnav.a@ti.com \
    --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