u-boot.git/test/boot/bootdev.c, branch v2024.10

test: Remove duplicate newlines

2024-07-15T18:12:18+00:00

Drop all duplicate newlines. No functional change.

Signed-off-by: Marek Vasut

Restore patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"

2024-05-20T19:35:03+00:00

As part of bringing the master branch back in to next, we need to allow
for all of these changes to exist here.

Reported-by: Jonas Karlman 
Signed-off-by: Tom Rini

Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet""

2024-05-19T14:16:36+00:00

When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay
Ethernet"' I failed to notice that b4 noticed it was based on next and
so took that as the base commit and merged that part of next to master.

This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing
changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35.

Reported-by: Jonas Karlman 
Signed-off-by: Tom Rini

test: Remove and add needed includes

2024-05-06T21:05:04+00:00

Remove  from all "test/" files and when needed add
missing include files directly.

Signed-off-by: Tom Rini

bootstd: Scan all bootdevs in a boot_targets entry (take 2)

2023-10-23T17:05:13+00:00

When the boot_targets environment variable is used with the distro-boot
scripts, each device is included individually. For example, if there
are three mmc devices, then we will have something like:

   boot_targets="mmc0 mmc1 mmc2"

In contrast, standard boot supports specifying just the uclass, i.e.:

   boot_targets="mmc"

The intention is that this should scan all MMC devices, but in fact it
currently only scans the first.

Update the logic to handle this case, without required BOOTSTD_FULL to
be enabled.

Signed-off-by: Simon Glass 
Reported-by: Date Huang 
Reported-by: Vincent Stehlé 
Reported-by: Ivan Ivanov 
Tested-by: Ivan T.Ivanov

bootstd: Correct logic for single uclass

2023-10-23T17:05:13+00:00

The current logic for "bootflow mmc" is flawed since it checks the
uclass of the bootdev instead of its parent, the media device. Correct
this and add a test that covers this scenario.

Signed-off-by: Simon Glass 
Tested-by: Ivan T.Ivanov

bootstd: Expand boot-ordering test to include USB

2023-10-23T17:05:13+00:00

Scan the USB bus as well, so we can check that different uclasses work
correctly in boot_targets

update the function comment with more detail.

Signed-off-by: Simon Glass 
Tested-by: Ivan T.Ivanov

Revert "bootstd: Scan all bootdevs in a boot_targets entry"

2023-10-23T17:05:13+00:00

This commit was intended to allow all bootdevs in each boot_targets
entry to be scanned. However it causes bad ordering with bootdevs, e.g.
scanning Ethernet bootdevs when it should be keeping to mmc.

Revert it so we can try another approach.

This reverts commit e824d0d0c219bc6da767f13f90c5b00eefe929f0.

Signed-off-by: Simon Glass 
Tested-by: Ivan T.Ivanov

bootstd: Scan all bootdevs in a boot_targets entry

2023-10-13T17:15:41+00:00

When the boot_targets environment variable is used with the distro-boot
scripts, each device is included individually. For example, if there
are three mmc devices, then we will have something like:

   boot_targets="mmc0 mmc1 mmc2"

In contrast, standard boot supports specifying just the uclass, i.e.:

   boot_targets="mmc"

The intention is that this should scan all MMC devices, but in fact it
currently only scans the first.

Update the logic to handle this case, without required BOOTSTD_FULL to
be enabled.

I believe at least three people reported this, but I found two.

Signed-off-by: Simon Glass 
Reported-by: Date Huang 
Reported-by: Vincent Stehlé

bootstd: usb: Avoid initing USB twice

2023-05-13T13:52:32+00:00

This causes crashes on some boards, e.g. rockpro64. In any case, we
should not do it.

Check the usb_started flag to avoid this.

Signed-off-by: Simon Glass 
Tested-by: Jonas Karlman 
Tested-by: Tom Rini