October 2024 - U-Boot

[PATCH 00/21] test: Tidy up the test/ directory
by Simon Glass 02 Nov '24

02 Nov '24

Some tests do not use the unit-test framework. Others are in a suite of their own, for no obvious reason. This series tidies this up. Simon Glass (21): bloblist: test: Move test into common bloblist: test: Drop global_data declarations bloblist: test: doc: Move into the common suite test: Drop test-trace.sh and common.sh compression: test: Move test into lib compression: test: Move into the lib suite command_ut: test: Move test into lib command: test: Move into the cmd suite test: Update command test to use unit-test functions bootm: test: Move test into boot test: Move print_ut test into common test: Move print_ut into the common suite test: Move str_ut test into lib str: test: Move into the lib suite test: Move unicode_ut test into lib test: Move unicode tests into the lib suite test: Move time_ut test into lib test: Move time tests into the lib suite test: Update time tests to use unit-test asserts test: Correct display of failing test test: Quote test names doc/usage/cmd/ut.rst | 29 +++++-- include/test/compression.h | 16 ---- test/Makefile | 10 --- test/boot/Makefile | 1 + test/{ => boot}/bootm.c | 0 test/cmd/Makefile | 1 + test/cmd/command.c | 108 +++++++++++++++++++++++++++ test/cmd_ut.c | 30 +------- test/command_ut.c | 104 -------------------------- test/common.sh | 20 ----- test/common/Makefile | 4 + test/{ => common}/bloblist.c | 47 ++++-------- test/{print_ut.c => common/print.c} | 27 ++----- test/lib/Makefile | 6 ++ test/{ => lib}/compression.c | 39 ++++------ test/{str_ut.c => lib/str.c} | 31 +++----- test/{time_ut.c => lib/time.c} | 60 +++++---------- test/{unicode_ut.c => lib/unicode.c} | 70 +++++++---------- test/test-main.c | 8 +- test/trace/test-trace.sh | 64 ---------------- 20 files changed, 240 insertions(+), 435 deletions(-) delete mode 100644 include/test/compression.h rename test/{ => boot}/bootm.c (100%) create mode 100644 test/cmd/command.c delete mode 100644 test/command_ut.c delete mode 100644 test/common.sh rename test/{ => common}/bloblist.c (93%) rename test/{print_ut.c => common/print.c} (94%) rename test/{ => lib}/compression.c (95%) rename test/{str_ut.c => lib/str.c} (93%) rename test/{time_ut.c => lib/time.c} (56%) rename test/{unicode_ut.c => lib/unicode.c} (92%) delete mode 100755 test/trace/test-trace.sh -- 2.43.0

2 30

[PATCH v7 00/11] labgrid: Provide an integration with Labgrid
by Simon Glass 02 Nov '24

02 Nov '24

Labgrid provides access to a hardware lab in an automated way. It is possible to boot U-Boot on boards in the lab without physically touching them. It relies on relays, USB UARTs and SD muxes, among other things. By way of background, about 4 years ago I wrong a thing called Labman[1] which allowed my lab of about 30 devices to be operated remotely, using tbot for the console and build integration. While it worked OK and I used it for many bisects, I didn't take it any further. It turns out that there was already an existing program, called Labgrid, which I did not know about at time (thank you Tom for telling me). It is more rounded than Labman and has a number of advantages: - does not need udev rules, mostly - has several existing users who rely on it - supports multiple machines exporting their devices It lacks a 'lab check' feature and a few other things, but these can be remedied. On and off over the past several weeks I have been experimenting with Labgrid. I have managed to create an initial U-Boot integration (this series) by adding various features to Labgrid[2] and the U-Boot test hooks. I hope that this might inspire others to set up boards and run tests automatically, rather than relying on infrequent, manual test. Perhaps it may even be possible to have a number of labs available. Included in the integration are a number of simple scripts which make it easy to connect to boards and run tests: ub-int <target> Build and boot on a target, starting an interactive session ub-cli <target> Build and boot on a target, ensure U-Boot starts and provide an interactive session from there ub-smoke <target> Smoke test U-Boot to check that it boots to a prompt on a target ub-bisect <target> Bisect a git tree to locate a failure on a particular target ub-pyt <target> <testspec> Run U-Boot pytests on a target Some of these help to provide the same tbot[4] workflow which I have relied on for several years, albeit much simpler versions. The goal here is to create some sort of script which can collect patches from the mailing list, apply them and test them on a selection of boards. I suspect that script already exists, so please let me know what you suggest. I hope you find this interesting and take a look! [1] https://github.com/sjg20/u-boot/tree/lab6a [2] https://github.com/labgrid-project/labgrid/pull/1411 [3] https://github.com/sjg20/uboot-test-hooks/tree/labgrid [4] https://tbot.tools/index.html Changes in v7: - Rebase on testb series - Expand commit message - Rename option to --use-running-system - Rebase on broken-out testb series Changes in v6: - Rebase without an earlier patch - Avoid doing the special shutdown unless USE_LABGRID is enabled - Drop patch 'test: Pass stderr to stdout' Changes in v5: - Add a few more comments - Comment out the debugging, which might be useful later - Add a patch to support testing with two board-builds Changes in v3: - Split out most patches into two new series and update cover letter Changes in v2: - Only disable echo if a terminal is detected - Avoid running a docker image for skipped lab tests Simon Glass (11): test: Allow signaling that U-Boot is ready test: Release board after tests complete test: Allow connecting to a running board test: Introduce the concept of a role test: Introduce lab mode test: Improve handling of sending commands test: Avoid double echo when starting up test: Try to shut down the lab console gracefully test: Add a section for closing the connection test: Support testing with two board-builds CI: Allow running tests on sjg lab .gitlab-ci.yml | 153 ++++++++++++++++++++++++++ test/py/conftest.py | 73 ++++++++++-- test/py/u_boot_console_base.py | 123 +++++++++++++++------ test/py/u_boot_console_exec_attach.py | 31 ++++-- test/py/u_boot_spawn.py | 36 +++++- 5 files changed, 363 insertions(+), 53 deletions(-) -- 2.34.1

2 42

[PATCH 0/3] Adjust how autoprobe is implemented
by Simon Glass 01 Nov '24

01 Nov '24

This little series makes a minor change to how autoprobe is implemeneted, as discussed on the list. SPL is left out for now, but we can discuss how best to deal with that. Simon Glass (3): common: Drop check for DM in initf_dm() dm: core: Simplify dm_probe_devices() common: Move autoprobe out to board init common/board_f.c | 9 +++++++-- common/board_r.c | 4 ++++ drivers/core/root.c | 27 ++++++++++++++++----------- include/dm/root.h | 10 ++++++++++ 4 files changed, 37 insertions(+), 13 deletions(-) -- 2.43.0

5 10

[PATCH v9 00/11] efi: Add a test for EFI bootmeth
by Simon Glass 01 Nov '24

01 Nov '24

The test coverage for the EFI bootmeth is incomplete since it does not actually boot the application. This series creates a simple test for this purpose. It includes a few patches to make this work: - Revert of an unreviewed patch to change the sandbox efi filename - Hang in sandbox virtio due to EFI probing all block devices Other necessary fixes have already been applied. Changes in v9: - Update license - Fix 'sevices' typo - Move the function into efi_helper.c - Split out into a separate change - Split out into its own patch - Separate into separate patches - Add new patch to drop sandbox PXE architecture - Mark the image as complete after writing it - Fix 'sevices' typo Changes in v8: - Add new patch to control on-host behaviour - Add new patch to move default filename to a function - Add new patch to report host default-filename in native mode - Add new patch to report host default-filename in native mode Changes in v7: - Update commit message - Drop patches already applied - Drop patch 'Disable ANSI output for tests' - Rebase on -master Changes in v6: - Drop the patch to disable sandbox virtio blk with EFI - Add new patch to disable the sandbox virtio blk device - Deal with sandbox CONFIG_LOGF_FUNC - Rebase on -next - Drop patches previously applied - Drop mention of helloworld since it is no-longer used by this test Changes in v4: - Add efi_loader tag to some patches - Split out non-EFI patches into a different series Changes in v2: - Add many new patches to resolve all the outstanding test issues Simon Glass (11): test: boot: Update bootflow_iter() for console checking efi_loader: Add a test app sandbox: Add a -N flag to control on-host behaviour efi: Move default filename to a function efi_loader: Move get_efi_pxe_arch() to efi_helper efi_loader: Allow reporting the host defaults sandbox: Report host default-filename in native mode efi_loader: Drop sandbox PXE architecture sandbox: virtio: Disable the sandbox virtio blk device test: efi: boot: Set up an image suitable for EFI testing test: efi: boot: Add a test for the efi bootmeth arch/Kconfig | 3 +- arch/sandbox/cpu/start.c | 10 ++++ arch/sandbox/dts/test.dts | 2 +- arch/sandbox/include/asm/state.h | 1 + boot/bootmeth_efi.c | 29 ++---------- cmd/efidebug.c | 25 ++++++++++ include/efi.h | 34 +++++++++++++ include/efi_default_filename.h | 56 ---------------------- lib/efi_loader/Kconfig | 10 ++++ lib/efi_loader/Makefile | 1 + lib/efi_loader/efi_bootmgr.c | 10 ++-- lib/efi_loader/efi_helper.c | 71 ++++++++++++++++++++++++++++ lib/efi_loader/testapp.c | 68 ++++++++++++++++++++++++++ test/boot/bootdev.c | 18 ++++++- test/boot/bootflow.c | 71 ++++++++++++++++++++++++++-- test/py/tests/bootstd/flash1.img.xz | Bin 0 -> 4980 bytes test/py/tests/test_ut.py | 53 ++++++++++++++++++--- 17 files changed, 364 insertions(+), 98 deletions(-) delete mode 100644 include/efi_default_filename.h create mode 100644 lib/efi_loader/testapp.c create mode 100644 test/py/tests/bootstd/flash1.img.xz -- 2.43.0

4 22

[PATCH v4 0/2] Add support for Cool Pi GenBook
by Andy Yan 01 Nov '24

01 Nov '24

Support for Cool Pi GenBook is landing Linux 6.12-rc1, so also add the support for u-boot here. Changes in v4: - Fix a underline too short error in rst doc Changes in v3: - Remove upstreamed dt in genbook-u-boot.dtsi - Remove MMC releated config as there is no SD-card on this machine - Enable LED config - Enable rk8xx pmic - rename defconfig to coolpi-cm5-genbook-rk3588_defconfig - redefine BOOT_TARGETS Changes in v2: - Cherry pick it from https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas… - split the dts to a separate commit - rename to genbook_cm5_rk3588 - move readme to doc/board, and write as reStructuredText format - alphabetically reorder - update doc/board/rockchip Andy Yan (2): arm64: dts: rockchip: Add support for rk3588 based Cool Pi CM5 GenBook board: rockchip: Add support for rk3588 GenBook .../dts/rk3588-coolpi-cm5-genbook-u-boot.dtsi | 20 + arch/arm/mach-rockchip/rk3588/Kconfig | 19 + board/coolpi/genbook_cm5_rk3588/Kconfig | 12 + board/coolpi/genbook_cm5_rk3588/MAINTAINERS | 7 + configs/coolpi-cm5-genbook-rk3588_defconfig | 101 +++++ doc/board/coolpi/genbook_cm5_rk3588.rst | 68 ++++ doc/board/coolpi/index.rst | 9 + doc/board/rockchip/rockchip.rst | 1 + .../rockchip/rk3588-coolpi-cm5-genbook.dts | 349 ++++++++++++++++++ include/configs/genbook-cm5-rk3588.h | 31 ++ 10 files changed, 617 insertions(+) create mode 100644 arch/arm/dts/rk3588-coolpi-cm5-genbook-u-boot.dtsi create mode 100644 board/coolpi/genbook_cm5_rk3588/Kconfig create mode 100644 board/coolpi/genbook_cm5_rk3588/MAINTAINERS create mode 100644 configs/coolpi-cm5-genbook-rk3588_defconfig create mode 100644 doc/board/coolpi/genbook_cm5_rk3588.rst create mode 100644 doc/board/coolpi/index.rst create mode 100644 dts/upstream/src/arm64/rockchip/rk3588-coolpi-cm5-genbook.dts create mode 100644 include/configs/genbook-cm5-rk3588.h -- 2.34.1

2 5

[PATCH v1 1/1] rockchip: rock5b-rk3588: Enable automatic PCI enumeration
by Sebastian Reichel 31 Oct '24

31 Oct '24

PCI enumeration is required to detect the onboard Ethernet device. Signed-off-by: Sebastian Reichel <sebastian.reichel(a)collabora.com> --- configs/rock5b-rk3588_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/configs/rock5b-rk3588_defconfig b/configs/rock5b-rk3588_defconfig index c54e13e8732c..e5b9f7d326b4 100644 --- a/configs/rock5b-rk3588_defconfig +++ b/configs/rock5b-rk3588_defconfig @@ -17,6 +17,7 @@ CONFIG_DEBUG_UART_CLOCK=24000000 CONFIG_SPL_SPI_FLASH_SUPPORT=y CONFIG_SPL_SPI=y CONFIG_PCI=y +CONFIG_PCI_INIT_R=y CONFIG_DEBUG_UART=y CONFIG_AHCI=y CONFIG_FIT=y -- 2.45.2

3 5

bios_emulator: how LOG_inpb() is supposed to work on non-x86 systems?
by Yuri Zaporozhets 31 Oct '24

31 Oct '24

Hi all, When trying to compile drivers/bios_emulator for RISC-V, I get a bunch of the following warnings: ================ In file included from drivers/bios_emulator/besys.c:51: drivers/bios_emulator/besys.c: In function ‘BE_inb’: ./arch/riscv/include/asm/io.h:18:43: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 18 | #define __arch_getb(a) (*(volatile unsigned char *)(a)) | ^ ./arch/riscv/include/asm/io.h:33:41: note: in expansion of macro ‘__arch_getb’ 33 | #define __raw_readb(a) __arch_getb(a) | ^~~~~~~~~~~ ./arch/riscv/include/asm/io.h:209:39: note: in expansion of macro ‘__raw_readb’ 209 | #define inb(p) ({ unsigned int __v = __raw_readb(__io(p)); __v; }) | ^~~~~~~~~~~ drivers/bios_emulator/biosemui.h:131:25: note: in expansion of macro ‘inb’ 131 | #define PM_inpb(port) inb(port) | ^~~ drivers/bios_emulator/biosemui.h:138:25: note: in expansion of macro ‘PM_inpb’ 138 | #define LOG_inpb(port) PM_inpb(port) | ^~~~~~~ drivers/bios_emulator/besys.c:572:31: note: in expansion of macro ‘LOG_inpb’ 572 | val = LOG_inpb(port); ================ My question is: how _in principle_ is this supposed to work? On non-x86 systems, the PCI I/O space must always be accessed using some base address (for example, for my PCIe video card it's 0x60080000). In the sequence above (inb -> __raw_readb -> __arch_getb) I do not see such base address at all. Previously, there was a constant VIDEO_IO_OFFSET added to the port (see 70f2030f02696ee1820d8df690e878de078b01b3), but it was removed completely. In arch/riscv/include/asm/io.h, the I/O primitives are defined as: #define inb(p) ({ unsigned int __v = __raw_readb(__io(p)); __v; }) where the __io() macro seems to be an excellent thing to account for the I/O base address. I would expect that the driver that uses PCI I/O defines something like: #define __io(port) (base_addr + port) where base_addr is a runtime variable. But instead both bios.c and besys.c have just "#define __io", without any parameters. I am totally puzzled. I would be grateful for any clarification how this code was supposed to work in the first place. P.S. Simon, adding you to CC: since you were working on this code in the past. Thanks in advance. -- Regards, Yuri

1 0

[PATCH] mtd: spi-nor: Guard SPI_STACKED_PARALLEL with DM_SPI check
by Tom Rini 31 Oct '24

31 Oct '24

While we want to compile the SPI_STACKED_PARALLEL code everywhere we can, it must first be guarded with an #if for DM_SPI as not all cases where we have this code built, such as in SPL, will have the relevant DM_SPI option enabled. Fixes: 43423cdc5dc1 ("mtd: spi-nor: Always build SPI_STACKED_PARALLEL code") Signed-off-by: Tom Rini <trini(a)konsulko.com> --- drivers/mtd/spi/spi-nor-core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/mtd/spi/spi-nor-core.c b/drivers/mtd/spi/spi-nor-core.c index a3a62fff213e..ec841fb13bd4 100644 --- a/drivers/mtd/spi/spi-nor-core.c +++ b/drivers/mtd/spi/spi-nor-core.c @@ -3166,6 +3166,7 @@ static int spi_nor_init_params(struct spi_nor *nor, spi_nor_post_sfdp_fixups(nor, params); } +#if CONFIG_IS_ENABLED(DM_SPI) if (CONFIG_IS_ENABLED(SPI_STACKED_PARALLEL)) { u64 flash_size[SNOR_FLASH_CNT_MAX] = { 0 }; struct udevice *dev = nor->spi->dev; @@ -3227,6 +3228,7 @@ static int spi_nor_init_params(struct spi_nor *nor, params->page_size <<= 1; } } +#endif spi_nor_late_init_fixups(nor, params); -- 2.43.0

2 3

[PATCH 00/34] bootstd: Support recording images
by Simon Glass 31 Oct '24

31 Oct '24

This series provides a way to keep track of the images used in bootstd, including the type of each image. At present this is sort-of handled by struct bootflow but in quite an ad-hoc way. The structure has become quite large and is hard to query. Future work will be able to reduce its size. Ultimately the 'bootflow info' command may change to also show images as a list, but that is left for later, as this series is already fairly long. So for now, just introduce the concept and adjust bootstd to use it, with a simple command to list the images. This series includes various alist enhancements, to make use of this new data structure a little easier. Simon Glass (34): alist: Mention the error condition in alist_add_placeholder() alist: Add a comment for alist_init_struct() alist: Expand the comment for alist_get() alist: Add a way to get the next element alist: Add for-loop helpers alist: Add a function to empty the list alist: Add a way to efficiently filter an alist dm: core: Add a function to see if a device exists test: boot: Use a consistent name for the script bootmeth bootstd: Move bootflow-adding to bootstd bootstd: Move bootflow-clearing to bootstd bootstd: Add a function to get bootstd only if available bootstd: Drop the bootdev-specific list of bootflows bootstd: Move the bootflow list into an alist image: Add a new type for extlinux image: Add a new type for EFI apps image: Add a new type for logo images image: Add a new type for a command-line string test: Expand implementation of ut_list_has_dm_tests() test: Drop the duplicate line in setup_bootmenu_image() test: boot: Update bootflow_iter() for console checking bootstd: cros: Correct the x86-setup address bootstd: Maintain a list of images bootstd: Update bootmeth_alloc_file() to record images boot: pxe: Drop the duplicate comment on get_pxe_file() efi: Simplify reading files by using the common function bootmeth: Update the read_file() method to include a type efi: Check the filename-allocation in the network path boot: Update extlinux pxe_getfile_func() to include type boot: Update pxe bootmeth to record images Update bootmeth_alloc_other() to record images bootstd: Avoid showing an invalid buffer address bootstd: Update cros bootmeth to record images bootstd: Add a simple command to list images boot/bootdev-uclass.c | 76 +++------- boot/bootflow.c | 37 +++-- boot/bootmeth-uclass.c | 54 ++++++- boot/bootmeth_android.c | 3 +- boot/bootmeth_cros.c | 33 +++- boot/bootmeth_efi.c | 16 +- boot/bootmeth_efi_mgr.c | 3 +- boot/bootmeth_extlinux.c | 7 +- boot/bootmeth_pxe.c | 21 ++- boot/bootmeth_qfw.c | 3 +- boot/bootmeth_sandbox.c | 3 +- boot/bootmeth_script.c | 7 +- boot/bootstd-uclass.c | 59 ++++++- boot/image.c | 4 + boot/pxe_utils.c | 36 ++--- boot/vbe_simple.c | 5 +- cmd/Kconfig | 9 ++ cmd/Makefile | 1 + cmd/bootdev.c | 2 +- cmd/bootflow.c | 13 +- cmd/bootstd.c | 65 ++++++++ cmd/pxe.c | 2 +- cmd/sysboot.c | 6 +- doc/develop/bootstd/overview.rst | 21 ++- doc/usage/cmd/bootstd.rst | 79 ++++++++++ doc/usage/index.rst | 1 + drivers/core/uclass.c | 11 ++ include/alist.h | 139 ++++++++++++++++- include/bootdev.h | 27 ---- include/bootflow.h | 44 ++++-- include/bootmeth.h | 20 ++- include/bootstd.h | 50 +++++- include/dm/uclass.h | 11 ++ include/image.h | 4 + include/pxe_utils.h | 14 +- lib/alist.c | 41 +++++ test/boot/bootflow.c | 110 +++++++++++++- test/dm/core.c | 22 +++ test/lib/alist.c | 253 +++++++++++++++++++++++++++++++ test/py/tests/test_ut.py | 5 +- test/test-main.c | 18 ++- 41 files changed, 1143 insertions(+), 192 deletions(-) create mode 100644 cmd/bootstd.c create mode 100644 doc/usage/cmd/bootstd.rst -- 2.34.1

4 59

[PATCH v2 00/13] boards: siemens: iot2050: SM variant, sysinfo support, fixes & cleanups
by Jan Kiszka 31 Oct '24

31 Oct '24

Changes in v2: - rebased over master, adding the missing 6.12 cherry-picks from devicetree-rebasing This adds support for the new IOT2050 SM variant, introduces a sysinfo driver which also permits SMBIOS support and switches the board to OF_UPSTREAM. There are some further fixes for the boards included as well. Not yet included is configuration support for DMA isolation via the PVU as this depends on not yet merged DT bindings and another overlay. Jan CC: Baocheng Su <baocheng.su(a)siemens.com> CC: Li Hua Qian <huaqian.li(a)siemens.com> Baocheng Su (5): board: siemens: iot2050: Fix coding style board: siemens: iot2050: Control pcie power for all variants board: siemens: iot2050: Pass DDR size from FSBL board: siemens: iot2050: Generalize the fdt fixup board: iot2050: Support new IOT2050-SM variant Jan Kiszka (5): board: siemens: iot2050: Fix mistake in list of writable env vars board: siemens: iot2050: Stop using special spl DT sources arm64: dts: ti: iot2050: Add overlays for M.2 used by firmware board: siemens: iot2050: Migrate to OF_UPSTREAM smbios: Fill UUID from sysinfo when available Li Hua Qian (3): arm64: dts: ti: iot2050: Disable lock-step for all iot2050 boards sysinfo: Add driver for IOT2050 boards board: siemens: iot2050: Use sysinfo for board initialization arch/arm/dts/Makefile | 8 - arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 19 +- arch/arm/dts/k3-am65-iot2050-common-pg1.dtsi | 46 -- arch/arm/dts/k3-am65-iot2050-common-pg2.dtsi | 51 -- .../dts/k3-am65-iot2050-common-u-boot.dtsi | 18 + arch/arm/dts/k3-am65-iot2050-common.dtsi | 738 ------------------ arch/arm/dts/k3-am65-iot2050-spl.dts | 17 - .../dts/k3-am6528-iot2050-basic-common.dtsi | 61 -- arch/arm/dts/k3-am6528-iot2050-basic-pg2.dts | 24 - arch/arm/dts/k3-am6528-iot2050-basic.dts | 24 - .../k3-am6548-iot2050-advanced-common.dtsi | 52 -- .../arm/dts/k3-am6548-iot2050-advanced-m2.dts | 119 --- .../dts/k3-am6548-iot2050-advanced-pg2.dts | 29 - .../k3-am6548-iot2050-advanced-sm-u-boot.dtsi | 1 + arch/arm/dts/k3-am6548-iot2050-advanced.dts | 24 - arch/arm/mach-k3/am65x/Kconfig | 2 + board/siemens/iot2050/board.c | 226 ++++-- configs/iot2050_defconfig | 7 +- doc/board/siemens/iot2050.rst | 7 +- drivers/sysinfo/Kconfig | 7 + drivers/sysinfo/Makefile | 1 + drivers/sysinfo/iot2050.c | 143 ++++ drivers/sysinfo/iot2050.h | 26 + .../arm64/ti/k3-am65-iot2050-common-pg2.dtsi | 5 - .../src/arm64/ti/k3-am65-iot2050-common.dtsi | 5 + .../src/arm64/ti/k3-am6528-iot2050-basic.dts | 5 - ...48-iot2050-advanced-m2-bkey-ekey-pcie.dtso | 2 +- ...-am6548-iot2050-advanced-m2-bkey-usb3.dtso | 2 +- include/configs/iot2050.h | 5 +- include/sysinfo.h | 1 + lib/smbios.c | 4 + 31 files changed, 379 insertions(+), 1300 deletions(-) delete mode 100644 arch/arm/dts/k3-am65-iot2050-common-pg1.dtsi delete mode 100644 arch/arm/dts/k3-am65-iot2050-common-pg2.dtsi delete mode 100644 arch/arm/dts/k3-am65-iot2050-common.dtsi delete mode 100644 arch/arm/dts/k3-am65-iot2050-spl.dts delete mode 100644 arch/arm/dts/k3-am6528-iot2050-basic-common.dtsi delete mode 100644 arch/arm/dts/k3-am6528-iot2050-basic-pg2.dts delete mode 100644 arch/arm/dts/k3-am6528-iot2050-basic.dts delete mode 100644 arch/arm/dts/k3-am6548-iot2050-advanced-common.dtsi delete mode 100644 arch/arm/dts/k3-am6548-iot2050-advanced-m2.dts delete mode 100644 arch/arm/dts/k3-am6548-iot2050-advanced-pg2.dts create mode 120000 arch/arm/dts/k3-am6548-iot2050-advanced-sm-u-boot.dtsi delete mode 100644 arch/arm/dts/k3-am6548-iot2050-advanced.dts create mode 100644 drivers/sysinfo/iot2050.c create mode 100644 drivers/sysinfo/iot2050.h rename arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso => dts/upstream/src/arm64/ti/k3-am6548-iot2050-advanced-m2-bkey-ekey-pcie.dtso (92%) rename arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso => dts/upstream/src/arm64/ti/k3-am6548-iot2050-advanced-m2-bkey-usb3.dtso (96%) -- 2.43.0

3 29