July 2024 - U-Boot

[PATCH 0/9] Bug-fixes for a few boards
by Simon Glass 31 Jul '24

31 Jul '24

This series includes fixes to get some rockchip and nvidia boards working again. It also provides a fix (revert) for Beaglebone Black and a devicetree fix for coral (x86). Simon Glass (9): nvidia: nyan-big: Disable debug UART tpm: Avoid code bloat when not using EFI_TCG2_PROTOCOL rockchip: veyron: Add logging for power init power: regulator: Handle autoset in regulators_enable_boot_on() fdt: Correct condition for bloblist existing spl: Allow ATF to work when dcache is disabled rockchip: bob: kevin: Disable dcache in SPL regulator: rk8xx: Fix incorrect parameter Revert "arm: am335x: Enable SPL_OF_CONTROL on some configs" board/google/veyron/veyron.c | 27 ++++++++++------------ common/spl/spl_atf.c | 3 ++- configs/am335x_boneblack_vboot_defconfig | 1 - configs/chromebook_bob_defconfig | 1 + configs/chromebook_kevin_defconfig | 1 + configs/nyan-big_defconfig | 1 - drivers/power/regulator/regulator-uclass.c | 2 +- drivers/power/regulator/rk8xx.c | 2 +- lib/Kconfig | 8 +++---- lib/fdtdec.c | 12 ++++++++-- 10 files changed, 32 insertions(+), 26 deletions(-) -- 2.34.1

7 44

[PATCH] usb: bootm: Drop old USB-device-removal code
by Simon Glass 31 Jul '24

31 Jul '24

USB is stopped using driver model now, in dm_remove_devices_flags() in announce_and_cleanup() at the top of this file. The usb_stop() call actually unbinds devices. When a USB device is unbound, it causes any bootflows attached to it to be removed, via a call to bootdev_clear_bootflows() from bootdev_pre_unbind(). This obviously makes it impossible to boot the bootflow. However, when booting a bootflow that relies on USB, usb_stop() is called, which unbinds the device. At that point any information attached to the bootflow is dropped. This is quite risky since the contents of freed memory are not guaranteed to remain unchanged. Depending on what other options are done before boot, a hard-to-find bug may crop up. Drop the call to this old function. Leave the netconsole call there, since this needs conversion to driver model. Signed-off-by: Simon Glass <sjg(a)chromium.org> Suggested-by: Shantur Rathore <i(a)shantur.com> --- The original patch was here: https://patchwork.ozlabs.org/project/uboot/patch/ 20231119121144.v5.5.If206027372f73ce32480223e5626f4b944e281b7@changeid/ boot/bootm.c | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/boot/bootm.c b/boot/bootm.c index 376d63aafc9..480f8e6a0e6 100644 --- a/boot/bootm.c +++ b/boot/bootm.c @@ -740,18 +740,6 @@ ulong bootm_disable_interrupts(void) eth_halt(); #endif -#if defined(CONFIG_CMD_USB) - /* - * turn off USB to prevent the host controller from writing to the - * SDRAM while Linux is booting. This could happen (at least for OHCI - * controller), because the HCCA (Host Controller Communication Area) - * lies within the SDRAM and the host controller writes continously to - * this area (as busmaster!). The HccaFrameNumber is for example - * updated every 1 ms within the HCCA structure in SDRAM! For more - * details see the OpenHCI specification. - */ - usb_stop(); -#endif return iflag; } -- 2.34.1

3 2

[PATCH v3] tools: Add script to update git subtree projects
by Raymond Mao 31 Jul '24

31 Jul '24

Recently we are introducing multiple git subtree projects and it is the right time to have a universal script to update various subtrees and replace the dts/update-dts-subtree.sh. update-subtree.sh is a wrapper of git subtree commands. Usage: From U-Boot top directory, run $ ./tools/update-subtree.sh pull <subtree-name> <release-tag> for pulling a tag from the upstream. Or run $ ./tools/update-subtree.sh pick <subtree-name> <commit-id> for cherry-pick a commit from the upstream. Currently <subtree-name> supports dts, mbedtls and lwip. Signed-off-by: Raymond Mao <raymond.mao(a)linaro.org> --- Changes in v2 - Refactored the script. - Update the control doc. Changes in v3 - Remove authorship from the file header. doc/develop/devicetree/control.rst | 8 +-- dts/update-dts-subtree.sh | 48 ----------------- tools/update-subtree.sh | 85 ++++++++++++++++++++++++++++++ 3 files changed, 89 insertions(+), 52 deletions(-) delete mode 100755 dts/update-dts-subtree.sh create mode 100755 tools/update-subtree.sh diff --git a/doc/develop/devicetree/control.rst b/doc/develop/devicetree/control.rst index ca4fb0b5b10..211f7e4909c 100644 --- a/doc/develop/devicetree/control.rst +++ b/doc/develop/devicetree/control.rst @@ -96,12 +96,12 @@ sync the `dts/upstream/` subtree from the devicetree-rebasing repo whenever the next branch opens (refer: :doc:`../release_cycle`) with the latest mainline Linux kernel release. To sync the `dts/upstream/` subtree, run:: - ./dts/update-dts-subtree.sh pull <devicetree-rebasing-release-tag> + ./tools/update-subtree.sh pull dts <devicetree-rebasing-release-tag> If required it is also possible to cherry-pick fixes from the devicetree-rebasing repository prior to next sync, usage:: - ./dts/update-dts-subtree.sh pick <devicetree-rebasing-commit-id> + ./tools/update-subtree.sh pick dts <devicetree-rebasing-commit-id> Configuration @@ -116,8 +116,8 @@ However, if `dts/upstream/` hasn't yet received devicetree source file for your newly added board support then one option is that you can add the corresponding devicetree source file as `arch/<arch>/dts/<name>.dts`. To select that add `# CONFIG_OF_UPSTREAM is not set` and set `DEFAULT_DEVICE_TREE=<name>` when -prompted by Kconfig. Another option is that you can use use the "pick" option of -`dts/update-dts-subtree.sh` mentioned above to bring in the commits that you +prompted by Kconfig. Another option is that you can use the "pick" option of +`tools/update-subtree.sh` mentioned above to bring in the commits that you need. This should include your CPU or SoC's devicetree file. On top of that any U-Boot diff --git a/dts/update-dts-subtree.sh b/dts/update-dts-subtree.sh deleted file mode 100755 index a57b78a41d3..00000000000 --- a/dts/update-dts-subtree.sh +++ /dev/null @@ -1,48 +0,0 @@ -#!/bin/sh -# SPDX-License-Identifier: GPL-2.0+ -# -# Copyright 2024 Linaro Ltd. -# -# Usage: from the top level U-Boot source tree, run: -# $ ./dts/update-dts-subtree.sh pull <release-tag> -# $ ./dts/update-dts-subtree.sh pick <commit-id> -# -# The script will pull changes from devicetree-rebasing repo into U-Boot -# as a subtree located as <U-Boot>/dts/upstream sub-directory. It will -# automatically create a squash/merge commit listing the commits imported. - -set -e - -merge_commit_msg=$(cat << EOF -Subtree merge tag '$2' of devicetree-rebasing repo [1] into dts/upstream - -[1] https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas… -EOF -) - -remote_add_and_fetch() { - if ! git remote get-url devicetree-rebasing 2>/dev/null - then - echo "Warning: Script automatically adds new git remote via:" - echo " git remote add devicetree-rebasing \\" - echo " https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas…" - git remote add devicetree-rebasing \ - https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicetree-rebas… - fi - git fetch devicetree-rebasing master -} - -if [ "$1" = "pull" ] -then - remote_add_and_fetch - git subtree pull --prefix dts/upstream devicetree-rebasing \ - "$2" --squash -m "${merge_commit_msg}" -elif [ "$1" = "pick" ] -then - remote_add_and_fetch - git cherry-pick -x --strategy=subtree -Xsubtree=dts/upstream/ "$2" -else - echo "usage: $0 <op> <ref>" - echo " <op> pull or pick" - echo " <ref> release tag [pull] or commit id [pick]" -fi diff --git a/tools/update-subtree.sh b/tools/update-subtree.sh new file mode 100755 index 00000000000..536b3318573 --- /dev/null +++ b/tools/update-subtree.sh @@ -0,0 +1,85 @@ +#!/bin/sh +# SPDX-License-Identifier: GPL-2.0+ +# +# Copyright (c) 2024 Linaro Limited +# +# Usage: from the top level U-Boot source tree, run: +# $ ./tools/update-subtree.sh pull <subtree-name> <release-tag> +# Or: +# $ ./tools/update-subtree.sh pick <subtree-name> <commit-id> +# +# The script will pull changes from subtree repo into U-Boot. +# It will automatically create a squash/merge commit listing the commits +# imported. + +set -e + +print_usage() { + echo "usage: $0 <op> <subtree-name> <ref>" + echo " <op> pull or pick" + echo " <subtree-name> mbedtls or dts or lwip" + echo " <ref> release tag [pull] or commit id [pick]" +} + +if [ $# -ne 3 ]; then + print_usage + exit 1 +fi + +op=$1 +subtree_name=$2 +ref=$3 + +set_params() { + case "$subtree_name" in + mbedtls) + path=lib/mbedtls/external/mbedtls + repo_url=https://github.com/Mbed-TLS/mbedtls.git + remote_name="mbedtls_upstream" + ;; + dts) + path=dts/upstream + repo_url=https://git.kernel.org/pub/scm/linux/kernel/git/devicetree/devicet… + remote_name="devicetree-rebasing" + ;; + lwip) + path=lib/lwip/lwip + repo_url=https://git.savannah.gnu.org/git/lwip.git + remote_name="lwip_upstream" + ;; + *) + echo "Invalid subtree name: $subtree_name" + print_usage + exit 1 + esac +} + +set_params + +merge_commit_msg=$(cat << EOF +Subtree merge tag '$ref' of $subtree_name repo [1] into $path + +[1] $repo_url +EOF +) + +remote_add_and_fetch() { + if [ -z "$(git remote get-url $remote_name 2>/dev/null)" ]; then + echo "Warning: Script automatically adds new git remote via:" + echo " git remote add $remote_name \\" + echo " $repo_url" + git remote add $remote_name $repo_url + fi + git fetch $remote_name master +} + +if [ "$op" = "pull" ]; then + remote_add_and_fetch + git subtree pull --prefix $path $remote_name "$ref" --squash -m "$merge_commit_msg" +elif [ "$op" = "pick" ]; then + remote_add_and_fetch + git cherry-pick -x --strategy=subtree -Xsubtree=$path/ "$ref" +else + print_usage + exit 1 +fi -- 2.25.1

2 1

[PATCH] env: mmc: Fix env loading with CONFIG_SYS_MMC_ENV_PART
by Mattijs Korpershoek 31 Jul '24

31 Jul '24

When CONFIG_SYS_MMC_ENV_PART=2, the environment is loaded from the USER partition (hwpart=0) instead of from the BOOT1 partition (hwpart=2). IS_ENABLED() cannot be used for non-boolean KConfig options. Its documentation states: > * IS_ENABLED(CONFIG_FOO) evaluates to 1 if CONFIG_FOO is set to 'y', > * 0 otherwise. So in our case, IS_ENABLED(CONFIG_SYS_MMC_ENV_PART) evaluates to 0. Because of this, the hwpart variable is never assigned and mmc_offset() ends up switching back to the USER hwpart (0) instead of BOOT1 (2). Fix it by using #define instead. Tested with: # have CONFIG_SYS_MMC_ENV_PART=2 in defconfig # 1. Erase mmc0boot1 => mmc dev 0 2 => mmc erase 0 400 => mmc read ${loadaddr} 0 400 => md ${loadaddr} 4 82000000: 00000000 00000000 00000000 00000000 ................ # 2. Restore default environment and save to MMC => env default -a -f => saveenv # 3. Read back mmc0boot1 and confirm the env is present => mmc read ${loadaddr} 0 400 => md ${loadaddr} 4 82000000: 13e0632e 72646461 7469665f 3978303d .c..addr_fit=0x9 Fixes: 5b4acb0ff79d ("env: mmc: Apply GPT only on eMMC user HW partition") Signed-off-by: Mattijs Korpershoek <mkorpershoek(a)baylibre.com> --- env/mmc.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/env/mmc.c b/env/mmc.c index 776df0786be5..0338aa6c56ad 100644 --- a/env/mmc.c +++ b/env/mmc.c @@ -110,8 +110,9 @@ static inline s64 mmc_offset(struct mmc *mmc, int copy) int hwpart = 0; int err; - if (IS_ENABLED(CONFIG_SYS_MMC_ENV_PART)) - hwpart = mmc_get_env_part(mmc); +#if defined(CONFIG_SYS_MMC_ENV_PART) + hwpart = mmc_get_env_part(mmc); +#endif #if defined(CONFIG_ENV_MMC_PARTITION) str = CONFIG_ENV_MMC_PARTITION; --- base-commit: 459560000736ac7c9c8b04522789c20fb45ff95a change-id: 20240719-fix-mmc-env-boot1-a8d4b4512a29 Best regards, -- Mattijs Korpershoek <mkorpershoek(a)baylibre.com>

2 2

[PATCH 0/2] Endian Kconfig improvements
by Jiaxun Yang 31 Jul '24

31 Jul '24

This is a subset of my previous arm64_be work. I wish this could be merged first so it would be easier to work against xtensa and arm64 be support. Thanks Signed-off-by: Jiaxun Yang <jiaxun.yang(a)flygoat.com> --- Jiaxun Yang (2): Kconfig: Unify endian support option config: Use CONFIG_SYS_BIG_ENDIAN in code whenever possible Makefile | 2 +- arch/Kconfig | 34 +++++++++++++++++----- arch/arc/include/asm/arc-bcr.h | 10 +++---- .../arm/cpu/armv8/linux-kernel-image-header-vars.h | 4 +-- arch/mips/Kconfig | 20 +++++-------- arch/mips/mach-ath79/Kconfig | 8 ++--- arch/mips/mach-bmips/Kconfig | 20 ++++++------- arch/mips/mach-jz47xx/Kconfig | 2 +- arch/mips/mach-mscc/Kconfig | 4 +-- arch/mips/mach-pic32/Kconfig | 2 +- drivers/mtd/nand/raw/brcmnand/brcmnand.c | 2 +- scripts/Makefile.build | 2 +- 12 files changed, 61 insertions(+), 49 deletions(-) --- base-commit: 902d8ee94ce29a088a325da6e69eeb1a25f1fec7 change-id: 20240717-edian-faaff1da6e44 Best regards, -- Jiaxun Yang <jiaxun.yang(a)flygoat.com>

2 3

[PATCH v4 0/5] video: Improve syncing performance with cyclic
by Simon Glass 31 Jul '24

31 Jul '24

Now that U-Boot has a background-processing feature, it is possible to reduce the amount of 'foreground' syncing of the display. At present this happens quite often. Foreground syncing blocks all other processing, sometimes for 10ms or more. When pasting commands into U-Boot over the UART, this typically result in characters being dropped. For example, on rpi_4 it isn't possible to paste in more than 35 characters before things fail. This makes updating the environment or entering long commands very painful over the console, since text must be pasted in chunks, or the vidconsole device must be dropped from stdout. This series introduces background syncing, enabled by default for boards which use video. The sync rates for foreground and background are configurable. With this series it is possible to paste in any amount of text to the command line. Some sandbox-specific workarounds can now be removed and sandbox video (./u-boot -Dl) is significantly more responsive. This obviously increases code size, since it enables a subsystem not normally used by default. However it only applies to boards which have VIDEO enabled, which are presumably less worried about memory space since the video code is fairly large. Also it is possible to disable CMD_CYCLIC and reduce the growth to: aarch64: (for 1/1 boards) all +1081.0 rodata +65.0 text +1016.0 arm: (for 1/1 boards) all +945.0 rodata +65.0 text +880.0 Without that, the increase doubles. It is of course possible to disable CYCLIC and still use VIDEO but this reverts to the current behaviour Changes in v4: - Imply SPL_CYCLIC if WATCHDOG is enabled Changes in v3: - Drop inclusion of kconfig.h in cyclic.h - Adapt to new cyclic API Changes in v2: - Add an SPL_CYCLIC symbol - Add a lot more explanation about the header files - Expand help for CONFIG_VIDEO - Fix 'groth' and 'work-around' typos in cover letter Simon Glass (5): cyclic: Add a symbol for SPL video: Move last_sync to private data video: Use cyclic to handle video sync sandbox: Increase cyclic CPU-time limit sandbox: Drop video-sync in serial driver common/Kconfig | 9 ++++++ common/Makefile | 2 +- drivers/serial/sandbox.c | 2 -- drivers/video/Kconfig | 35 +++++++++++++++++++++ drivers/video/video-uclass.c | 52 +++++++++++++++++++++++++------ drivers/watchdog/Kconfig | 2 ++ include/asm-generic/global_data.h | 2 +- include/cyclic.h | 5 +-- include/video.h | 2 ++ 9 files changed, 96 insertions(+), 15 deletions(-) -- 2.34.1

2 6

[PATCH RFC] gpio: Fix probing of gpio-hogs
by Chris Webb 31 Jul '24

31 Jul '24

48b3ecbe replumbed the gpio-hog probing to use DM_FLAG_PROBE_AFTER_BIND. Unfortunately gpio_post_bind is called after the non-preloc recursive dm_probe_devices completes, so setting this flag does not have the intended effect and the gpio-hogs never get probed. With instrumentation: [...] CPU: MediaTek MT7981 Model: GL.iNet GL-X3000 DRAM: 512 MiB <mtk_pinctrl_mt7981_bind called> <dm_probe_devices called: root root_driver root_driver [+] [ ]> <dm_probe_devices called: clk fixed_clock gpt_dummy20m [ ] [ ]> [...] <dm_probe_devices called: led gpio_led signal-4 [ ] [ ]> Core: 34 devices, 14 uclasses, devicetree: separate MMC: <gpio_post_bind called> mmc@11230000: 0 [...] Probe them directly in gpio_post_bind instead. Signed-off-by: Chris Webb <chris(a)arachsys.com> --- drivers/gpio/gpio-uclass.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-uclass.c b/drivers/gpio/gpio-uclass.c index 4234cd91..1c6e1715 100644 --- a/drivers/gpio/gpio-uclass.c +++ b/drivers/gpio/gpio-uclass.c @@ -1539,7 +1539,9 @@ static int gpio_post_bind(struct udevice *dev) * since hogs can be essential to the hardware * system. */ - dev_or_flags(child, DM_FLAG_PROBE_AFTER_BIND); + ret = device_probe(child); + if (ret) + return ret; } } }

3 12

Pull request efi-2024-10-rc2
by Heinrich Schuchardt 31 Jul '24

31 Jul '24

Dear Tom, The following changes since commit 8877bc51a8a4d921ba2f163208b8b1a57ba47c18: Merge patch series "led: implement software blinking" (2024-07-30 14:31:24 -0600) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-efi.git tags/efi-2024-10-rc2 for you to fetch changes up to 939afc80b6b5de23d70789f3cb3a391dd31319b1: dm: use list_count_nodes() for counting list nodes (2024-07-31 09:54:53 +0200) ---------------------------------------------------------------- Pull request efi-2024-10-rc2 Documentation: * Add a description for bootmeth_android UEFI: * Provide and use function list_count_nodes() * Require EFI boot manager for EBBR compliance * Correct check in efi_load_option_dp_join() * Adjust config options for capsule updates SMBIOS: * Add extended Extended BIOS ROM Size ---------------------------------------------------------------- Caleb Connolly (1): efi_loader: add /dtbs search path Heinrich Schuchardt (3): efi_loader: require EFI boot manager for EBBR compliance smbios: add extended Extended BIOS ROM Size efi_loader: correct check in efi_load_option_dp_join() Ilias Apalodimas (1): efi_loader: adjust config options for capsule updates Mattijs Korpershoek (1): doc: Add a description for bootmeth_android Sughosh Ganu (5): linux: list: add a function to count list nodes efi_memory: use list_count_nodes() to count list entries efi_memory: avoid possible null pointer dereference efi_memory: get the efi_mem_list node directly dm: use list_count_nodes() for counting list nodes MAINTAINERS | 1 + doc/develop/bootstd/android.rst | 39 +++++++++++++++++++++++++++++++++++++++ doc/develop/bootstd/index.rst | 1 + doc/develop/bootstd/overview.rst | 2 +- drivers/core/util.c | 14 ++------------ include/dm/util.h | 8 -------- include/linux/list.h | 15 +++++++++++++++ include/smbios.h | 1 + lib/efi_loader/Kconfig | 2 ++ lib/efi_loader/efi_fdt.c | 3 +++ lib/efi_loader/efi_helper.c | 2 +- lib/efi_loader/efi_memory.c | 33 ++++++++++++--------------------- lib/smbios.c | 9 ++++++++- test/dm/bus.c | 5 +++-- test/dm/core.c | 9 +++++---- test/dm/test-fdt.c | 5 +++-- 16 files changed, 97 insertions(+), 52 deletions(-) create mode 100644 doc/develop/bootstd/android.rst

2 1

[PATCH] arm: dts: orangepi: Fix Orange Pi R1 and Plus LTS boot issue
by Pugemon 31 Jul '24

31 Jul '24

Orange Pi R1 Plus and LTS don't have eMMC (default mmc0 in rk3328-u-boot.dtsi). The device is equipped with SPI flash memory, which U-Boot tries to use for reading configuration. However, the manufacturer has not provided any means to utilize SPI flash memory. There is no documentation, or software available for this purpose. As a result, during OpenWRT sysupgrade, the board fails to boot because the script that switches the boot_device to an available one does not trigger. This patch changes the alias of mmc0 from &emmc to &sdmmc, ensuring the board boots correctly, and sysupgrade completes successfully. Additionally, this allows saving the U-Boot environment by using saveenv with uboot-envtool. Signed-off-by: Pugemon <islavaivanov76(a)gmail.com> Cc: Tianling Shen <cnsztl(a)gmail.com> --- arch/arm/dts/rk3328-orangepi-r1-plus-lts-u-boot.dtsi | 12 ++++++++++++ arch/arm/dts/rk3328-orangepi-r1-plus-u-boot.dtsi | 12 ++++++++++++ 2 files changed, 24 insertions(+) diff --git a/arch/arm/dts/rk3328-orangepi-r1-plus-lts-u-boot.dtsi b/arch/arm/dts/rk3328-orangepi-r1-plus-lts-u-boot.dtsi index b50c1332b8..7063b188f2 100644 --- a/arch/arm/dts/rk3328-orangepi-r1-plus-lts-u-boot.dtsi +++ b/arch/arm/dts/rk3328-orangepi-r1-plus-lts-u-boot.dtsi @@ -2,11 +2,23 @@ /* * (C) Copyright 2018-2019 Rockchip Electronics Co., Ltd * (C) Copyright 2020 David Bauer + * (C) Copyright 2024 Pugemon */ #include "rk3328-u-boot.dtsi" #include "rk3328-sdram-lpddr3-666.dtsi" +/ { + aliases { + mmc0 = &sdmmc; + spi0 = &spi0; + }; + + chosen { + u-boot,spl-boot-order = "same-as-spl", &sdmmc; + }; +}; + &spi0 { flash@0 { bootph-pre-ram; diff --git a/arch/arm/dts/rk3328-orangepi-r1-plus-u-boot.dtsi b/arch/arm/dts/rk3328-orangepi-r1-plus-u-boot.dtsi index 8ae003bbef..0374172527 100644 --- a/arch/arm/dts/rk3328-orangepi-r1-plus-u-boot.dtsi +++ b/arch/arm/dts/rk3328-orangepi-r1-plus-u-boot.dtsi @@ -2,11 +2,23 @@ /* * (C) Copyright 2018-2019 Rockchip Electronics Co., Ltd * (C) Copyright 2020 David Bauer + * (C) Copyright 2024 Pugemon */ #include "rk3328-u-boot.dtsi" #include "rk3328-sdram-ddr4-666.dtsi" +/ { + aliases { + mmc0 = &sdmmc; + spi0 = &spi0; + }; + + chosen { + u-boot,spl-boot-order = "same-as-spl", &sdmmc; + }; +}; + &spi0 { flash@0 { bootph-pre-ram;

2 1

[PATCH v3 0/5] video: Improve syncing performance with cyclic
by Simon Glass 31 Jul '24

31 Jul '24

Now that U-Boot has a background-processing feature, it is possible to reduce the amount of 'foreground' syncing of the display. At present this happens quite often. Foreground syncing blocks all other processing, sometimes for 10ms or more. When pasting commands into U-Boot over the UART, this typically result in characters being dropped. For example, on rpi_4 it isn't possible to paste in more than 35 characters before things fail. This makes updating the environment or entering long commands very painful over the console, since text must be pasted in chunks, or the vidconsole device must be dropped from stdout. This series introduces background syncing, enabled by default for boards which use video. The sync rates for foreground and background are configurable. With this series it is possible to paste in any amount of text to the command line. Some sandbox-specific workarounds can now be removed and sandbox video (./u-boot -Dl) is significantly more responsive. This obviously increases code size, since it enables a subsystem not normally used by default. However it only applies to boards which have VIDEO enabled, which are presumably less worried about memory space since the video code is fairly large. Also it is possible to disable CMD_CYCLIC and reduce the growth to: aarch64: (for 1/1 boards) all +1081.0 rodata +65.0 text +1016.0 arm: (for 1/1 boards) all +945.0 rodata +65.0 text +880.0 Without that, the increase doubles. It is of course possible to disable CYCLIC and still use VIDEO but this reverts to the current behaviour Changes in v3: - Drop inclusion of kconfig.h in cyclic.h - Adapt to new cyclic API Changes in v2: - Add an SPL_CYCLIC symbol - Add a lot more explanation about the header files - Expand help for CONFIG_VIDEO - Fix 'groth' and 'work-around' typos in cover letter Simon Glass (5): cyclic: Add a symbol for SPL video: Move last_sync to private data video: Use cyclic to handle video sync sandbox: Increase cyclic CPU-time limit sandbox: Drop video-sync in serial driver common/Kconfig | 9 ++++++ common/Makefile | 2 +- drivers/serial/sandbox.c | 2 -- drivers/video/Kconfig | 35 +++++++++++++++++++++ drivers/video/video-uclass.c | 52 +++++++++++++++++++++++++------ drivers/watchdog/Kconfig | 1 + include/asm-generic/global_data.h | 2 +- include/cyclic.h | 5 +-- include/video.h | 2 ++ 9 files changed, 95 insertions(+), 15 deletions(-) -- 2.34.1

3 12