From: Jerome Forissier <jerome.forissier@linaro.org>
To: u-boot@lists.denx.de
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Michal Simek <michal.simek@amd.com>,
Jerome Forissier <jerome.forissier@linaro.org>
Subject: [PATCH v2 0/5] Static initcalls
Date: Wed, 18 Dec 2024 16:53:53 +0100 [thread overview]
Message-ID: <cover.1734537135.git.jerome.forissier@linaro.org> (raw)
This series replaces the dynamic initcalls (with function pointers) with
static calls, and gets rid of initcall_run_list(), init_sequence_f,
init_sequence_f_r and init_sequence_r. This makes the code simpler and the
binary slighlty smaller: -2507 bytes/-0.23 % with LTO enabled and -1232
bytes/-0.11 % with LTO disabled (xilinx_zynqmp_kria_defconfig).
Execution time doesn't seem to change noticeably. There is no impact on
the SPL.
Changes in v2:
- INTICALL() and INITCALL_EVT() now call hang() immediately on error
- Fixed typo: s/intcall_run_f_r/initcall_run_f_r/
Jerome Forissier (4):
board_init_f(): use static calls
board_init_f_r(): use static calls
board_init_r(): use static calls
initcall: remove initcall_run_list()
Michal Simek (1):
common: board: Simplify array with function pointers with
CONFIG_IS_ENABLED
common/board_f.c | 210 ++++++++++++++-----------------
common/board_r.c | 241 ++++++++++++++----------------------
include/initcall.h | 45 +++----
lib/Makefile | 1 -
lib/initcall.c | 102 ---------------
test/py/tests/test_trace.py | 8 +-
6 files changed, 210 insertions(+), 397 deletions(-)
delete mode 100644 lib/initcall.c
--
2.43.0
next reply other threads:[~2024-12-18 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 15:53 Jerome Forissier [this message]
2024-12-18 15:53 ` [PATCH v2 1/5] common: board: Simplify array with function pointers with CONFIG_IS_ENABLED Jerome Forissier
2024-12-18 15:53 ` [PATCH v2 2/5] board_init_f(): use static calls Jerome Forissier
2024-12-18 17:27 ` Quentin Schulz
2024-12-18 17:38 ` Jerome Forissier
2024-12-18 17:47 ` Quentin Schulz
2024-12-18 18:21 ` Jerome Forissier
2024-12-21 8:10 ` Ilias Apalodimas
2024-12-21 12:08 ` Jerome Forissier
2024-12-18 15:53 ` [PATCH v2 3/5] board_init_f_r(): " Jerome Forissier
2024-12-21 8:14 ` Ilias Apalodimas
2024-12-18 15:53 ` [PATCH v2 4/5] board_init_r(): " Jerome Forissier
2024-12-18 15:53 ` [PATCH v2 5/5] initcall: remove initcall_run_list() Jerome Forissier
2025-01-01 17:55 ` [PATCH v2 0/5] Static initcalls Tom Rini
2025-01-03 1:41 ` Simon Glass
2025-01-03 8:49 ` Jerome Forissier
2025-01-03 8:47 ` Jerome Forissier
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=cover.1734537135.git.jerome.forissier@linaro.org \
--to=jerome.forissier@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=michal.simek@amd.com \
--cc=sjg@chromium.org \
--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