mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: oss@kalray.eu
To: barebox@lists.infradead.org
Cc: jmaselbas@kalray.eu, ysionneau@kalray.eu
Subject: [PATCH 1/3] kvx: Add missing include/asm/mmu.h
Date: Tue, 27 Jun 2023 17:42:00 +0200	[thread overview]
Message-ID: <20230627154202.8976-1-oss@kalray.eu> (raw)

From: Jules Maselbas <jmaselbas@kalray.eu>

Since the rework of remap_range each architecture is expected to have
the asm/mmu.h header, this wasn't the case for kvx, fix this.

By default the KV3-1 cpu (as found in Coolidge SoC) starts with all memory
uncached and MMU disabled. Data and instruction L1-caches are enabled very
early during barebox start code, see arch/kvx/cpu/start.S, using the wfxl
instruction to modify DCE and ICE (resp. Data and Instruction Cache Enable)
bits in PS (Processor Status) of the system register file.

The core MMU is not used by barebox, however there is a default mapping of
the memory when the MMU is disabled where only the SMEM and DDR memory are
cached and device-memory isn't.

Fixes b792124a7d ("rework remap_range")

Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
---
 arch/kvx/include/asm/mmu.h | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 arch/kvx/include/asm/mmu.h

diff --git a/arch/kvx/include/asm/mmu.h b/arch/kvx/include/asm/mmu.h
new file mode 100644
index 0000000000..d39889bd3f
--- /dev/null
+++ b/arch/kvx/include/asm/mmu.h
@@ -0,0 +1,8 @@
+/* SPDX-License-Identifier: GPL-2.0-only */
+
+#ifndef __ASM_MMU_H
+#define __ASM_MMU_H
+
+#define MAP_ARCH_DEFAULT MAP_CACHED
+
+#endif /* __ASM_MMU_H */
-- 
2.17.1








             reply	other threads:[~2023-06-27 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 15:42 oss [this message]
2023-06-27 15:42 ` [PATCH 2/3] kvx: Replace dinval alias with d1inval oss
2023-06-27 15:42 ` [PATCH 3/3] kvx: Fix asm syntax in start.S oss
2023-06-28  8:46 ` [PATCH 1/3] kvx: Add missing include/asm/mmu.h Sascha Hauer

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=20230627154202.8976-1-oss@kalray.eu \
    --to=oss@kalray.eu \
    --cc=barebox@lists.infradead.org \
    --cc=jmaselbas@kalray.eu \
    --cc=ysionneau@kalray.eu \
    /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