All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benedikt-Alexander Mokroß" <u-boot@bamkrs.de>
To: u-boot@lists.denx.de
Subject: [PATCH] Correct sun8i-v3s SRAM size
Date: Tue, 2 Jun 2020 09:10:08 +0200	[thread overview]
Message-ID: <BCD852AB-2814-4D74-B41F-D7C281D15D43@bamkrs.de> (raw)
In-Reply-To: <CAMty3ZBQ9kYh+aUgMSbGiSgCd3jxa9Yy2+AdhPwxTgw54bvH-g@mail.gmail.com>

Hi Jagan,

I run into some size-related issues regarding my SPL configuration for a custom V3s board (mainly due to using fit images). In fact, the V3s has even more SRAM that could be used for the SPL. However the BROM won't boot anything larger than 32KiB. So I use this 32KiB limit in production now and found no issues with my 29KiB SPL whatsoever. And - if I read the BROM ASM correctly - there is no performance drawback for default (and smaller) SPL configurations since the BROM only loads the actual SPL size amount of pages/bytes.

I think it would be much less frustrating for other users if they could use these 32KiB from the start since the current limit is hit pretty fast and there is no reason why it should be this 24k limit for the V3s. It's another poorly or even plain wrongly documented aspect of the Allwinner BSP.

Benedikt

Am 1. Juni 2020 19:00:30 MESZ schrieb Jagan Teki <jagan@amarulasolutions.com>:
On Tue, Apr 28, 2020 at 9:26 PM Benedikt-Alexander Mokro?
<catchall@bamkrs.de> wrote:

 According to the Datasheet, the V3s has a 32KiB SRAM.
 This patch corrects CONFIG_SPL_MAX_SIZE and LOW_LEVEL_SRAM_STACK
 accordingly.

Look like the existing value has taken from allwinner BSP, but did you
find any issues with the existing one?

Jagan.

  reply	other threads:[~2020-06-02  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 14:33 [PATCH] Correct sun8i-v3s SRAM size Benedikt-Alexander Mokroß
2020-06-01 17:00 ` Jagan Teki
2020-06-02  7:10   ` Benedikt-Alexander Mokroß [this message]
2020-06-02 10:50     ` Maxime Ripard
2020-06-11  9:30     ` Jagan Teki

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=BCD852AB-2814-4D74-B41F-D7C281D15D43@bamkrs.de \
    --to=u-boot@bamkrs.de \
    --cc=u-boot@lists.denx.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.