May 2021 - U-Boot

[PATCH v2 00/18] am335x, guardian: update board specific changes
by Gireesh.Hiremath＠in.bosch.com 27 May '21

27 May '21

From: Gireesh Hiremath <Gireesh.Hiremath(a)in.bosch.com> add support for updated TI clock driver, backlight, splash screen, swi logic, add ubi fastmap support, update pinmux, code clean up address the v1 review comments like: split board changes and defconfig changes into separate patches, adding clock support Gireesh Hiremath (15): am335x, guardian: configs: Enable clock driver for guardian am335x, guardian: configs: add ubi fastmap support am335x, guardian: configs: cmd: add memtest configs am335x, guardian: add memtest address range am335x, guardian: set environment variable autoload to no am335x, guardian: code cleanup and boot optimization am335x, guardian: configs: set boot delay am335x, guardian: configs: cmd : disable spl command am335x, guardian: update swi logic am335x, guardian: Enable backlight am335x, guardian: configs: Enable display config drivers: video: hx8238 fix build bug am335x, guardian: Enable panel driver Himax HX8238D am335x, guardian: software update available status is stored in AM3352 RTC scracth register am335x, guardian: configs: Enable bootcount nvmem support Moses Christopher (3): am335x, guardian: mem: Add board dependent mem values am335x, guardian: set tftp_load_addr in environment am335x, guardian: Update pinmux configuration arch/arm/dts/am335x-guardian-u-boot.dtsi | 11 ++ arch/arm/dts/am335x-guardian.dts | 14 +- .../include/asm/arch-am33xx/mem-guardian.h | 63 ++++++++ arch/arm/mach-omap2/am33xx/Kconfig | 2 + arch/arm/mach-omap2/am33xx/board.c | 4 + arch/arm/mach-omap2/mem-common.c | 4 + board/bosch/guardian/board.c | 151 +++++++++++++++--- board/bosch/guardian/mux.c | 3 +- configs/am335x_guardian_defconfig | 27 +++- drivers/bootcount/Kconfig | 27 +++- drivers/bootcount/Makefile | 1 + drivers/bootcount/bootcount_nvmem.c | 57 +++++++ drivers/video/Makefile | 2 +- drivers/video/hx8238d.c | 4 +- include/configs/am335x_guardian.h | 21 ++- 15 files changed, 349 insertions(+), 42 deletions(-) create mode 100644 arch/arm/include/asm/arch-am33xx/mem-guardian.h create mode 100644 drivers/bootcount/bootcount_nvmem.c -- 2.20.1

2 19

[PATCH] DTS: khadas-vim2 spi-flash change spi-max-frequency v2
by Artem Lapkin 27 May '21

27 May '21

change max freq to 104Mhz for SPI-NOR flash Signed-off-by: Artem Lapkin <art(a)khadas.com> --- arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi b/arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi index c1763336cf..247817adea 100644 --- a/arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi +++ b/arch/arm/dts/meson-gxm-khadas-vim2-u-boot.dtsi @@ -18,5 +18,6 @@ }; &spifc { + spi-max-frequency = <104000000>; status = "okay"; }; -- 2.25.1

2 1

[PATCH v2] mtd: spi-nor-ids: add XT25F128B flash support
by Neil Armstrong 27 May '21

27 May '21

This adds the XTX Technology Inc. flash producer Kconfig entry to enable support for the 128Mbit XT25F128B NOR SPI flash. Signed-off-by: Neil Armstrong <narmstrong(a)baylibre.com> --- drivers/mtd/spi/Kconfig | 6 ++++++ drivers/mtd/spi/spi-nor-ids.c | 4 ++++ 2 files changed, 10 insertions(+) diff --git a/drivers/mtd/spi/Kconfig b/drivers/mtd/spi/Kconfig index f8db8e5213..512b57f0db 100644 --- a/drivers/mtd/spi/Kconfig +++ b/drivers/mtd/spi/Kconfig @@ -162,6 +162,12 @@ config SPI_FLASH_XMC Add support for various XMC (Wuhan Xinxin Semiconductor Manufacturing Corp.) SPI flash chips (XM25xxx) +config SPI_FLASH_XTX + bool "XTX SPI flash support" + help + Add support for various XTX (XTX Technology Limited) + SPI flash chips (XT25xxx) + endif config SPI_FLASH_USE_4K_SECTORS diff --git a/drivers/mtd/spi/spi-nor-ids.c b/drivers/mtd/spi/spi-nor-ids.c index 2b57797954..e995a9eca7 100644 --- a/drivers/mtd/spi/spi-nor-ids.c +++ b/drivers/mtd/spi/spi-nor-ids.c @@ -336,6 +336,10 @@ const struct flash_info spi_nor_ids[] = { /* XMC (Wuhan Xinxin Semiconductor Manufacturing Corp.) */ { INFO("XM25QH64A", 0x207017, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, { INFO("XM25QH128A", 0x207018, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, +#endif +#ifdef CONFIG_SPI_FLASH_XTX + /* XTX (XTX Technology Inc.) */ + { INFO("XT25F128B", 0x0b4018, 0, 64 * 1024, 256, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) }, #endif { }, }; -- 2.25.1

1 0

[PATCH] VIM3: mmc_get_env_dev correct non emmc boot sources
by Artem Lapkin 27 May '21

27 May '21

need return -1 if boot source is not EMMC or SD ( for example it will be useful if we have multy env sources configuration and device was booted from SPI flash and env need read from SPI not from mmc ) Signed-off-by: Artem Lapkin <art(a)khadas.com> --- board/amlogic/vim3/vim3.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/board/amlogic/vim3/vim3.c b/board/amlogic/vim3/vim3.c index 6cd5f2e1..71aaa0d8 100644 --- a/board/amlogic/vim3/vim3.c +++ b/board/amlogic/vim3/vim3.c @@ -19,9 +19,15 @@ int mmc_get_env_dev(void) { - if (meson_get_boot_device() == BOOT_DEVICE_EMMC) + switch (meson_get_boot_device()) { + case BOOT_DEVICE_EMMC: return 2; - return 1; + case BOOT_DEVICE_SD: + return 1; + default: + /* boot device is not EMMC|SD */ + return -1; + } } /* -- 2.25.1

3 2

[PATCH] DTS: khadas-vim2 spi-flash change spi-max-frequency
by Artem Lapkin 27 May '21

27 May '21

change max freq to 104Mhz for SPI-NOR flash Signed-off-by: Artem Lapkin <art(a)khadas.com> --- arch/arm/dts/meson-gxm-khadas-vim2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/dts/meson-gxm-khadas-vim2.dts b/arch/arm/dts/meson-gxm-khadas-vim2.dts index bff8ec2c1c..e2bd9c7c81 100644 --- a/arch/arm/dts/meson-gxm-khadas-vim2.dts +++ b/arch/arm/dts/meson-gxm-khadas-vim2.dts @@ -341,7 +341,7 @@ #size-cells = <1>; compatible = "winbond,w25q16", "jedec,spi-nor"; reg = <0>; - spi-max-frequency = <3000000>; + spi-max-frequency = <104000000>; }; }; -- 2.25.1

2 1

[PATCH RFC 0/2] lib: Remove the need for a HASH_CALCULATE config
by Alexandru Gagniuc 27 May '21

27 May '21

I had accidentally noticed commit 87316da05f2f ("lib: introduce HASH_CALCULATE option"), when rebasing an unrelated series. It immediately caught my attention because It seemed to me to increase complexity, without any actual benefit. In this series, I present an alternative approach, which solves the problem by leveraging existing infrastructure instead of adding more Kconfig variables. Alexandru Gagniuc (2): Revert "lib: introduce HASH_CALCULATE option" efi_loader: Work-around build issue due to missing hash_calculate() common/Kconfig.boot | 1 - lib/Kconfig | 3 --- lib/Makefile | 2 +- lib/efi_loader/Kconfig | 4 ++-- 4 files changed, 3 insertions(+), 7 deletions(-) -- 2.31.1

4 5

[PATCH] MAINTAINERS: Add allwinner/sunxi driver directories
by Samuel Holland 27 May '21

27 May '21

These drivers are sunxi platform-specific, and so are of interest to the sunxi maintainers. In fact, as there is no PHY driver maintainer, drivers/phy/allwinner had no maintainer at all. Signed-off-by: Samuel Holland <samuel(a)sholland.org> --- MAINTAINERS | 3 +++ 1 file changed, 3 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index c6dd9bf838..2d66831694 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -478,6 +478,9 @@ F: arch/arm/cpu/armv7/sunxi/ F: arch/arm/include/asm/arch-sunxi/ F: arch/arm/mach-sunxi/ F: board/sunxi/ +F: drivers/clk/sunxi/ +F: drivers/phy/allwinner/ +F: drivers/video/sunxi/ ARM TEGRA M: Tom Warren <twarren(a)nvidia.com> -- 2.26.3

3 3

[PATCH 0/3] sunxi: dts: Update H3/H5/H6 devicetree from Linux
by Andre Przywara 27 May '21

27 May '21

This syncs the SoC .dtsi and board .dts files from the Linux 5.12 release. For the H3 and H5 this brings us the proper RGMII modes for the boards with Gigabit Ethernet PHYs. The rest are smaller updates, but bring us port 0 USB support on the H6 boards in U-Boot. I know it's a bit late in the game, but those changes look innocent enough to make it into the v2021.07 release still. This way we have all 64-bit boards using Linux 5.12 DTs. Cheers, Andre Andre Przywara (3): arm: dts: sunxi: h6: Update DT files arm: dts: sunxi: h5: Update DT files arm: dts: sunxi: h3: Update DT files .../dts/sun50i-h5-bananapi-m2-plus-v1.2.dts | 1 + arch/arm/dts/sun50i-h5-cpu-opp.dtsi | 79 +++++++++++++++ .../arm/dts/sun50i-h5-libretech-all-h3-cc.dts | 1 + .../arm/dts/sun50i-h5-libretech-all-h5-cc.dts | 2 +- arch/arm/dts/sun50i-h5-nanopi-neo-plus2.dts | 6 +- arch/arm/dts/sun50i-h5-nanopi-neo2.dts | 4 +- arch/arm/dts/sun50i-h5-orangepi-pc2.dts | 27 +++++- arch/arm/dts/sun50i-h5-orangepi-prime.dts | 6 +- arch/arm/dts/sun50i-h5-orangepi-zero-plus.dts | 4 +- .../arm/dts/sun50i-h5-orangepi-zero-plus2.dts | 38 ++++++++ arch/arm/dts/sun50i-h5.dtsi | 61 ++++++++++-- arch/arm/dts/sun50i-h6-beelink-gs1.dts | 6 +- arch/arm/dts/sun50i-h6-cpu-opp.dtsi | 20 ++-- arch/arm/dts/sun50i-h6-orangepi-3.dts | 4 +- arch/arm/dts/sun50i-h6-orangepi.dtsi | 4 +- arch/arm/dts/sun50i-h6-pine-h64.dts | 7 +- arch/arm/dts/sun50i-h6.dtsi | 26 +++++ .../dts/sun8i-h2-plus-bananapi-m2-zero.dts | 96 ++++++++++++++++++- arch/arm/dts/sun8i-h3-beelink-x2.dts | 4 +- arch/arm/dts/sun8i-h3-nanopi-duo2.dts | 4 +- arch/arm/dts/sun8i-h3-nanopi-neo-air.dts | 4 +- arch/arm/dts/sun8i-h3-nanopi.dtsi | 4 +- arch/arm/dts/sun8i-h3-orangepi-pc-plus.dts | 5 - arch/arm/dts/sun8i-h3-orangepi-plus2e.dts | 2 +- arch/arm/dts/sun8i-h3-orangepi-zero-plus2.dts | 38 ++++++++ arch/arm/dts/sun8i-h3.dtsi | 49 +++++++++- arch/arm/dts/sunxi-h3-h5.dtsi | 42 +++++++- 27 files changed, 483 insertions(+), 61 deletions(-) create mode 100644 arch/arm/dts/sun50i-h5-cpu-opp.dtsi -- 2.17.5

1 3

[PATCH] fastboot: Fix overflow when calculating chunk size
by Sean Anderson 26 May '21

26 May '21

If a chunk was larger than 4GiB, then chunk_data_sz would overflow and blkcnt would not be calculated correctly. Upgrade it to a u64 and cast its multiplicands as well. Also fix bytes_written while we're at it. Signed-off-by: Sean Anderson <sean.anderson(a)seco.com> --- lib/image-sparse.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/lib/image-sparse.c b/lib/image-sparse.c index 187ac28cd3..52c8dcc08c 100644 --- a/lib/image-sparse.c +++ b/lib/image-sparse.c @@ -55,10 +55,10 @@ int write_sparse_image(struct sparse_storage *info, lbaint_t blk; lbaint_t blkcnt; lbaint_t blks; - uint32_t bytes_written = 0; + uint64_t bytes_written = 0; unsigned int chunk; unsigned int offset; - unsigned int chunk_data_sz; + uint64_t chunk_data_sz; uint32_t *fill_buf = NULL; uint32_t fill_val; sparse_header_t *sparse_header; @@ -132,7 +132,7 @@ int write_sparse_image(struct sparse_storage *info, sizeof(chunk_header_t)); } - chunk_data_sz = sparse_header->blk_sz * chunk_header->chunk_sz; + chunk_data_sz = ((u64)sparse_header->blk_sz) * chunk_header->chunk_sz; blkcnt = chunk_data_sz / info->blksz; switch (chunk_header->chunk_type) { case CHUNK_TYPE_RAW: @@ -162,7 +162,7 @@ int write_sparse_image(struct sparse_storage *info, return -1; } blk += blks; - bytes_written += blkcnt * info->blksz; + bytes_written += ((u64)blkcnt) * info->blksz; total_blocks += chunk_header->chunk_sz; data += chunk_data_sz; break; @@ -222,7 +222,7 @@ int write_sparse_image(struct sparse_storage *info, blk += blks; i += j; } - bytes_written += blkcnt * info->blksz; + bytes_written += ((u64)blkcnt) * info->blksz; total_blocks += chunk_data_sz / sparse_header->blk_sz; free(fill_buf); break; @@ -253,7 +253,7 @@ int write_sparse_image(struct sparse_storage *info, debug("Wrote %d blocks, expected to write %d blocks\n", total_blocks, sparse_header->total_blks); - printf("........ wrote %u bytes to '%s'\n", bytes_written, part_name); + printf("........ wrote %llu bytes to '%s'\n", bytes_written, part_name); if (total_blocks != sparse_header->total_blks) { info->mssg("sparse image write failure", response); -- 2.25.1

4 6

RZ/G2 USB tree question
by Adam Ford 26 May '21

26 May '21

I have a board with multiple USB controllers, but they all seem to show in index of 1 with usb tree. USB device tree: 1 Hub (5 Gb/s, 0mA) U-Boot XHCI Host Controller 1 Hub (480 Mb/s, 0mA) u-boot EHCI Host Controller 1 Hub (480 Mb/s, 0mA) | u-boot EHCI Host Controller | +-2 Hub (480 Mb/s, 2mA) | +-3 Mass Storage (480 Mb/s, 200mA) | Generic Mass Storage 20621F3F | +-4 Mass Storage (480 Mb/s, 224mA) SanDisk Ultra USB 3.0 4C530001010924108332 => Is this normal behavior? I thought the different hubs would have unique numbers similar to how the devices connected to a lower hub each have unique numbers adam

1 0