Files
u-boot/cmd
Tom Rini 47e544f576 Merge patch series "Tidy up use of 'SPL' and CONFIG_SPL_BUILD"
Simon Glass <sjg@chromium.org> says:

When the SPL build-phase was first created it was designed to solve a
particular problem (the need to init SDRAM so that U-Boot proper could
be loaded). It has since expanded to become an important part of U-Boot,
with three phases now present: TPL, VPL and SPL

Due to this history, the term 'SPL' is used to mean both a particular
phase (the one before U-Boot proper) and all the non-proper phases.
This has become confusing.

For a similar reason CONFIG_SPL_BUILD is set to 'y' for all 'SPL'
phases, not just SPL. So code which can only be compiled for actual SPL,
for example, must use something like this:

   #if defined(CONFIG_SPL_BUILD) && !defined(CONFIG_TPL_BUILD)

In Makefiles we have similar issues. SPL_ has been used as a variable
which expands to either SPL_ or nothing, to chose between options like
CONFIG_BLK and CONFIG_SPL_BLK. When TPL appeared, a new SPL_TPL variable
was created which expanded to 'SPL_', 'TPL_' or nothing. Later it was
updated to support 'VPL_' as well.

This series starts a change in terminology and usage to resolve the
above issues:

- The word 'xPL' is used instead of 'SPL' to mean a non-proper build
- A new CONFIG_XPL_BUILD define indicates that the current build is an
  'xPL' build
- The existing CONFIG_SPL_BUILD is changed to mean SPL; it is not now
  defined for TPL and VPL phases
- The existing SPL_ Makefile variable is renamed to SPL_
- The existing SPL_TPL Makefile variable is renamed to PHASE_

It should be noted that xpl_phase() can generally be used instead of
the above CONFIGs without a code-space or run-time penalty.

This series does not attempt to convert all of U-Boot to use this new
terminology but it makes a start. In particular, renaming spl.h and
common/spl seems like a bridge too far at this point.

The series is fully bisectable. It has also been checked to ensure there
are no code-size changes on any commit.
2024-10-11 12:23:25 -06:00
..
2024-09-12 17:35:37 +02:00
2024-07-15 12:12:17 -06:00
2024-02-15 10:38:34 +01:00
2024-10-02 13:32:56 -06:00
2024-07-15 12:12:17 -06:00
2024-07-15 12:12:17 -06:00
2024-10-09 22:04:56 -06:00
2024-07-15 12:12:17 -06:00
2024-08-02 15:16:51 -03:00
2024-07-15 12:12:17 -06:00
2024-08-13 06:12:40 +02:00
2024-09-12 17:35:37 +02:00
2024-09-12 17:35:37 +02:00
2024-10-07 21:31:22 -06:00
2022-03-15 16:19:29 -04:00
2024-07-15 12:12:17 -06:00
2024-09-12 17:35:37 +02:00
2024-07-15 12:12:17 -06:00
2024-09-12 17:35:37 +02:00
2024-08-13 06:23:05 +02:00
2024-10-11 11:44:48 -06:00
2024-03-07 09:23:10 -05:00
2024-09-18 13:01:00 -06:00
2024-09-18 13:07:19 -06:00
2024-07-15 12:12:17 -06:00
2024-10-10 16:02:20 -06:00
2024-07-15 12:12:17 -06:00
2024-07-15 12:12:17 -06:00
2024-09-12 17:35:37 +02:00
2024-05-22 08:55:29 -06:00
2022-09-02 13:40:42 -04:00
2024-08-26 14:05:38 -06:00
2024-06-24 13:34:52 -06:00
2024-07-15 12:12:17 -06:00
2020-08-07 22:31:32 -04:00
2024-07-15 12:12:17 -06:00
2024-07-15 12:12:17 -06:00
2024-06-04 08:09:09 -06:00
2024-10-10 16:02:20 -06:00
2024-07-15 12:12:17 -06:00
2024-07-15 12:12:17 -06:00
2024-08-09 16:03:20 -06:00
2024-09-18 13:00:59 -06:00
2024-07-15 12:12:17 -06:00
2024-07-15 12:12:17 -06:00
2024-07-15 12:12:17 -06:00