U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 0/5] Static initcalls
Date: Tue, 17 Dec 2024 16:59:31 +0100	[thread overview]
Message-ID: <cover.1734448827.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: -2655 bytes/-0.25 % with LTO enabled and -1344
bytes/-0.12 % with LTO disabled (xilinx_zynqmp_kria_defconfig).

Execution time doesn't seem to change noticeably. There is no impact on
the SPL.

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            | 213 +++++++++++++++----------------
 common/board_r.c            | 244 ++++++++++++++----------------------
 include/initcall.h          |  43 +++----
 lib/Makefile                |   1 -
 lib/initcall.c              | 102 ---------------
 test/py/tests/test_trace.py |   8 +-
 6 files changed, 218 insertions(+), 393 deletions(-)
 delete mode 100644 lib/initcall.c

-- 
2.43.0


             reply	other threads:[~2024-12-17 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 15:59 Jerome Forissier [this message]
2024-12-17 15:59 ` [PATCH 1/5] common: board: Simplify array with function pointers with CONFIG_IS_ENABLED Jerome Forissier
2024-12-18 12:03   ` Ilias Apalodimas
2024-12-18 12:15     ` Ilias Apalodimas
2024-12-18 12:28       ` Jerome Forissier
2024-12-18 12:15     ` Jerome Forissier
2024-12-18 12:27       ` Ilias Apalodimas
2024-12-17 15:59 ` [PATCH 2/5] board_init_f(): use static calls Jerome Forissier
2024-12-18 12:38   ` Ilias Apalodimas
2024-12-18 14:02     ` Jerome Forissier
2024-12-17 15:59 ` [PATCH 3/5] board_init_f_r(): " Jerome Forissier
2024-12-17 15:59 ` [PATCH 4/5] board_init_r(): " Jerome Forissier
2024-12-17 15:59 ` [PATCH 5/5] initcall: remove initcall_run_list() 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.1734448827.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