U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Tom Rini <trini@konsulko.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Leo Liang <leo.liang@sifive.com>,
	Marek Vasut <marek.vasut+renesas@mailbox.org>,
	E Shattow <e@freeshell.de>,
	u-boot@lists.u-boot-project.org
Subject: [PATCH] lmb: Add StarFive JH-7110 SoC as requiring DMA below 4G
Date: Tue, 29 Sep 2026 16:07:50 -0700	[thread overview]
Message-ID: <20260929230758.616924-1-e@freeshell.de> (raw)

Platform drivers and hardware for StarFive JH-7110 SoC are not capable of
DMA access above 4GB. This was previously a problem for MMC access then
resolved by a workaround, since reverted in a3075db94d49 ("lmb: Reinstate
access to memory above ram_top"). The symptom of this is EFI boot failure
of GRUB from EFI System Partition on USB MSC with a starfive_visionfive2
board target that has the on-chip Cadence USB, tested with Pine64 Star64.

Restore the workaround with a dependency on LMB_LIMIT_DMA_BELOW_RAM_TOP.

Signed-off-by: E Shattow <e@freeshell.de>
---
 lib/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Kconfig b/lib/Kconfig
index 6b6b90bc915c..4bb120c97cbd 100644
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -1314,7 +1314,7 @@ config SPL_LMB_ARCH_MEM_MAP
 config LMB_LIMIT_DMA_BELOW_RAM_TOP
 	bool
 	depends on LMB
-	default y if ARCH_BCM283X || ARCH_ROCKCHIP
+	default y if ARCH_BCM283X || ARCH_ROCKCHIP || STARFIVE_JH7110
 	help
 	  Some architectures can not DMA above ram_top boundary,
 	  which is after 4 GiB or 32-bit boundary too. Limit the

base-commit: 369d71b895bc5ce94556d43f05ef9d20084af0d5
-- 
2.53.0


             reply	other threads:[~2026-09-29 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 23:07 E Shattow [this message]
2026-09-30  0:43 ` [PATCH] lmb: Add StarFive JH-7110 SoC as requiring DMA below 4G Marek Vasut
2026-09-30  1:51   ` E Shattow
2026-09-30 14:18     ` Tom Rini
2026-09-30 17:17 ` 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=20260929230758.616924-1-e@freeshell.de \
    --to=e@freeshell.de \
    --cc=leo.liang@sifive.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=xypron.glpk@gmx.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