March 2022 - U-Boot

[PULL] u-boot-riscv/master
by Leo Liang 16 Mar '22

16 Mar '22

Hi Tom, The following changes since commit c149bf41404e34014e37de32fac332892b11bd4a: Prepare v2022.04-rc4 (2022-03-14 16:39:08 -0400) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-riscv.git for you to fetch changes up to aa34e13346cf727197981c599f688b406005049a: pinctrl: k210: Fix bias-pull-up (2022-03-15 17:43:11 +0800) CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/11297 ---------------------------------------------------------------- Damien Le Moal (4): k210: use the board vendor name rather than the marketing name k210: dts: add missing power bus clocks k210: dts: align fpioa node with Linux spi: dw: Force set K210 fifo length to 31 Niklas Cassel (3): k210: dts: align plic node with Linux pinctrl: k210: Fix loop in k210_pc_get_drive() pinctrl: k210: Fix bias-pull-up Sean Anderson (1): spi: dw: Actually mask interrupts MAINTAINERS | 12 +- arch/riscv/dts/k210-maix-bit.dts | 3 +- arch/riscv/dts/k210.dtsi | 177 ++++++++++++--------- board/sipeed/maix/maix.c | 2 +- doc/board/sipeed/maix.rst | 20 +-- ...ryte,k210-sysctl.txt => canaan,k210-sysctl.txt} | 8 +- ...ndryte,k210-fpioa.txt => canaan,k210-fpioa.txt} | 12 +- doc/device-tree-bindings/spi/snps,dw-apb-ssi.txt | 4 +- drivers/clk/Makefile | 2 +- drivers/clk/{clk_kendryte.c => clk_k210.c} | 4 +- drivers/pinctrl/Makefile | 2 +- .../pinctrl/{pinctrl-kendryte.c => pinctrl-k210.c} | 25 ++- drivers/spi/designware_spi.c | 20 ++- include/configs/sipeed-maix.h | 2 +- include/{kendryte => k210}/pll.h | 0 test/dm/k210_pll.c | 2 +- 16 files changed, 174 insertions(+), 121 deletions(-) rename doc/device-tree-bindings/mfd/{kendryte,k210-sysctl.txt => canaan,k210-sysctl.txt} (78%) rename doc/device-tree-bindings/pinctrl/{kendryte,k210-fpioa.txt => canaan,k210-fpioa.txt} (91%) rename drivers/clk/{clk_kendryte.c => clk_k210.c} (99%) rename drivers/pinctrl/{pinctrl-kendryte.c => pinctrl-k210.c} (97%) rename include/{kendryte => k210}/pll.h (100%) Best regards, Leo

2 1

[PULL] u-boot-sh/master
by Marek Vasut 16 Mar '22

16 Mar '22

Config tweaks to enable the right I2C driver The following changes since commit c96137000e4cf486dcb164fd67a1a0b5b2fb99c6: Merge tag 'efi-2022-04-rc3-2' of https://source.denx.de/u-boot/custodians/u-boot-efi (2022-03-13 08:18:17 -0400) are available in the Git repository at: git://source.denx.de/u-boot-sh.git master for you to fetch changes up to 23fd0bb987c781d2f87af6b546fb219b40ad1057: configs: condor: Enabled I2C support for R-Car V3H (2022-03-14 11:49:17 +0100) ---------------------------------------------------------------- Nam Nguyen (3): configs: falcon: Enabled I2C support for R-Car V3U configs: eagle: Enabled I2C support for R-Car V3M configs: condor: Enabled I2C support for R-Car V3H configs/r8a77970_eagle_defconfig | 2 +- configs/r8a77980_condor_defconfig | 2 +- configs/r8a779a0_falcon_defconfig | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)

2 1

[PATCH] efi_loader: Set variable attributes when EFI_BUFFER_TOO_SMALL is returned
by Ilias Apalodimas 16 Mar '22

16 Mar '22

Starting UEFI Spec 2.8 we must fill in the variable attributes when GetVariable() returns EFI_BUFFER_TOO_SMALL and Attributes is non-NULL. This code was written with 2.7 in mind so let's move the code around a bit and fill in the attributes EFI_BUFFER_TOO_SMALL is returned Signed-off-by: Ilias Apalodimas <ilias.apalodimas(a)linaro.org> --- lib/efi_loader/efi_variable_tee.c | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/lib/efi_loader/efi_variable_tee.c b/lib/efi_loader/efi_variable_tee.c index 58931c4efd74..33c7dfc53d14 100644 --- a/lib/efi_loader/efi_variable_tee.c +++ b/lib/efi_loader/efi_variable_tee.c @@ -408,22 +408,31 @@ efi_status_t efi_get_variable_int(const u16 *variable_name, /* Communicate */ ret = mm_communicate(comm_buf, payload_size); if (ret == EFI_SUCCESS || ret == EFI_BUFFER_TOO_SMALL) { + int tmp; /* Update with reported data size for trimmed case */ *data_size = var_acc->data_size; + /* + * UEFI > 2.7 needs the attributes set even if the buffer is + * smaller + */ + tmp = get_property_int(variable_name, name_size, vendor, + &var_property); + if (tmp != EFI_SUCCESS) { + ret = tmp; + goto out; + } + + if (attributes) { + *attributes = var_acc->attr; + if (var_property.property & + VAR_CHECK_VARIABLE_PROPERTY_READ_ONLY) + *attributes |= EFI_VARIABLE_READ_ONLY; + } } - if (ret != EFI_SUCCESS) - goto out; - ret = get_property_int(variable_name, name_size, vendor, &var_property); if (ret != EFI_SUCCESS) goto out; - if (attributes) { - *attributes = var_acc->attr; - if (var_property.property & VAR_CHECK_VARIABLE_PROPERTY_READ_ONLY) - *attributes |= EFI_VARIABLE_READ_ONLY; - } - if (data) memcpy(data, (u8 *)var_acc->name + var_acc->name_size, var_acc->data_size); -- 2.32.0

2 2

u-boot v2022.01 and Arria-10 socdk not booting
by Marcel Gielen [Celestia-STS] 16 Mar '22

16 Mar '22

I am working on an Enclustra mercury board and had some issues with booting, which stopped after (successful) FPGA configuration. (Console: FPGA: Enter user mode is the last line printed) Since we also have an Arria10 socdk available, I decided to try that one. For the sockdk I have a working sdcard, which also includes a FitImage containing a peripheral and core rbf. I tried the card (boots) replaced the bootloader with a vanilla built socfpga_arria10_defconfig and booting seems to stop at a similar point. Last console message: "early release succeeded" and then it stops. Am I overlooking something, or are there issues with mainline u-boot and arria10 ? Any suggestions where to look ?

2 1

[PATCH] CI, Docker: Update to latest focal tag
by Tom Rini 16 Mar '22

16 Mar '22

Signed-off-by: Tom Rini <trini(a)konsulko.com> --- .azure-pipelines.yml | 2 +- .gitlab-ci.yml | 2 +- tools/docker/Dockerfile | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml index 8352b10348de..cf49161c6f3a 100644 --- a/.azure-pipelines.yml +++ b/.azure-pipelines.yml @@ -2,7 +2,7 @@ variables: windows_vm: windows-2019 ubuntu_vm: ubuntu-18.04 macos_vm: macOS-10.15 - ci_runner_image: trini/u-boot-gitlab-ci-runner:focal-20220113-03Feb2022 + ci_runner_image: trini/u-boot-gitlab-ci-runner:focal-20220302-15Mar2022 # Add '-u 0' options for Azure pipelines, otherwise we get "permission # denied" error when it tries to "useradd -m -u 1001 vsts_azpcontainer", # since our $(ci_runner_image) user is not root. diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 1f4be626adab..31f50968a33e 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2,7 +2,7 @@ # Grab our configured image. The source for this is found at: # https://source.denx.de/u-boot/gitlab-ci-runner -image: trini/u-boot-gitlab-ci-runner:focal-20220113-03Feb2022 +image: trini/u-boot-gitlab-ci-runner:focal-20220302-15Mar2022 # We run some tests in different order, to catch some failures quicker. stages: diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile index 7a3f5cbade4e..f1d597abd8a4 100644 --- a/tools/docker/Dockerfile +++ b/tools/docker/Dockerfile @@ -2,7 +2,7 @@ # This Dockerfile is used to build an image containing basic stuff to be used # to build U-Boot and run our test suites. -FROM ubuntu:focal-20220113 +FROM ubuntu:focal-20220302 MAINTAINER Tom Rini <trini(a)konsulko.com> LABEL Description=" This image is for building U-Boot inside a container" -- 2.25.1

1 1

[PATCH] doc: uefi: Fix reference to CONFIG_EFI_SECURE_BOOT
by Jan Kiszka 16 Mar '22

16 Mar '22

From: Jan Kiszka <jan.kiszka(a)siemens.com> There is no CONFIG_UEFI_SECURE_BOOT, and there was never any. Signed-off-by: Jan Kiszka <jan.kiszka(a)siemens.com> --- Was briefly nervous finding only the documentation but no implementation yet. ;) doc/develop/uefi/uefi.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/develop/uefi/uefi.rst b/doc/develop/uefi/uefi.rst index b7bf1356276..fe337c88bda 100644 --- a/doc/develop/uefi/uefi.rst +++ b/doc/develop/uefi/uefi.rst @@ -105,7 +105,7 @@ The UEFI specification[1] defines a secure way of executing UEFI images by verifying a signature (or message digest) of image with certificates. This feature on U-Boot is enabled with:: - CONFIG_UEFI_SECURE_BOOT=y + CONFIG_EFI_SECURE_BOOT=y To make the boot sequence safe, you need to establish a chain of trust; In UEFI secure boot the chain trust is defined by the following UEFI variables -- 2.34.1

2 1

[PATCH v5 0/3] rockchip: sdhci: Add HS400 Enhanced Strobe support
by Alper Nebi Yasak 16 Mar '22

16 Mar '22

This series implements support for the HS400 Enhanced Strobe mode on the Rockchip SDHCI driver, for both RK3399 and RK3568. To test, I'm building for chromebook_kevin with the following configs enabled: +CONFIG_MMC_SPEED_MODE_SET=y [...] CONFIG_MMC_PWRSEQ=y +CONFIG_MMC_IO_VOLTAGE=y +CONFIG_MMC_UHS_SUPPORT=y +CONFIG_MMC_HS400_ES_SUPPORT=y +CONFIG_MMC_HS400_SUPPORT=y CONFIG_MMC_DW=y CONFIG_MMC_DW_ROCKCHIP=y CONFIG_MMC_SDHCI=y +CONFIG_MMC_SDHCI_SDMA=y CONFIG_MMC_SDHCI_ROCKCHIP=y and running roughly: $ mmc rescan [0|1|3|10|11|12] $ mmc info $ mmc part $ load mmc 0:1 0xd0000000 256MiB.bin $ load mmc 0:1 0xd0000000 16MiB.bin $ load mmc 0:1 0xd0000000 8MiB.bin Here's the differences in info and speeds I get with this: Mode | Bus Speed | Bus Width -----------------------+--------------+-------------- MMC Legacy | 25000000 | 8-bit MMC High Speed (26MHz) | 26000000 | 8-bit MMC High Speed (52MHz) | 52000000 | 8-bit HS200 (200MHz) | 200000000 | 8-bit HS400 (200MHz) | 200000000 | 8-bit DDR HS400ES (200MHz) | 200000000 | 8-bit DDR Mode | 256 MiB Load | 16 MiB Load | 8 MiB Load -----------------------+--------------+--------------+-------------- MMC Legacy | ~22.1 MiB/s | ~21.9 MiB/s | ~21.6 MiB/s MMC High Speed (26MHz) | ~22.1 MiB/s | ~21.9 MiB/s | ~21.6 MiB/s MMC High Speed (52MHz) | ~43.7 MiB/s | ~42.8 MiB/s | ~41.7 MiB/s HS200 (200MHz) | ~161.2 MiB/s | ~149.5 MiB/s | ~137.9 MiB/s HS400 (200MHz) | ~254.5 MiB/s | ~235.3 MiB/s | ~216.2 MiB/s HS400ES (200MHz) | ~254.7 MiB/s | ~238.8 MiB/s | ~216.2 MiB/s Hope I haven't missed anything. Enabling the configs above for each board is left to board maintainers as I can't test on those boards. Changes in v5: - Incorporate RK3568 HS400ES fixes from Yifeng Zhao: - Use DWCMSHC_CTRL_HS400 = 0x7, instead of SDHCI_CTRL_HS400 = 0x5 - Configure DWCMSHC_CARD_IS_EMMC in rk3568_sdhci_set_ios_post() - Configure DLL_STRBIN and DLL_TXCLK for HS400. - Drop re-init fix already merged to master v4: https://patchwork.ozlabs.org/project/uboot/list/?series=283482&state=* Changes in v4: - Add comment for SDHCI set_enhanced_strobe() operation - Add comment for Rockchip SDHCI set_enhanced_strobe() driver data op v3: https://patchwork.ozlabs.org/project/uboot/list/?series=281327&state=* Changes in v3: - Set DWCMSHC_CARD_IS_EMMC bit in rk3568_emmc_phy_init() v2: https://patchwork.ozlabs.org/project/uboot/list/?series=280494&state=* Changes in v2: - Unset ES bit in rk3399 set_control_reg() to fix a reinit issue - Don't use unnecessary & for function pointer in ops struct - Rename rk3399_set_enhanced_strobe -> rk3399_sdhci_set_enhanced_strobe - Rename rk3568_set_enhanced_strobe -> rk3568_sdhci_set_enhanced_strobe - Let set_enhanced_strobe() unset the ES bit if mode is not HS400_ES - Rewrote cover letter v1: https://patchwork.ozlabs.org/project/uboot/list/?series=269768&state=* Alper Nebi Yasak (3): mmc: sdhci: Add HS400 Enhanced Strobe support rockchip: sdhci: Add HS400 Enhanced Strobe support for RK3399 rockchip: sdhci: Add HS400 Enhanced Strobe support for RK3568 drivers/mmc/rockchip_sdhci.c | 117 +++++++++++++++++++++++++++++++++-- drivers/mmc/sdhci.c | 18 ++++++ include/sdhci.h | 12 ++++ 3 files changed, 141 insertions(+), 6 deletions(-) -- 2.35.1

4 8

[PATCH u-boot-marvell] arm: mvebu: dts: turris_mox: fix non-working network / MDIO
by Marek Behún 16 Mar '22

16 Mar '22

From: Marek Behún <marek.behun(a)nic.cz> Commit 0934dddc6436 ("arm: a37xx: Update DTS files to version from upstream Linux kernel") ported Linux's device-tree files for Armada 3720 SOCs. This broke network on Turris MOX, because the SOC's MDIO bus in U-Boot currently isn't probed via DM as it's own device, but is registered as part of mvneta's driver, which means that pinctrl definitions are not parsed for the MDIO bus node. Also mvneta driver does not consider "phy-handle" property, only "phy". For now, fix this by adding armada-3720-turris-mox-u-boot.dtsi file returning the MDIO to how it was defined previously. A better solution (using proper mvmdio DM driver) is being work on, but will need testing on various boards, and we need the bug fixed now for the upcoming release. Fixes: 0934dddc6436 ("arm: a37xx: Update DTS files to version from upstream Linux kernel") Signed-off-by: Marek Behún <marek.behun(a)nic.cz> --- Dear Stefan, this fix is needed for the upcoming release, is it still possible? Thanks. Marek --- .../dts/armada-3720-turris-mox-u-boot.dtsi | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 arch/arm/dts/armada-3720-turris-mox-u-boot.dtsi diff --git a/arch/arm/dts/armada-3720-turris-mox-u-boot.dtsi b/arch/arm/dts/armada-3720-turris-mox-u-boot.dtsi new file mode 100644 index 0000000000..2e05b973d2 --- /dev/null +++ b/arch/arm/dts/armada-3720-turris-mox-u-boot.dtsi @@ -0,0 +1,23 @@ +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) +/* + * 2022 by Marek Behún <kabel(a)kernel.org> + */ + +/ { + mdio { + #address-cells = <1>; + #size-cells = <0>; + + old_binding_phy1: ethernet-phy@1 { + reg = <1>; + }; + }; +}; + +&eth0 { + pinctrl-0 = <&rgmii_pins>, <&smi_pins>; + /delete-property/ phy-handle; + phy = <&old_binding_phy1>; +}; + +/delete-node/ &mdio; -- 2.34.1

3 3

booting of renesas rcar v3u
by Tuschik Thilo 16 Mar '22

16 Mar '22

Good morning, I am doing my master thesis /w the rcar v3u of renesas and I am facing the issue that the booting of the linux does stop at one point. It seems to be a problem with *Starting Rebuild Dynamic Linker Cache...* and *Starting Network Time Synchronization...*. It gives me the output, that Network Time Synchronization is stopped, because it is not able to be started correctly (even NTP messages are not being sent). It also gives a log like: A start job is running forâ€¦amic Linker Cache Is this still part of the u-boot code? Do you have any clue how to resolve this? Or where I could look for a resolution at least? Best regards Thilo Tuschik

1 0

AP152 & TP-Link Archer C7
by Brice GIBOUDEAU 16 Mar '22

16 Mar '22

?Hello, As I need to modify the boot environment I need to upgrade the fairly old Uboot-1.1.4 that you find on those quite popular device TP-Link Archer C7 (version 5 in my case). After investigations I found that you have a support for the AP152 that is the base of that router. I just changed few things to enable the proper boot address and Ethernet support. U-Boot work well but twhen OpenWRT boot it crash with random characters on the console during the PIEe initialization. Did I missed something ? (a variabe to set somewhere ?) I added debug info below. Regards, MiNuS_89 ?-------- Below the last line of the boot log from the console that show the issue. [ 1.770010] 8021q: 802.1Q VLAN Support v1.8 [ 1.775142] PCI host bridge /ahb/pcie-controller@18250000 ranges: [ 1.781508] MEM 0x0000000012000000..0x0000000013ffffff [ 1.786923] IO 0x0000000000000000..0x0000000000000000 [[ 1.998826] rr724x-pci11825000..pcie-cnntrolee:: PCIe iink is oonn 244244 P htt iiggeoo ss 0::0 [[ .86557]ci_s 00:0: N bsnesurc fun fo rt us wl uee[b 00ff [ 2.884066pccbus 0000::rt s ssor [[mm 12000000x11fffff [[ .8874] ctoys uabl toopen tc evic (rt0) 28758] pi_s 00:0 bsn_re [bs 0-f] d s pdtedto00 --------- My U-Boot version: U-Boot 2022.04-rc4 (Mar 15 2022 - 16:56:25 +0100) --------- I cross compiled it with the OpenWRT SDK: openwrt-sdk-21.02.2-ath79-generic_gcc-8.4.0_musl.Linux-x86_64 -------- I'm booting OpenWRT 21.02.2 and it boot correctly with the original U-Boot that I recovered a couple of time to investigate.

1 0