u-boot.git/test/cmd, branch v2025.10

test: cmd: Add simple test for i3c

2025-08-06T06:41:52+00:00

Add simple test to check i3c controller defined in sandbox test DT.
Basically, this test case will check validity of the i3c controller
by probing it and perform basic commands of cmd/i3c.c

Signed-off-by: Dinesh Maniyam

test: wget: add a test case for validating URI

2025-07-03T08:34:20+00:00

The wget module has a function wget_validate_uri() which is used for
validating the URI to be used by wget. Add a basic test case for this
function.

Signed-off-by: Sughosh Ganu 
Reviewed-by: Heinrich Schuchardt 
Reviewed-by: Ilias Apalodimas 
Signed-off-by: Ilias Apalodimas

global: Avoid indirect inclusion of from

2025-05-29T14:29:16+00:00

The include file  does not need anything from .
Furthermore, include/env.h itself includes other headers which can lead
to longer indirect inclusion paths. To prepare to remove  from
 fix all of the places which had relied on this indirect
inclusion to instead include  directly.

Reviewed-by: Mattijs Korpershoek  # android, bcb
Reviewed-by: Jerome Forissier  # spawn
Signed-off-by: Tom Rini

cmd/mem.c, test/cmd/mem_copy.c: Add

2025-05-29T14:29:16+00:00

These files require  in order to have MEM_SUPPORT_64BIT_DATA
be defined but currently rely on a long indirect include path to get it.
Add this directly.

Signed-off-by: Tom Rini

Merge patch series "Uthreads"

2025-04-23T19:21:39+00:00

Jerome Forissier  says:

This series introduces threads and uses them to improve the performance
of the USB bus scanning code and to implement background jobs in the
shell via two new commands: 'spawn' and 'wait'.

The threading framework is called 'uthread' and is inspired from the
barebox threads [2]. setjmp() and longjmp() are used to save and
restore contexts, as well as a non-standard extension called initjmp().
This new function is added in several patches, one for each
architecture that supports HAVE_SETJMP. A new symbol is defined:
HAVE_INITJMP. Two tests, one for initjmp() and one for the uthread
scheduling, are added to the lib suite.

After introducing threads and making schedule() and udelay() a thread
re-scheduling point, the USB stack initialization is modified to benefit
from concurrency when UTHREAD is enabled, where uthreads are used in
usb_init() to initialize and scan multiple busses at the same time.
The code was tested on arm64 and arm QEMU with 4 simulated XHCI buses
and some devices. On this platform the USB scan takes 2.2 s instead of
5.6 s. Tested on i.MX93 EVK with two USB hubs, one ethernet adapter and
one webcam on each, "usb start" takes 2.4 s instead of 4.6 s.

Finally, the spawn and wait commands are introduced, allowing the use of
threads from the shell. Tested on the i.MX93 EVK with a spinning HDD
connected to USB1 and the network connected to ENET1. The USB plus DHCP
init sequence "spawn usb start; spawn dhcp; wait" takes 4.5 seconds
instead of 8 seconds for "usb start; dhcp".

[1] https://patchwork.ozlabs.org/project/uboot/list/?series=446674
[2] https://github.com/barebox/barebox/blob/master/common/bthread.c

Link: https://lore.kernel.org/r/20250418141114.2056981-1-jerome.forissier@linaro.org

test: cmd: add test for spawn and wait commands

2025-04-23T19:19:44+00:00

Test the spawn and wait commands.

Signed-off-by: Jerome Forissier 
Acked-by: Ilias Apalodimas

test: run some test commands only if HUSH_PARSER is enabled

2025-04-22T18:26:41+00:00

Some test commands (such as "false", or the empty string) need
CONFIG_HUSH_PARSER=y. Fix test/cmd/command.c.

Signed-off-by: Jerome Forissier

Kbuild: Always use $(PHASE_)

2025-04-11T18:16:44+00:00

It is confusing to have both "$(PHASE_)" and "$(XPL_)" be used in our
Makefiles as part of the macros to determine when to do something in our
Makefiles based on what phase of the build we are in. For consistency,
bring this down to a single macro and use "$(PHASE_)" only.

Signed-off-by: Tom Rini

test: Drop suites.h

2025-02-12T02:12:36+00:00

This file is empty now. Remove it and its uses.

Signed-off-by: Simon Glass

cmd/setexpr: support concatenation of direct strings

2025-02-07T19:35:23+00:00

The setexpr.s command allows to concatenate two strings.

According to the description in doc/usage/cmd/setexpr.rst the parameters
value1 and value2 can be either direct values or pointers to a
memory location holding the values.

Unfortunately `setexpr.s  + ` fails if any of the values
is a direct value. $? is set to false.

* Add support for direct values in setexpr.s.
* Correct the unit test for "setexpr.s fred 0".
* Add a new unit test for "setexpr.s fred '1' + '3'" giving '13'.

Signed-off-by: Heinrich Schuchardt