From: Marek Szyprowski <m.szyprowski@samsung.com>
To: linux-mm@kvack.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Mike Rapoport <rppt@kernel.org>, Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Oreoluwa Babatunde <oreoluwa.babatunde@oss.qualcomm.com>,
Wandun <chenwandun1@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v2 0/2] of: reserved_mem: use dynamically allocated reserved_mem array
Date: Thu, 8 Oct 2026 17:23:59 +0200 [thread overview]
Message-ID: <20261008152403.766439-1-m.szyprowski@samsung.com> (raw)
In-Reply-To: CGME20261008152449eucas1p29758be26c325084093c14cfa9b8b2d04@eucas1p2.samsung.com
Mike Rapoport suggested [1] how to properly use dynamically allocated
arrays during early boot.
Use this approach for reserved_mem array during early scan of the
reserved regions. Having all the reserved regions in a single array
removes the need of the two pass initialization introduced by commit
8a6e02d0c00e ("of: reserved_mem: Restructure how the reserved memory
regions are processed"), so implement it to make the code simpler,
easier to understand and ready for adding proper error checking.
Tested on ARM32, ARM64 and RiscV64 based boards.
[1] https://lore.kernel.org/all/asc6brs_g0ky0wOM@kernel.org/
Best regards
Marek Szyprowski, PhD
Samsung R&D Institute Poland
Changelog:
v2:
- removed superfluous ifdefs
v1: https://lore.kernel.org/all/20261008094125.3197971-1-m.szyprowski@samsung.com/
- initial version
Patch summary:
Marek Szyprowski (2):
of: reserved_mem: group allocation helpers together
of: reserved_mem: allocate and map the reserved_mem array early
drivers/of/fdt.c | 3 -
drivers/of/of_private.h | 2 -
drivers/of/of_reserved_mem.c | 455 +++++++++++++++--------------------
3 files changed, 195 insertions(+), 265 deletions(-)
--
2.43.0
next parent reply other threads:[~2026-10-08 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261008152449eucas1p29758be26c325084093c14cfa9b8b2d04@eucas1p2.samsung.com>
2026-10-08 15:23 ` Marek Szyprowski [this message]
2026-10-08 15:24 ` [PATCH v2 1/2] of: reserved_mem: group allocation helpers together Marek Szyprowski
2026-10-08 15:24 ` [PATCH v2 2/2] of: reserved_mem: allocate and map the reserved_mem array early Marek Szyprowski
2026-10-08 15:35 ` sashiko-bot
2026-10-09 2:16 ` Wandun
2026-10-09 11:27 ` Marek Szyprowski
2026-10-09 5:20 ` kernel test robot
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=20261008152403.766439-1-m.szyprowski@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=chenwandun1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oreoluwa.babatunde@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=saravanak@kernel.org \
/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