From: Devarsh Thakkar <devarsht@ti.com>
To: <u-boot@lists.denx.de>, <sjg@chromium.org>, <agust@denx.de>,
<trini@konsulko.com>, <bmeng.cn@gmail.com>, <msuchanek@suse.de>,
<rasmus.villemoes@prevas.dk>, <yangshiji66@outlook.com>
Cc: <praneeth@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<a-bhatia1@ti.com>, <j-luthra@ti.com>, <nsekhar@ti.com>,
<n-jain1@ti.com>, <devarsht@ti.com>
Subject: [PATCH v2 6/6] doc: spl: Add info regarding memory reservation and missing Kconfigs
Date: Fri, 10 Nov 2023 20:59:44 +0530 [thread overview]
Message-ID: <20231110152944.647535-7-devarsht@ti.com> (raw)
In-Reply-To: <20231110152944.647535-1-devarsht@ti.com>
Add information regarding memory reservation scheme in SPL
and details regarding scheme which need to be followed while reserving
those areas which need to be preserved across bootstages.
Also add missing CONFIG_SPL Kconfigs and new ones which were added
recently.
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
---
V1->V3 : No change
---
doc/develop/spl.rst | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/doc/develop/spl.rst b/doc/develop/spl.rst
index 76e87f07c7..fc570589eb 100644
--- a/doc/develop/spl.rst
+++ b/doc/develop/spl.rst
@@ -65,6 +65,15 @@ CONFIG_SPL_NAND_LOAD (drivers/mtd/nand/raw/nand_spl_load.o)
CONFIG_SPL_SPI_LOAD (drivers/mtd/spi/spi_spl_load.o)
CONFIG_SPL_RAM_DEVICE (common/spl/spl.c)
CONFIG_SPL_WATCHDOG (drivers/watchdog/libwatchdog.o)
+CONFIG_SPL_SYSCON (drivers/core/syscon-uclass.o)
+CONFIG_SPL_GZIP (lib/gzip.o)
+CONFIG_SPL_VIDEO (drivers/video/video-uclass.o drivers/video/vidconsole-uclass.o)
+CONFIG_SPL_SPLASH_SCREEN (common/splash.o)
+CONFIG_SPL_SPLASH_SOURCE (common/splash_source.o)
+CONFIG_SPL_GPIO (drivers/gpio)
+CONFIG_SPL_DM_GPIO (drivers/gpio/gpio-uclass.o)
+CONFIG_SPL_BMP (drivers/video/bmp.o)
+CONFIG_SPL_BLOBLIST (common/bloblist.o)
Adding SPL-specific code
------------------------
@@ -164,3 +173,16 @@ cflow will spit out a number of warnings as it does not parse
the config files and picks functions based on #ifdef. Parsing the '.i'
files instead introduces another set of headaches. These warnings are
not usually important to understanding the flow, however.
+
+
+Reserving memory in SPL
+-----------------------
+
+If memory need to be reserved in RAM during SPL stage so that area won't get touched
+by SPL and/or u-boot, it need to be reserved starting from end of RAM.
+
+Also the regions which are to be preserved across further stages of boot need to be reserved first starting from
+framebuffer memory which must be reserved from end of RAM for which helper function spl_reserve_video_from_ram_top is provided.
+
+The corresponding information of reservation for those regions can be passed to further stages of boot using a bloblist.
+For e.g. the information for framebuffer area reserved by SPL can be passed onto u-boot using BLOBLISTT_U_BOOT_VIDEO.
--
2.34.1
next prev parent reply other threads:[~2023-11-10 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 15:29 [PATCH v2 0/6] Move framebuffer reservation for SPL to RAM end Devarsh Thakkar
2023-11-10 15:29 ` [PATCH v2 1/6] arm: mach-k3: common: Reserve video memory from end of the RAM Devarsh Thakkar
2023-11-12 20:01 ` Simon Glass
2023-12-05 11:33 ` Nikhil Jain
2023-11-10 15:29 ` [PATCH v2 2/6] board: ti: am62x: evm: Remove video_setup from spl_board_init Devarsh Thakkar
2023-11-12 20:01 ` Simon Glass
2023-11-10 15:29 ` [PATCH v2 3/6] common/board_f: Catch bloblist before starting resevations Devarsh Thakkar
2023-11-12 20:01 ` Simon Glass
2023-11-10 15:29 ` [PATCH v2 4/6] video: Skip framebuffer reservation if already reserved Devarsh Thakkar
2023-11-12 20:01 ` Simon Glass
2023-11-10 15:29 ` [PATCH v2 5/6] video: Fill video handoff in video post probe Devarsh Thakkar
2023-11-12 20:01 ` Simon Glass
2023-11-25 14:27 ` Devarsh Thakkar
2023-12-02 18:23 ` Simon Glass
2023-12-05 10:11 ` Devarsh Thakkar
2023-11-10 15:29 ` Devarsh Thakkar [this message]
2023-11-12 20:01 ` [PATCH v2 6/6] doc: spl: Add info regarding memory reservation and missing Kconfigs Simon Glass
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=20231110152944.647535-7-devarsht@ti.com \
--to=devarsht@ti.com \
--cc=a-bhatia1@ti.com \
--cc=agust@denx.de \
--cc=bmeng.cn@gmail.com \
--cc=j-luthra@ti.com \
--cc=msuchanek@suse.de \
--cc=n-jain1@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=praneeth@ti.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=yangshiji66@outlook.com \
/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