February 2024 - U-Boot

[PATCH] MAINTAINERS: Update after GEHC spin-off
by Ian Ray 19 Feb '24

19 Feb '24

Update our email addresses, from @ge.com to @gehealthcare.com, after GE HealthCare was spun-off from GE. Remove Antti, who no longer works on the project. Signed-off-by: Ian Ray <ian.ray(a)gehealthcare.com> --- MAINTAINERS | 2 +- board/ge/b1x5v2/MAINTAINERS | 4 ++-- board/ge/bx50v3/MAINTAINERS | 2 +- board/ge/mx53ppd/MAINTAINERS | 3 +-- 4 files changed, 5 insertions(+), 6 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 46ba17647f..338b7b6348 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -453,7 +453,7 @@ F: drivers/timer/mchp-pit64b-timer.c ARM MSC SM2S IMX8MP SOM M: Martyn Welch <martyn.welch(a)collabora.com> -M: Ian Ray <ian.ray(a)ge.com> +M: Ian Ray <ian.ray(a)gehealthcare.com> S: Maintained F: arch/arm/dts/imx8mp-msc-sm2s* F: board/msc/sm2s_imx8mp/ diff --git a/board/ge/b1x5v2/MAINTAINERS b/board/ge/b1x5v2/MAINTAINERS index 3196ddbb51..7312f4be1a 100644 --- a/board/ge/b1x5v2/MAINTAINERS +++ b/board/ge/b1x5v2/MAINTAINERS @@ -1,6 +1,6 @@ GE B1X5V2 BOARD -M: Huan 'Kitty' Wang <HuanWang(a)ge.com> -M: Ian Ray <ian.ray(a)ge.com> +M: Huan 'Kitty' Wang <HuanWang(a)gehealthcare.com> +M: Ian Ray <ian.ray(a)gehealthcare.com> M: Martyn Welch <martyn.welch(a)collabora.com> S: Maintained F: arch/arm/dts/imx6dl-b1x5v2.dts diff --git a/board/ge/bx50v3/MAINTAINERS b/board/ge/bx50v3/MAINTAINERS index c165048336..53a8d88a90 100644 --- a/board/ge/bx50v3/MAINTAINERS +++ b/board/ge/bx50v3/MAINTAINERS @@ -1,5 +1,5 @@ GE BX50V3 BOARD -M: Ian Ray <ian.ray(a)ge.com> +M: Ian Ray <ian.ray(a)gehealthcare.com> M: Martyn Welch <martyn.welch(a)collabora.com> S: Maintained F: arch/arm/dts/imx6q-b450v3.dts diff --git a/board/ge/mx53ppd/MAINTAINERS b/board/ge/mx53ppd/MAINTAINERS index 146a460e7e..19e4ea7593 100644 --- a/board/ge/mx53ppd/MAINTAINERS +++ b/board/ge/mx53ppd/MAINTAINERS @@ -1,6 +1,5 @@ GE PPD BOARD -M: Antti Mäentausta <antti.maentausta(a)ge.com> -M: Ian Ray <ian.ray(a)ge.com> +M: Ian Ray <ian.ray(a)gehealthcare.com> M: Martyn Welch <martyn.welch(a)collabora.com> S: Maintained F: arch/arm/dts/imx53-ppd* -- 2.39.2

2 1

[PATCH] disk: dos: Add all options for EFI System Partitions
by Peter Robinson 19 Feb '24

19 Feb '24

The EFI spec states that the ESP can be any of FAT12/16/32 but for compatibility doesn't necssarily require the partition to be the EFI partition table ID of 0xef. A number of arm devices will not find their firmware on a FAT partition with an ID of 0xef so also allow the original FAT12/16/32 partition IDs as they are also permissable for an ESP. Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com> --- disk/part_dos.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/disk/part_dos.c b/disk/part_dos.c index 567ead7511d..303eb1d13ee 100644 --- a/disk/part_dos.c +++ b/disk/part_dos.c @@ -40,6 +40,12 @@ static int get_bootable(dos_partition_t *p) { int ret = 0; + if (p->sys_ind == 0x1) + ret |= PART_EFI_SYSTEM_PARTITION; + if (p->sys_ind == 0x6) + ret |= PART_EFI_SYSTEM_PARTITION; + if (p->sys_ind == 0x0b) + ret |= PART_EFI_SYSTEM_PARTITION; if (p->sys_ind == 0xef) ret |= PART_EFI_SYSTEM_PARTITION; if (p->boot_ind == 0x80) -- 2.43.1

3 3

[PATCH v10 0/8] spi-nor: Add parallel and stacked memories support
by Venkatesh Yadav Abbarapu 19 Feb '24

19 Feb '24

This series adds support for Xilinx qspi parallel and stacked memeories. In parallel mode, the current implementation assumes that a maximum of two flashes are connected. The QSPI controller splits the data evenly between both the flashes so, both the flashes that are connected in parallel mode should be identical. During each operation SPI-NOR sets 0th bit for CS0 & 1st bit for CS1 in nor->flags. In stacked mode the current implementation assumes that a maximum of two flashes are connected and both the flashes are of same make but can differ in sizes. So, except the sizes all other flash parameters of both the flashes are identical. Spi-nor will pass on the appropriate flash select flag to low level driver, and it will select pass all the data to that particular flash. Write operation in parallel mode are performed in page size * 2 chunks as each write operation results in writing both the flashes. For doubling the address space each operation is performed at addr/2 flash offset, where addr is the address specified by the user. Similarly for read and erase operations it will read from both flashes, so size and offset are divided by 2 and send to flash. Changes in v2: - Fixed the compilation issues. Changes in v3: - Fixed the CI issues. Changes in v4: - Removed the dio,dummy_bytes variables from zynq_qspi driver. - Fix the compilation issue by including the DM_SPI config. Changes in v5: - Fixed the issue reported by buildman. Changes in v6: - Fixed the issues reported while running the sandbox test cases. Changes in v7: - Fixed the issues reported while running these da850evm_defconfig, imx28_xea_defconfig configs. - Fixed the issue when DM_SPI config is disabled. - Fixed the issue while running the sandbox_noinst_defconfig with spl ./spl/u-boot-spl -d arch/sandbox/dts/test.dtb jedec_spi_nor spi.bin@0: has no valid 'reg' property (-12) jedec_spi_nor spi.bin@1: has no valid 'reg' property (-12) ### ERROR ### Please RESET the board ### Changes in v8: - Fixed the compilation issue with imx28_xea_defconfig. - Fixed the SPL size issue with the axm and taurus defconfigs. - Rebased the patches on top of next branch. Changes in v9: - Updated the commit log why SPL_FIT is being enabled. Changes in v10: - Added the new config SPI_ADVANCE to fix the issue while enabling imx28_xea_defconfig. Ashok Reddy Soma (4): mtd: spi-nor: Add parallel and stacked memories support mtd: spi-nor: Add parallel memories support for read_sr and read_fsr mtd: spi-nor: Add parallel and stacked memories support in read_bar and write_bar spi: spi-uclass: Read chipselect and restrict capabilities Venkatesh Yadav Abbarapu (4): spi: zynqmp_gqspi: Add parallel memories support in GQSPI driver spi: zynq_qspi: Add parallel memories support in QSPI driver spi: Add the spi advance options for non SPL config: xea: Enable the SPI_ADVANCE config option configs/imx28_xea_defconfig | 1 + drivers/mtd/spi/sandbox.c | 2 +- drivers/mtd/spi/spi-nor-core.c | 398 ++++++++++++++++++++++++++++----- drivers/spi/Kconfig | 7 + drivers/spi/altera_spi.c | 4 +- drivers/spi/atcspi200_spi.c | 2 +- drivers/spi/ath79_spi.c | 2 +- drivers/spi/atmel_spi.c | 6 +- drivers/spi/bcm63xx_hsspi.c | 42 ++-- drivers/spi/bcm63xx_spi.c | 6 +- drivers/spi/bcmbca_hsspi.c | 34 +-- drivers/spi/cf_spi.c | 6 +- drivers/spi/davinci_spi.c | 8 +- drivers/spi/fsl_dspi.c | 18 +- drivers/spi/fsl_espi.c | 4 +- drivers/spi/fsl_qspi.c | 4 +- drivers/spi/gxp_spi.c | 2 +- drivers/spi/mpc8xx_spi.c | 4 +- drivers/spi/mpc8xxx_spi.c | 10 +- drivers/spi/mscc_bb_spi.c | 4 +- drivers/spi/mxc_spi.c | 6 +- drivers/spi/npcm_fiu_spi.c | 14 +- drivers/spi/nxp_fspi.c | 2 +- drivers/spi/octeon_spi.c | 2 +- drivers/spi/omap3_spi.c | 4 +- drivers/spi/pic32_spi.c | 2 +- drivers/spi/rk_spi.c | 4 +- drivers/spi/rockchip_sfc.c | 2 +- drivers/spi/spi-aspeed-smc.c | 28 +-- drivers/spi/spi-mxic.c | 6 +- drivers/spi/spi-qup.c | 4 +- drivers/spi/spi-sifive.c | 6 +- drivers/spi/spi-sn-f-ospi.c | 2 +- drivers/spi/spi-sunxi.c | 6 +- drivers/spi/spi-synquacer.c | 4 +- drivers/spi/spi-uclass.c | 34 ++- drivers/spi/stm32_qspi.c | 2 +- drivers/spi/stm32_spi.c | 4 +- drivers/spi/ti_qspi.c | 14 +- drivers/spi/xilinx_spi.c | 6 +- drivers/spi/zynq_qspi.c | 119 ++++++++-- drivers/spi/zynq_spi.c | 6 +- drivers/spi/zynqmp_gqspi.c | 141 ++++++++++-- include/linux/mtd/spi-nor.h | 12 + include/spi.h | 23 +- lib/acpi/acpi_device.c | 2 +- 46 files changed, 791 insertions(+), 228 deletions(-) -- 2.25.1

3 10

[PATCH v8 00/16] Introduce initial TI's J784S4 and AM69 support
by Apurva Nandan 19 Feb '24

19 Feb '24

Hello Everyone! This series will introduce basic support (SD and UART) support for Texas Instruments J784S4 EVM. The J784S4 SoC device tree patches are taken from kernel patch submissions and will be updated as they are accepted and merged to the kernel tree. All other patches are specific to SPL and u-boot and do not have dependency on other trees. Appreciate a review for acceptance to u-boot tree. Here are some of the salient features of the J784S4 automotive grade application processor: The J784S4 SoC belongs to the K3 Multicore SoC architecture platform, providing advanced system integration in automotive, ADAS and industrial applications requiring AI at the network edge. This SoC extends the K3 Jacinto 7 family of SoCs with focus on raising performance and integration while providing interfaces, memory architecture and compute performance for multi-sensor, high concurrency applications. Some highlights of this SoC are: * Up to 8 Cortex-A72s, four clusters of lockstep capable dual Cortex-R5F MCUs, 4 C7x floating point vector DSPs with Matrix Multiply Accelerator(MMA) for deep learning and CNN. * 3D GPU: Automotive grade IMG BXS-4-64 MC1 * Vision Processing Accelerator (VPAC) with image signal processor and Depth and Motion Processing Accelerator (DMPAC) * Three CSI2.0 4L RX plus two CSI2.0 4L TX, two DSI Tx, one eDP/DP and one DPI interface. * Integrated gigabit ethernet switch, up to 8 ports (TDA4VH), two ports support 10Gb USXGMII; Two 4 lane PCIe-GEN3 controllers, USB3.0 Dual-role device subsystems, Up to 20 MCANs, among other peripherals. See J784S4 Technical Reference Manual (SPRUJ52 - JUNE 2022) for further details: http://www.ti.com/lit/zip/spruj52 In addtion, the J784S4 EVM board is designed for TI J784S4 SoC. It supports the following interfaces: * 32 GB DDR4 RAM * x2 Gigabit Ethernet interfaces capable of working in Switch and MAC mode * x1 Input Audio Jack, x1 Output Audio Jack * x1 USB2.0 Hub with two Type A host and x1 USB 3.1 Type-C Port * x2 4L PCIe connector * x1 UHS-1 capable micro-SD card slot * 512 Mbit OSPI flash, 1 Gbit Octal NAND flash, 512 Mbit QSPI flash, UFS flash. * x6 UART through UART-USB bridge * XDS110 for onboard JTAG debug using USB * Temperature sensors, user push buttons and LEDs * 40-pin User Expansion Connector * x2 ENET Expansion Connector, x1 GESI expander, x2 Display connector * x1 15-pin CSI header * x6 MCAN instances Schematics: https://www.ti.com/lit/zip/sprr458 eMMC UDA moode bootlog: https://gist.githubusercontent.com/apurvanandan1997/3cffada252d50a8aa0c00a9… Note: This series is dependent on the following series for removing findfdt env: https://lore.kernel.org/u-boot/20240109191506.3820908-1-nm@ti.com/ Sync-up for PATCH #4 is posted on Linux: https://lore.kernel.org/linux-arm-kernel/20240119171619.3759205-1-a-nandan@… Changes in v8: 1) Squashed Linux am69-sk and j784s4-evm dts patches into one 2) Sorted config addition of SoC in arm/mach-K3/Kconfig 3) Updated commit messages according to the reviews 4) Removed #inlcude <config.h> 5) Removed k3_mmc_stop_clock and k3_mmc_restart_clock 6) Moved board_init_f logic to separate smaller functions 7) Removed J784S4 EVM specific Kconfig options in j784s4_int.c 8) Cleaned up emmc boot flow based on commit 66459346463439c72f84cfd1f985496b8a6142d8 9) Removed the dependency of findfdt and updated to ti_set_fdt_env 10) Updated copyright messages 11) Did cleanup/formatting of yaml files, removing linting errors 12) Removed k3-am69-sk specific things from k3-j784s4-binman.dtsi 13) Changed OF_LIST to a single dtb 14) Added bootph-all tag in EVM and SK dts instead of u-boot.dtsi 15) Trimmed the defconfig files to minimal 16) Merged the MAINTAINER file in right patches 17) Updated OpenOCD tag in U-Boot doc 18) And fixed other formatting mistakes. Link to v7: https://lore.kernel.org/u-boot/20231219191537.4039361-1-a-nandan@ti.com/ Changes in v7: 1) Moved to unified memory map in arm64-mmu.c based on https://lore.kernel.org/all/20231128170528.407707-1-afd@ti.com/ 2) Used ARRAY_SIZE in clk-data.c and dev-data.c 3) Removed I2C board detect from j784s4_init.c 4) Rebased to latest next Link to v6: https://lore.kernel.org/all/20231206123753.1486031-1-a-nandan@ti.com/ Changes in v6: 1) Move bootph-all of memory node to u-boot.dtsi 2) Used a while loop for DRAM controller init, instead of hard-coding for 4 DRAM 3) Fixed build error by adding board/ti/j784s4/Kconfig 4) Trimmed out j784s4_evm.h 5) Fixed checkpatch warnings Link to v5: https://patchwork.ozlabs.org/project/uboot/cover/20231130115552.3580995-1-a… Changes in v5: 1) Incorporated Andrew Davis' "Move R5 specific code into new r5/ directory" and "Move board selection to mach-k3" series changes. 2) Incorporated Neha Francis' "Move to using templated FITs" series changes. 3) Synced device tree files with Linux v6.7-rc1 4) Changed ti_mmc to mmc1 target from bootstd 5) Updated doc based on review comments 6) Removed remoteproc support from the series 7) Splitted board files patch into smaller patches 8) Trimmed j784s4.env to necessary variables 9) Used fdtdec_setup_mem_size_base fdtdec_setup_memory_banksize in evm.c 10) Trimmed down evm.c to essential header files. 11) Switched to multi-dtb fit compilation with config fragments Link to v4: https://lore.kernel.org/u-boot/20231001165545.494212-1-a-nandan@ti.com/ Changes in v4: 1) Cleaned up Copyright and SPDX identifiers 2) Synced the device trees to Linux v6.6-rc1 tag 3) Added cleanup patch for sorting SoC JTAG ID entries 4) Removed EEPROM board detect from evm.c and added am69 config fragments 5) Updated MAINTAINERS files and commit messages 6) Removed struct renaming in ti_k3_r5f_rproc driver Link to v3: https://lore.kernel.org/u-boot/20230908110551.861575-1-a-nandan@ti.com/ Changes in v3: 1) Added AM69 SK support in the series 2) Switched from distroboot to bootstd support 3) Added remoteproc support for J784S4 4) Added documentation for both SoCs 5) Added binman support 6) Removed unnecessarry nodes from r5-evm.dts and evm-u-boot.dtsi 7) Added HS device support 8) Added env file for environement variables 9) Removed ti-serdes-mux bindings 10) Cleaned up all files and synced with latest 11) Addressed all previous review comments Note: The base dts files have been sync from next-20230905 linux tag as per review comment received on previous re-roll: https://lore.kernel.org/u-boot/20230321155227.GV8135@bill-the-cat/ Link to v2: https://lore.kernel.org/u-boot/20230321141028.24456-1-hnagalla@ti.com/ Apurva Nandan (14): arm: mach-k3: Kconfig: Sort SOC_K3 config entries arm: mach-k3: Add basic support for J784S4 SoC definition arm: dts: Introduce j784s4 and am69 dts from linux kernel arm: dts: Add bootph-all for memory node arm: mach-k3: Sort SoC JTAG_ID entries soc: ti: k3-socinfo: Add entry for J784S4 SoC arm: mach-k3: j784s4: Add clk and power support drivers: dma: Add support for J784S4 SoC board: ti: j784s4: Add board support for J784S4 EVM board: ti: j748s4: Add board config yaml files board: ti: j784s4: Add boot environment variables arm: dts: Introduce j784s4 u-boot dts files configs: j784s4_evm: Add defconfig for j784s4 evm board doc: board: ti: k3: Add J784S4 EVM and AM69 SK documentation Dasnavis Sabiya (2): arm: dts: Introduce am69-sk u-boot dts files configs: Add am69_sk_* defconfig fragments arch/arm/dts/Makefile | 6 + arch/arm/dts/k3-am69-r5-sk.dts | 105 + arch/arm/dts/k3-am69-sk-u-boot.dtsi | 48 + arch/arm/dts/k3-am69-sk.dts | 901 ++ arch/arm/dts/k3-j784s4-binman.dtsi | 345 + arch/arm/dts/k3-j784s4-ddr-evm-lp4-4266.dtsi | 8757 ++++++++++++++++ arch/arm/dts/k3-j784s4-ddr.dtsi | 8858 +++++++++++++++++ arch/arm/dts/k3-j784s4-evm-u-boot.dtsi | 25 + arch/arm/dts/k3-j784s4-evm.dts | 982 ++ arch/arm/dts/k3-j784s4-main.dtsi | 2068 ++++ arch/arm/dts/k3-j784s4-mcu-wakeup.dtsi | 743 ++ arch/arm/dts/k3-j784s4-r5-evm.dts | 105 + arch/arm/dts/k3-j784s4-thermal.dtsi | 101 + arch/arm/dts/k3-j784s4.dtsi | 294 + arch/arm/mach-k3/Kconfig | 33 +- arch/arm/mach-k3/Makefile | 2 + arch/arm/mach-k3/include/mach/hardware.h | 13 +- .../mach-k3/include/mach/j784s4_hardware.h | 59 + arch/arm/mach-k3/include/mach/j784s4_spl.h | 47 + arch/arm/mach-k3/include/mach/spl.h | 4 + arch/arm/mach-k3/j784s4/Kconfig | 34 + arch/arm/mach-k3/j784s4_fdt.c | 15 + arch/arm/mach-k3/j784s4_init.c | 305 + arch/arm/mach-k3/r5/Makefile | 1 + arch/arm/mach-k3/r5/j784s4/Makefile | 7 + arch/arm/mach-k3/r5/j784s4/clk-data.c | 428 + arch/arm/mach-k3/r5/j784s4/dev-data.c | 98 + board/ti/j784s4/Kconfig | 37 + board/ti/j784s4/MAINTAINERS | 25 + board/ti/j784s4/Makefile | 7 + board/ti/j784s4/board-cfg.yaml | 37 + board/ti/j784s4/evm.c | 43 + board/ti/j784s4/j784s4.env | 17 + board/ti/j784s4/pm-cfg.yaml | 13 + board/ti/j784s4/rm-cfg.yaml | 3058 ++++++ board/ti/j784s4/sec-cfg.yaml | 380 + board/ti/j784s4/tifs-rm-cfg.yaml | 2656 +++++ configs/am69_sk_a72.config | 5 + configs/am69_sk_r5.config | 5 + configs/j784s4_evm_a72_defconfig | 158 + configs/j784s4_evm_r5_defconfig | 153 + doc/board/ti/j784s4_evm.rst | 299 + doc/board/ti/k3.rst | 1 + drivers/clk/ti/clk-k3.c | 6 + drivers/dma/ti/Makefile | 1 + drivers/dma/ti/k3-psil-j784s4.c | 166 + drivers/dma/ti/k3-psil-priv.h | 1 + drivers/dma/ti/k3-psil.c | 2 + drivers/firmware/ti_sci_static_data.h | 34 + drivers/power/domain/ti-power-domain.c | 6 + drivers/ram/Kconfig | 2 +- drivers/soc/soc_ti_k3.c | 3 + include/configs/j784s4_evm.h | 15 + include/k3-clk.h | 1 + include/k3-dev.h | 1 + 55 files changed, 31496 insertions(+), 20 deletions(-) create mode 100644 arch/arm/dts/k3-am69-r5-sk.dts create mode 100644 arch/arm/dts/k3-am69-sk-u-boot.dtsi create mode 100644 arch/arm/dts/k3-am69-sk.dts create mode 100644 arch/arm/dts/k3-j784s4-binman.dtsi create mode 100644 arch/arm/dts/k3-j784s4-ddr-evm-lp4-4266.dtsi create mode 100644 arch/arm/dts/k3-j784s4-ddr.dtsi create mode 100644 arch/arm/dts/k3-j784s4-evm-u-boot.dtsi create mode 100644 arch/arm/dts/k3-j784s4-evm.dts create mode 100644 arch/arm/dts/k3-j784s4-main.dtsi create mode 100644 arch/arm/dts/k3-j784s4-mcu-wakeup.dtsi create mode 100644 arch/arm/dts/k3-j784s4-r5-evm.dts create mode 100644 arch/arm/dts/k3-j784s4-thermal.dtsi create mode 100644 arch/arm/dts/k3-j784s4.dtsi create mode 100644 arch/arm/mach-k3/include/mach/j784s4_hardware.h create mode 100644 arch/arm/mach-k3/include/mach/j784s4_spl.h create mode 100644 arch/arm/mach-k3/j784s4/Kconfig create mode 100644 arch/arm/mach-k3/j784s4_fdt.c create mode 100644 arch/arm/mach-k3/j784s4_init.c create mode 100644 arch/arm/mach-k3/r5/j784s4/Makefile create mode 100644 arch/arm/mach-k3/r5/j784s4/clk-data.c create mode 100644 arch/arm/mach-k3/r5/j784s4/dev-data.c create mode 100644 board/ti/j784s4/Kconfig create mode 100644 board/ti/j784s4/MAINTAINERS create mode 100644 board/ti/j784s4/Makefile create mode 100644 board/ti/j784s4/board-cfg.yaml create mode 100644 board/ti/j784s4/evm.c create mode 100644 board/ti/j784s4/j784s4.env create mode 100644 board/ti/j784s4/pm-cfg.yaml create mode 100644 board/ti/j784s4/rm-cfg.yaml create mode 100644 board/ti/j784s4/sec-cfg.yaml create mode 100644 board/ti/j784s4/tifs-rm-cfg.yaml create mode 100644 configs/am69_sk_a72.config create mode 100644 configs/am69_sk_r5.config create mode 100644 configs/j784s4_evm_a72_defconfig create mode 100644 configs/j784s4_evm_r5_defconfig create mode 100644 doc/board/ti/j784s4_evm.rst create mode 100644 drivers/dma/ti/k3-psil-j784s4.c create mode 100644 include/configs/j784s4_evm.h -- 2.34.1

6 47

Booting RPi5B with latest git
by John 19 Feb '24

19 Feb '24

I am running Arch ARM on a RPi4B and also on a RPi5B. My RPi4B can boot the vanilla kernel package (linux-aarch64) with the latest uboot-raspberrypi (2024.04-rc2) just fine. Yet, if I take that uSD card and place it in my RPi5B, it does not boot. I only see the "U-Boot" submarine logo in the upper right of the screen/no debug output. Any thoughts are appreciated. I built u-boot like this: unset CFLAGS unset CXXFLAGS unset CPPFLAGS make rpi_arm64_config echo 'CONFIG_IDENT_STRING=" Arch Linux ARM"' >> .config make EXTRAVERSION=-2024.04rc2

5 8

[PATCH v5 00/11] An effort to bring DT bindings compliance within U-Boot
by Sumit Garg 19 Feb '24

19 Feb '24

Changes in v5: -------------- - Rebased on tip of master (050a9b981d6a835133521b599be3ae189ce70f41) - Created v5_dt branch for testing purposes: https://github.com/b49020/u-boot/tree/v5_dt - Patch #6: Added support to cherry-pick fixes in subtree update script. Also, used https:// instead of git://. - Patch #7: Fixed inappropriate documentation update. - Patch #8: Document how to cherry-pick fixes from devicetree-rebasing tree. Changes in v4: -------------- - Switched subtree to be imported as dts/upstream sub-directory rather than devicetree-rebasing sub-directory to better suite U-Boot directory structure. - Since we now have v6.7-dts tag available now, so switch subtree to that from its beginning. - Patch #2: Incorporate build fix to adjust Bindings Makefile rules to old U-Boot Kbuild infrastructure. - Patch #3: Incorporate fix to resolve rk3399 migration issue reported by Simon. - Patch #4: New patch to reuse upstream DT includes by U-Boot as per Brian's use-case for TI K3 SoCs. - Patch #5: Added a note to OF_UPSTREAM Kconfig option. - Patch #6: New patch to add script dts/update-dts-subtree.sh as per Rob's comments. - Patch #7: Separate patch to align documentation to use Kconfig symbols instead. - Patch #8: Clarify subtree uprev schedule as a separate documentation section. Also, fixed documentation typos. - Patch #9: Added commit description. Changes in v3: -------------- - Patch #4: Minor commit message update - Patch #5: Replace CONFIG_* with Kconfig options - Patch #7: Dropped Makefile portion and enabled OF_UPSTREAM for SoC instead. - Patch #1, #3, #6 and #8: Picked up review tags Changes in v2: -------------- - Patch #1: excluded gitab CI config check and added commit description. - Patch #3: s/UBOOT_DTSI_LOC/u_boot_dtsi_loc/ - Patch #4: s/DEVICE_TREE_LOC/dt_dir/ and s/U-boot/U-Boot/ - Patch #5: s/U-boot/U-Boot/ - Patch #6 and #7: Picked up review tags Prerequisite ------------ This patch series requires devicetree-rebasing git repo to be added as a subtree to the main U-Boot repo via: $ git subtree add --prefix dts/upstream \ https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas… \ v6.7-dts --squash Background ---------- This effort started while I was reviewing patch series corresponding to Qcom platforms [1] which was about to import modified devicetree source files from Linux kernel. I suppose keeping devicetree files sync with Linux kernel without any DT bindings schema validation has been a pain for U-Boot SoC/platform maintainers. There has been past discussions about a single DT repo but that hasn't come up and Linux kernel remained the place where DT source files as well as bindings are placed and maintained. However, Linux kernel DT maintainers proposed [2] for U-Boot to rather use devicetree-rebasing repo [3] which is a forked copy from Linux kernel for DT source files as well as bindings. It is tagged at every Linux kernel major release or intermideate release candidates. So here I have tried to reuse that to bring DT bingings compliance as well as a standard way to maintain a regular sync of DT source files with Linux kernel. In order to maintain devicetree files sync, U-Boot will maintains a Git subtree for devicetee-rebasing repo as `dts/upstream` sub-directory. U-Boot will regularly sync `dts/upstream/` subtree whenever the next window opens with the next available kernel major release. `dts/update-dts-subtree.sh` script provides a wrapper around git subtree pull command, usage from the top level U-Boot source tree, run: $ ./dts/update-dts-subtree.sh pull <devicetree-rebasing-release-tag> If required it is also possible to cherry-pick fixes from devicetree-rebasing tree prior to next sync, usage: $ ./dts/update-dts-subtree.sh pick <devicetree-rebasing-commit-id> The RFC/prototype for this series has been discussed with Linux DT maintainers as well as U-Boot maintainers here [4]. Now we would like to reach out to wider U-Boot community to seek feedback. [1] https://lore.kernel.org/all/CAFA6WYMLUD9cnkr=R0Uur+1UeTMkKjM2zDdMJtXb3nmrLk… [2] https://lore.kernel.org/all/CAL_JsqKEjv2tSGmT+0ZiO7_qbBfhTycbGnhJhYpKDFzfO9… [3] https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas… [4] https://github.com/u-boot/u-boot/pull/451 Changes ------- Traditionally, U-Boot placed copies of devicetree source files from Linux kernel into `arch/<arch>/dts/<name>.dts` which can be selected via setting "<name>" when prompted for `DEFAULT_DEVICE_TREE` by Kconfig. SoC/board maintainers are encouraged to migrate to use synced copies from `dts/upstream/src/<arch>/<vendor>`. To do that enable `OF_UPSTREAM` for the SoC being used via Kconfig and set up "<vendor>/<name>" when prompted for `DEFAULT_DEVICE_TREE` by Kconfig. An example have been shown for Amlogic meson-gxbb SoC and corresponding derived boards via patch #10 and #11. Devicetree bindings schema checks --------------------------------- With devicetee-rebasing Git subtree, the devicetree bindings are also regularly synced with Linux kernel as `dts/upstream/Bindings/` sub-directory. This allows U-Boot to run devicetree bindings schema checks which will bring compliance to U-Boot core/drivers regarding usage of devicetree. Dependencies ------------ The DT schema project must be installed in order to validate the DT schema binding documents and validate DTS files using the DT schema. The DT schema project can be installed with pip: $ pip3 install dtschema Note that 'dtschema' installation requires 'swig' and Python development files installed first. On Debian/Ubuntu systems: $ apt install swig python3-dev Several executables (dt-doc-validate, dt-mk-schema, dt-validate) will be installed. Ensure they are in your PATH (~/.local/bin by default). Recommended is also to install yamllint (used by dtschema when present). $ apt install yamllint Running checks -------------- In order to perform validation of DTB files, use the ``dtbs_check`` target: $ make dtbs_check It is also possible to run checks with a subset of matching schema files by setting the ``DT_SCHEMA_FILES`` variable to 1 or more specific schema files or patterns (partial match of a fixed string). Each file or pattern should be separated by ':'. $ make dtbs_check DT_SCHEMA_FILES=trivial-devices.yaml:rtc.yaml $ make dtbs_check DT_SCHEMA_FILES=/gpio/ $ make dtbs_check DT_SCHEMA_FILES=trivial-devices.yaml Sumit Garg (11): CI: Exclude devicetree-rebasing subtree for CONFIG checks Makefile: Add support for DT bindings schema checks scripts/Makefile.lib: Statically define *-u-boot.dtsi files location Makefile: Allow upstream DT subtree to provide DT includes dts: Add alternative location for upstream DTB builds dts: Add script to uprev dts/upstream subtree doc: devicetree: Align documentation to use Kconfig options doc: devicetree: Updates for devicetree-rebasing subtree MAINTAINERS: Add myself as devicetree-rebasing maintainer dts: meson-gxbb: Switch to using upstream DT dts: meson-gxbb: Drop redundant devicetree files .azure-pipelines.yml | 3 +- .gitlab-ci.yml | 3 +- MAINTAINERS | 5 + Makefile | 23 +- arch/arm/dts/Makefile | 8 - arch/arm/dts/meson-gxbb-kii-pro.dts | 140 ---- arch/arm/dts/meson-gxbb-nanopi-k2.dts | 426 ------------ arch/arm/dts/meson-gxbb-odroidc2.dts | 414 ----------- arch/arm/dts/meson-gxbb-p200.dts | 100 --- arch/arm/dts/meson-gxbb-p201.dts | 26 - arch/arm/dts/meson-gxbb-p20x.dtsi | 250 ------- arch/arm/dts/meson-gxbb-wetek-hub.dts | 58 -- arch/arm/dts/meson-gxbb-wetek-play2.dts | 119 ---- arch/arm/dts/meson-gxbb-wetek.dtsi | 292 -------- arch/arm/dts/meson-gxbb.dtsi | 870 ------------------------ arch/arm/mach-meson/Kconfig | 1 + configs/nanopi-k2_defconfig | 2 +- configs/odroid-c2_defconfig | 2 +- configs/p200_defconfig | 2 +- configs/p201_defconfig | 2 +- configs/videostrong-kii-pro_defconfig | 2 +- configs/wetek-hub_defconfig | 2 +- configs/wetek-play2_defconfig | 2 +- doc/develop/devicetree/control.rst | 161 +++-- dts/Kconfig | 16 + dts/Makefile | 17 +- dts/update-dts-subtree.sh | 45 ++ dts/upstream/Bindings/Makefile | 6 +- dts/upstream/src/arm64/Makefile | 14 + scripts/Makefile.lib | 49 +- 30 files changed, 281 insertions(+), 2779 deletions(-) delete mode 100644 arch/arm/dts/meson-gxbb-kii-pro.dts delete mode 100644 arch/arm/dts/meson-gxbb-nanopi-k2.dts delete mode 100644 arch/arm/dts/meson-gxbb-odroidc2.dts delete mode 100644 arch/arm/dts/meson-gxbb-p200.dts delete mode 100644 arch/arm/dts/meson-gxbb-p201.dts delete mode 100644 arch/arm/dts/meson-gxbb-p20x.dtsi delete mode 100644 arch/arm/dts/meson-gxbb-wetek-hub.dts delete mode 100644 arch/arm/dts/meson-gxbb-wetek-play2.dts delete mode 100644 arch/arm/dts/meson-gxbb-wetek.dtsi delete mode 100644 arch/arm/dts/meson-gxbb.dtsi create mode 100755 dts/update-dts-subtree.sh create mode 100644 dts/upstream/src/arm64/Makefile -- 2.34.1

5 23

[PATCH] mmc: rockchip_sdhci: Use bounce buffer in SPL to fix read performance
by Jonas Karlman 18 Feb '24

18 Feb '24

The commit 3b804b370dd8 ("mmc: rockchip_sdhci: Disable DMA mode using a device tree property") and commit 2cc6cde647e2 ("mmc: rockchip_sdhci: Limit number of blocks read in a single command") implemented a workaround to fix loading a part of TF-A into SRAM from eMMC in SPL. This has resulted in very slow read performance of FIT from eMMC in SPL on RK3588. Change to make use of a bounce buffer to significantly improve the read performance when malloc_limit is large enough and use PIO mode as fall back. Also update the size of align_buffer to use SDHCI_DEFAULT_BOUNDARY_SIZE instead of a hardcoded 512 * 1024. Signed-off-by: Jonas Karlman <jonas(a)kwiboo.se> --- - This has been tested on RK3588 boards with malloc_limit above 512 KiB and on RK3399 boards with less than 512 KiB malloc_limit. - Together with HS200 mode [1] and D-cache [2] enabled in SPL loading of FIT can be very fast on RK3588. [1] https://patchwork.ozlabs.org/patch/1895043/ [2] https://patchwork.ozlabs.org/patch/1891025/ --- drivers/mmc/rockchip_sdhci.c | 20 ++++++++++++++++---- drivers/mmc/sdhci.c | 2 +- 2 files changed, 17 insertions(+), 5 deletions(-) diff --git a/drivers/mmc/rockchip_sdhci.c b/drivers/mmc/rockchip_sdhci.c index 706fb1235796..528544b1eff8 100644 --- a/drivers/mmc/rockchip_sdhci.c +++ b/drivers/mmc/rockchip_sdhci.c @@ -21,6 +21,9 @@ #include <syscon.h> #include <asm/arch-rockchip/clock.h> #include <asm/arch-rockchip/hardware.h> +#include <asm/global_data.h> + +DECLARE_GLOBAL_DATA_PTR; /* DWCMSHC specific Mode Select value */ #define DWCMSHC_CTRL_HS400 0x7 @@ -591,12 +594,21 @@ static int rockchip_sdhci_probe(struct udevice *dev) return ret; /* - * Disable use of DMA and force use of PIO mode in SPL to fix an issue - * where loading part of TF-A into SRAM using DMA silently fails. + * Use a bounce buffer or PIO mode in SPL to fix an issue where loading + * part of TF-A directly into SRAM using DMA silently fails. */ if (IS_ENABLED(CONFIG_SPL_BUILD) && - dev_read_bool(dev, "u-boot,spl-fifo-mode")) - host->flags &= ~USE_DMA; + dev_read_bool(dev, "u-boot,spl-fifo-mode")) { + if (CONFIG_IS_ENABLED(SYS_MALLOC_F) && + gd->malloc_limit > SDHCI_DEFAULT_BOUNDARY_SIZE) { + cfg->b_max = SDHCI_DEFAULT_BOUNDARY_SIZE / + MMC_MAX_BLOCK_LEN; + host->force_align_buffer = true; + host->quirks |= SDHCI_QUIRK_32BIT_DMA_ADDR; + } else { + host->flags &= ~USE_DMA; + } + } /* * Reading more than 4 blocks with a single CMD18 command in PIO mode diff --git a/drivers/mmc/sdhci.c b/drivers/mmc/sdhci.c index 0178ed8a11e1..cc855dc7ba3d 100644 --- a/drivers/mmc/sdhci.c +++ b/drivers/mmc/sdhci.c @@ -736,7 +736,7 @@ static int sdhci_init(struct mmc *mmc) host->force_align_buffer = true; #else if (host->quirks & SDHCI_QUIRK_32BIT_DMA_ADDR) { - host->align_buffer = memalign(8, 512 * 1024); + host->align_buffer = memalign(8, SDHCI_DEFAULT_BOUNDARY_SIZE); if (!host->align_buffer) { printf("%s: Aligned buffer alloc failed!!!\n", __func__); -- 2.43.0

1 1

[PATCH v2 0/2] rockchip: Update stack and bss addresses on RK3328 and RK3399
by Jonas Karlman 18 Feb '24

18 Feb '24

With the stack and text base used by U-Boot SPL and proper on RK3328 and RK3399 there is a high likelihood of overlapping when U-Boot proper + FDT nears 1 MiB in size. Trying to run U-Boot proper close to 1 MiB in size with debug logging something similar to following can be observed: FDT 00000000002fc4e0 gd 00000000002fddf0 FDT overlap resetting ... System reset not supported on this platform ### ERROR ### Please RESET the board ### Fix this by changing stack and bss addresses used on RK3328 and RK3399. The addresses chosen for stack and bss is a combination from both boards. Changes in v2: - Rebase on v2 of "rockchip: rk3328: Update defconfigs, DTs and enable boot from SPI" [1] - Use correct address 0x04000000 for 64 MiB offset in commit message - Collect r-b tag This series depends on v2 of the following two series: - rockchip: rk3328: Update defconfigs, DTs and enable boot from SPI [1] - rockchip: Read cpuid and generate MAC address from efuse for RK3328 and RK3399 [2] A copy of this series and its two depends can be found at [3]. [1] https://patchwork.ozlabs.org/cover/1900345/ [2] https://patchwork.ozlabs.org/cover/1897743/ [3] https://github.com/Kwiboo/u-boot-rockchip/commits/rk3328-update-v2 Jonas Karlman (2): rockchip: rk3328: Update stack addresses rockchip: rk3399: Update stack and bss addresses arch/arm/mach-rockchip/rk3328/Kconfig | 2 +- configs/chromebook_bob_defconfig | 2 +- configs/chromebook_kevin_defconfig | 2 +- configs/eaidk-610-rk3399_defconfig | 4 ++-- configs/evb-rk3328_defconfig | 4 +--- configs/evb-rk3399_defconfig | 4 ++-- configs/ficus-rk3399_defconfig | 2 +- configs/firefly-rk3399_defconfig | 4 ++-- configs/khadas-edge-captain-rk3399_defconfig | 4 ++-- configs/khadas-edge-rk3399_defconfig | 4 ++-- configs/khadas-edge-v-rk3399_defconfig | 4 ++-- configs/leez-rk3399_defconfig | 4 ++-- configs/nanopc-t4-rk3399_defconfig | 4 ++-- configs/nanopi-m4-2gb-rk3399_defconfig | 4 ++-- configs/nanopi-m4-rk3399_defconfig | 4 ++-- configs/nanopi-m4b-rk3399_defconfig | 4 ++-- configs/nanopi-neo4-rk3399_defconfig | 4 ++-- configs/nanopi-r2c-plus-rk3328_defconfig | 4 ++-- configs/nanopi-r2c-rk3328_defconfig | 4 ++-- configs/nanopi-r2s-rk3328_defconfig | 4 ++-- configs/nanopi-r4s-rk3399_defconfig | 4 ++-- configs/orangepi-r1-plus-lts-rk3328_defconfig | 4 ++-- configs/orangepi-r1-plus-rk3328_defconfig | 4 ++-- configs/orangepi-rk3399_defconfig | 4 ++-- configs/pinebook-pro-rk3399_defconfig | 4 ++-- configs/pinephone-pro-rk3399_defconfig | 4 ++-- configs/puma-rk3399_defconfig | 2 +- configs/roc-cc-rk3328_defconfig | 4 ++-- configs/roc-pc-mezzanine-rk3399_defconfig | 4 ++-- configs/roc-pc-rk3399_defconfig | 4 ++-- configs/rock-4c-plus-rk3399_defconfig | 4 ++-- configs/rock-4se-rk3399_defconfig | 4 ++-- configs/rock-pi-4-rk3399_defconfig | 4 ++-- configs/rock-pi-4c-rk3399_defconfig | 4 ++-- configs/rock-pi-e-rk3328_defconfig | 4 +--- configs/rock-pi-n10-rk3399pro_defconfig | 4 ++-- configs/rock64-rk3328_defconfig | 4 ++-- configs/rock960-rk3399_defconfig | 4 ++-- configs/rockpro64-rk3399_defconfig | 4 ++-- 39 files changed, 71 insertions(+), 75 deletions(-) -- 2.43.0

1 3

[PULL] u-boot-sh/master-porter
by Marek Vasut 18 Feb '24

18 Feb '24

The following changes since commit 9e00b6993f724da9699ef12573307afea8c19284: Merge tag 'u-boot-dfu-20240215' of https://source.denx.de/u-boot/custodians/u-boot-dfu (2024-02-15 10:26:24 -0500) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-sh.git master-porter for you to fetch changes up to 87f9ffbef5e894bbcea99614520c8afd216bbf1a: ARM: renesas: Enable LTO on R-Car (2024-02-17 22:38:20 +0100) ---------------------------------------------------------------- Marek Vasut (3): ARM: renesas: Disable EFI on R-Car Gen2 ARM: renesas: Set R-Car Gen2 board size limit to 512 kiB ARM: renesas: Enable LTO on R-Car Niklas Söderlund (1): clk: renesas: Fix broken clocks on all Gen2 boards Kconfig | 3 ++- arch/arm/Kconfig | 1 + configs/alt_defconfig | 2 ++ configs/blanche_defconfig | 2 ++ configs/gose_defconfig | 2 ++ configs/koelsch_defconfig | 2 ++ configs/lager_defconfig | 2 ++ configs/porter_defconfig | 2 ++ configs/silk_defconfig | 2 ++ configs/stout_defconfig | 2 ++ drivers/clk/renesas/clk-rcar-gen2.c | 9 +++++++++ 11 files changed, 28 insertions(+), 1 deletion(-)

2 1

[PATCH 2/2] cli: allow users to determine history buffer allocation method
by Hanyuan Zhao 17 Feb '24

17 Feb '24

This commit allows users to choose the appropriate memory allocation method between static allocated and dynamically calloc. The previous static-array way will not obviously contribute to the final binary size since it is uninitialized, and might have better performance than the dynamical one. Now we provide the users with both the two options. Signed-off-by: Hanyuan Zhao <hanyuan-z(a)qq.com> --- cmd/Kconfig | 8 ++++++++ common/cli_readline.c | 23 ++++++++++++++++------- 2 files changed, 24 insertions(+), 7 deletions(-) diff --git a/cmd/Kconfig b/cmd/Kconfig index af4dbc95fc..d0140b6cbe 100644 --- a/cmd/Kconfig +++ b/cmd/Kconfig @@ -190,6 +190,14 @@ config CMD_HISTORY Show the command-line history, i.e. a list of commands that are in the history buffer. +config CMD_HISTORY_USE_CALLOC + bool "dynamically allocate memory" + default y + depends on CMD_HISTORY + help + Saying Y to this will use calloc to get the space for history + storing. Or it will be compiled as a static array. + config CMD_LICENSE bool "license" select BUILD_BIN2C diff --git a/common/cli_readline.c b/common/cli_readline.c index eec6d8b0a2..a945cbf7cf 100644 --- a/common/cli_readline.c +++ b/common/cli_readline.c @@ -87,26 +87,35 @@ static int hist_add_idx; static int hist_cur = -1; static unsigned hist_num; +#ifndef CONFIG_CMD_HISTORY_USE_CALLOC +static char hist_data[HIST_MAX][HIST_SIZE + 1]; +#endif static char *hist_list[HIST_MAX]; #define add_idx_minus_one() ((hist_add_idx == 0) ? hist_max : hist_add_idx-1) static int hist_init(void) { - unsigned char *hist; int i; - hist_max = 0; - hist_add_idx = 0; - hist_cur = -1; - hist_num = 0; - - hist = calloc(HIST_MAX, HIST_SIZE + 1); +#ifndef CONFIG_CMD_HISTORY_USE_CALLOC + for (i = 0; i < HIST_MAX; i++) { + hist_list[i] = hist_data[i]; + hist_list[i][0] = '\0'; + } +#else + unsigned char *hist = calloc(HIST_MAX, HIST_SIZE + 1); if (!hist) panic("%s: calloc: out of memory!\n", __func__); for (i = 0; i < HIST_MAX; i++) hist_list[i] = hist + (i * (HIST_SIZE + 1)); +#endif + + hist_max = 0; + hist_add_idx = 0; + hist_cur = -1; + hist_num = 0; return 0; } -- 2.34.1

1 0