U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Tom Rini <trini@konsulko.com>
Cc: j@jannau.net, u-boot@lists.denx.de
Subject: Re: [PATCH] apple_m1_defconfig: Bump CONFIG_LMB_MAX_REGIONS to 64
Date: Fri, 17 Mar 2023 19:16:21 +0100	[thread overview]
Message-ID: <875yazb5vu.fsf@bloch.sibelius.xs4all.nl> (raw)
In-Reply-To: <20230317164316.GZ54321@bill-the-cat> (message from Tom Rini on Fri, 17 Mar 2023 12:43:16 -0400)

> Date: Fri, 17 Mar 2023 12:43:16 -0400
> From: Tom Rini <trini@konsulko.com>
> 
> On Mon, Mar 13, 2023 at 03:31:32PM +0100, Mark Kettenis wrote:
> > > From: Janne Grunau <j@jannau.net>
> > > Date: Mon, 13 Mar 2023 14:54:32 +0100
> > > 
> > > Apple silicon SoCs have numerous embedded co-processors with pre-loaded
> > > firmware. The co-processors text and data sections need to be mapped via
> > > DART iommus controlled by the main processor. Those sections are
> > > exported as reserved-memory. Bump CONFIG_LMB_MAX_REGIONS from 8 to 64 to
> > > deal with the large amount of reserved-memory regions.
> > 
> > We recently bumped the default for CONFIG_LMB_MAX_REGIONS from 8 to
> > 16, but 64 would be a safer value for this platform as there are more
> > co-processor drivers in the pipeline that may add reserved-memory
> > regions.  These machines have plenty of memory.
> > 
> > > Signed-off-by: Janne Grunau <j@jannau.net>
> > 
> > Reviewed-by: Mark Kettenis <kettenis@openbsd.org>
> 
> Does this mean it's a fix we need for v2023.04, or v2023.07 is OK?

2023.07 is ok

  reply	other threads:[~2023-03-17 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 13:54 [PATCH] apple_m1_defconfig: Bump CONFIG_LMB_MAX_REGIONS to 64 Janne Grunau
2023-03-13 14:31 ` Mark Kettenis
2023-03-17 16:43   ` Tom Rini
2023-03-17 18:16     ` Mark Kettenis [this message]
2023-03-30  1:54 ` 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=875yazb5vu.fsf@bloch.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=j@jannau.net \
    --cc=trini@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox