From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, mol@pengutronix.de
Subject: Re: [PATCH 0/6] memory: fuse overlapping memory banks
Date: Wed, 2 Jun 2021 08:38:27 +0200 [thread overview]
Message-ID: <20210602063827.GV5211@pengutronix.de> (raw)
In-Reply-To: <20210531071239.30653-1-a.fatoum@pengutronix.de>
On Mon, May 31, 2021 at 09:12:33AM +0200, Ahmad Fatoum wrote:
> The request region code makes sense to ensure drivers don't try to claim
> (I/O) memory region claimed by another driver or by the memory
> allocator. It doesn't make as much sense for registering available
> memory banks, because there is often overlap:
>
> - device tree often defines the (minimally) available /memory across
> variants
> - subarchitectures like i.MX, STM32MP, OMAP or SAMA5 query the main
> RAM size from controller registers
>
> So far, overlap went mostly unnoticed, because the RAM controller
> drivers didn't check for errors. However, if barebox is already running
> from RAM outside that described by the device tree, there will be errors
> and /delete-node/ annotations that need to be added into device trees.
>
> Upstream device tree can be extended later on with a /memory node, which
> in turn will break barebox. This series fixes all of that. Overlapping
> memory banks are combined into one. Errors are propagated everywhere.
> /delete-node/ memory@X shouldn't be needed for new boards.
>
> Ahmad Fatoum (6):
> common: memory: allocate all memory devices at once
> memory: fuse overlapping memory banks
> of: propagate errors inside barebox_register_{of,fdt} into initcalls
> of: warn about of_add_memory_bank errors
> ARM: <asm/memory.h>: propagate error codes from arm_add_mem_device()
> ARM: report probe error at arm_add_mem_device() callsites on failure
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-06-02 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 7:12 Ahmad Fatoum
2021-05-31 7:12 ` [PATCH 1/6] common: memory: allocate all memory devices at once Ahmad Fatoum
2021-05-31 7:12 ` [PATCH 2/6] memory: fuse overlapping memory banks Ahmad Fatoum
2021-05-31 7:12 ` [PATCH 3/6] of: propagate errors inside barebox_register_{of, fdt} into initcalls Ahmad Fatoum
2021-05-31 7:12 ` [PATCH 4/6] of: warn about of_add_memory_bank errors Ahmad Fatoum
2021-05-31 7:12 ` [PATCH 5/6] ARM: <asm/memory.h>: propagate error codes from arm_add_mem_device() Ahmad Fatoum
2021-05-31 7:12 ` [PATCH 6/6] ARM: report probe error at arm_add_mem_device() callsites on failure Ahmad Fatoum
2021-06-02 6:38 ` Sascha Hauer [this message]
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=20210602063827.GV5211@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mol@pengutronix.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