All of lore.kernel.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Marek Vasut <marek.vasut@mailbox.org>, Tom Rini <trini@konsulko.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Leo Liang <leo.liang@sifive.com>,
	u-boot@lists.u-boot-project.org
Subject: Re: [PATCH] lmb: Add StarFive JH-7110 SoC as requiring DMA below 4G
Date: Tue, 29 Sep 2026 18:51:24 -0700	[thread overview]
Message-ID: <8a759e95-866e-460c-9899-d5bb30ff4e04@freeshell.de> (raw)
In-Reply-To: <bdec8558-0408-4efc-8a50-e726c8be9cee@mailbox.org>

Hi,

On 9/29/26 17:43, Marek Vasut wrote:
> On 9/30/26 1:07 AM, E Shattow wrote:
>> Platform drivers and hardware for StarFive JH-7110 SoC are not capable of
>> DMA access above 4GB
> 
> 4 GiB

Yes, I agree.

> 
>> . 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>
> 
> Reviewed-by: Marek Vasut <marek.vasut+renesas@mailbox.org>

Looks good to me as suggested.

Thanks,  -E



  reply	other threads:[~2026-09-30  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 23:07 [PATCH] lmb: Add StarFive JH-7110 SoC as requiring DMA below 4G E Shattow
2026-09-30  0:43 ` Marek Vasut
2026-09-30  1:51   ` E Shattow [this message]
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=8a759e95-866e-460c-9899-d5bb30ff4e04@freeshell.de \
    --to=e@freeshell.de \
    --cc=leo.liang@sifive.com \
    --cc=marek.vasut@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.