December 2021 - U-Boot

kwboot: Testing latest kwboot with Kirkwood SoC boards
by Tony Dinh 14 Dec '21

14 Dec '21

Hi Marek and Pali, First off all, thanks for your hughe work on this. I have a few Armada 38x boards that I had quite a hard time running kwboot in the past. Hopefully, I will have more luck with the new kwboot. Here is a problem I've found running kwboot on the Zyxel NSA310S NAS (Kirkwood 6702). The target is a Pogoplug V4 (Kirkwood 6192 SoC). Same behavior was observed running kwboot on this Pogoplug V4 to boot the NSA310S target. - kwboot build version ./kwboot-2021/kwboot kwboot version 2022.01-rc1-00034-gbc18582a14 - kwboot session log ./kwboot-2021/kwboot -t -p -B 115200 /dev/ttyUSB0 -b uboot.2021.07-tld-1.pogo_v4.mtd0.kwb Patching image boot signature to UART Aligning image header to Xmodem block size Sending boot message. Please reboot the target...\ Waiting 2s and flushing tty Sending boot image header (480 bytes)... 26 % [.... ] Done U-Boot 2021.04-tld-1 (Jun 10 2021 - 20:46:14 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB NAND: 128 MiB MMC: Loading Environment from NAND... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: eth0: ethernet-controller@72000 88E1116 Initialized on ethernet-controller@72000 Hit any key to stop autoboot: 9 8 7 As you can see above, it looks like the u-boot header transfer was completed but the u-boot image transfer did not start. Seems like BootROM did not recognize the header is UART. The Pogoplug V4 continued to boot with the image on NAND (U-Boot 2021.04-tld-1). So kwboot_xm_finish() was never executed. At this point we lost the terminal, and could not interrupt the countdown. The system continued booting and at one point, serial console output stopped with an error message that indicated kwboot thinks it is still in xmodem mode (but the BootROM actually started the NAND image). xmodem: Connection timed out Please let me know if there is any idea that you want me to try. Thanks, Tony

4 42

[PATCH 0/2] Add support for pine H64 model B board
by Daniel Wagenknecht 14 Dec '21

14 Dec '21

The following patches add support for the pine H64 model B board. The hardware differences to the pine H64 model A are minimal and not relevant for u-boot. The differences in the device-tree are relevant in linux though and the u-boot preset for the 'fdtfile' variable is infered from CONFIG_DEFAULT_DEVICE_TREE, thus using the model A's u-boot on a model B board works, but selects the wrong device tree when booting linux. An alternative approach would be to implement logic like used by e.g. the rockchip based boards to use the separate CONFIG_DEFAULT_FDT_FILE option to preset the 'fdtfile' variable and thus select the device-tree to use when booting linux. I prefer the 'copy dts file from linux kernel src' approach as implemented in these patches. If necessary I'd also be willing to be the maintainer for this board. But since I'm (not yet) paying attention to u-boot development progress I'd prefer if this would be maintained together with the pine H64 model A board. CC Icenowy Zheng as the pine H64 model A maintianer. Daniel Wagenknecht (2): sunxi: dts: add device-tree for pine H64 model B sunxi: configs: add defconfig for pine H64 model B arch/arm/dts/Makefile | 1 + arch/arm/dts/sun50i-h6-pine-h64-model-b.dts | 51 +++++++++++++++++++++ configs/pine_h64-model-b_defconfig | 21 +++++++++ 3 files changed, 73 insertions(+) create mode 100644 arch/arm/dts/sun50i-h6-pine-h64-model-b.dts create mode 100644 configs/pine_h64-model-b_defconfig -- 2.31.1

1 2

[PATCH 0/1] fix SPI pinmuxing for Allwinner H6 SoCs
by Daniel Wagenknecht 14 Dec '21

14 Dec '21

The following patch fixes the SPI not working with H6 SoCs. I encountered this on a pine H64 model B board when trying to configure u-boot to work with the on-board SPI flash. Register inspection showed that the pins were configured for the wrong function '0b011' which is the SD/eMMC interface instead of '0b100' which is needed for SPI. See Allwinner H6 datasheet section '3.21.5.1 PC Configuration Register 0'. I also saw that a new config symbol CONFIG_SUN50I_GEN_H6 was introduced and the SPI driver could probably be converted to that one to also work for H616 SoCs. Since I don't have any Allwinner H616 based board available for testing I didn't approach this. The SPL SPI driver is not effected by this, since the correct conditional logic was already implemented there. Daniel Wagenknecht (1): sunxi: SPI: fix pinmuxing for Allwinner H6 SoCs drivers/spi/spi-sunxi.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- 2.31.1

1 1

[RFC PATCH v4 0/6] fpga: zynqmp: Adding support of loading authenticated images
by Oleksandr Suvorov 14 Dec '21

14 Dec '21

Note: this version of the patchset changes the interface to the load() callback of xilinx_fpga_op. This patchset introduces support for the authenticated FPGA images on ZynqMP boards, besides that introducing common way to pass the compatible property to any fpga driver. It bases on the initial work by Jorge Ramirez-Ortiz <jorge(a)foundries.io> https://patchwork.ozlabs.org/project/uboot/patch/20211015091506.2602-1-jorg… https://patchwork.ozlabs.org/project/uboot/patch/20211005111324.19749-3-jor… Changes in v4: - change interface to xilinx_desc->operations->load() callback. - fix a bug from previous version of the patchset in dereferencing of a parent fpga_desc structure. Changes in v3: - remove the patch which introduced CMD_SPL_FPGA_LOAD_SECURE. - fix mixing definitions/declarations. - replace strcmp() calls with more secure strncmp(). - document the "u-boot,zynqmp-fpga-ddrauth" compatible string. - fix code style by check-patch recommendations. Changes in v2: - add function fit_fpga_load() to simplify calls of fpga_load() from contexts without a compatible attribute. - move all ZynqMP-specific logic to drivers/fpga/zynqmppl.c - prepare for passing a "compatible" FDT property to any fpga driver. Oleksandr Suvorov (6): fpga: add option for loading FPGA secure bitstreams fpga: add fit_fpga_load function fpga: xilinx: pass an address of xilinx_desc in fpga_desc fpga: xilinx: add missed identifier names fpga: xilinx: pass xilinx_desc pointer address into load() ops fpga: zynqmp: support loading authenticated images cmd/Kconfig | 3 +- common/Kconfig.boot | 4 +-- common/spl/spl_fit.c | 6 ++-- doc/uImage.FIT/source_file_format.txt | 5 +++- drivers/fpga/Kconfig | 14 +++++++++ drivers/fpga/fpga.c | 41 ++++++++++++++++++++------- drivers/fpga/spartan2.c | 3 +- drivers/fpga/spartan3.c | 3 +- drivers/fpga/versalpl.c | 2 +- drivers/fpga/virtex2.c | 3 +- drivers/fpga/xilinx.c | 8 ++++-- drivers/fpga/zynqmppl.c | 30 +++++++++++++++++--- drivers/fpga/zynqpl.c | 3 +- include/fpga.h | 4 +++ include/xilinx.h | 12 ++++---- 15 files changed, 106 insertions(+), 35 deletions(-) -- 2.31.1

3 9

[PATCH] net: zynq: Add support for PHY configuration in SGMII mode
by Michal Simek 14 Dec '21

14 Dec '21

SGMII configuration depends on proper GT setting that's why when node has phys property call PSGTR driver to configure it properly. Signed-off-by: Michal Simek <michal.simek(a)xilinx.com> --- drivers/net/zynq_gem.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/drivers/net/zynq_gem.c b/drivers/net/zynq_gem.c index 5cbe8d28304b..fece077066df 100644 --- a/drivers/net/zynq_gem.c +++ b/drivers/net/zynq_gem.c @@ -12,6 +12,7 @@ #include <common.h> #include <cpu_func.h> #include <dm.h> +#include <generic-phy.h> #include <log.h> #include <net.h> #include <netdev.h> @@ -716,6 +717,21 @@ static int zynq_gem_probe(struct udevice *dev) struct zynq_gem_priv *priv = dev_get_priv(dev); int ret; + if (priv->interface == PHY_INTERFACE_MODE_SGMII) { + struct phy phy; + + ret = generic_phy_get_by_index(dev, 0, &phy); + if (!ret) { + ret = generic_phy_init(&phy); + if (ret) + return ret; + + ret = generic_phy_power_on(&phy); + if (ret) + return ret; + } + } + ret = zynq_gem_reset_init(dev); if (ret) return ret; -- 2.33.1

4 4

[PULL] Pull request for u-boot master / v2022.01 = u-boot-stm32-20211213
by Patrice CHOTARD 13 Dec '21

13 Dec '21

Hi Tom Please pull the STM32 related patches for u-boot/master, v2022.01 = u-boot-stm32-20211213 CI status: https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/10215 Thanks Patrice The following changes since commit ade37460a944aed36ae6ee634c4d4a9a22690461: Prepare v2022.01-rc3 (2021-11-29 11:16:03 -0500) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-stm.git tags/u-boot-stm32-20211213 for you to fetch changes up to 5c592b636a4006a50228d54eda3fe291eaa1abb8: ARM: stm32: Enable KSZ90x1 PHY driver on DHCOR (2021-12-13 14:34:22 +0100) ---------------------------------------------------------------- - enable KSZ90x1 PHY driver on DHCOR - DHSOM boards: - increase USB power-good delay - add update_sf script to install U-Boot into SF - increase PHY auto-negotiation timeout to 20 seconds - fix SoM and board coding strap GPIO handling ---------------------------------------------------------------- Marek Vasut (6): ARM: stm32: Increase USB power-good delay on DHSOM ARM: stm32: Add update_sf script to install U-Boot into SF on DHSOM ARM: stm32: Increase PHY auto-negotiation timeout to 20s on DHSOM ARM: stm32: Fix SoM and board coding strap GPIO handling on DHSOM ARM: dts: stm32: Add custom PHY reset bindings on AV96 ARM: stm32: Enable KSZ90x1 PHY driver on DHCOR arch/arm/dts/stm32mp15xx-dhcor-avenger96-u-boot.dtsi | 11 +++++++++++ board/dhelectronics/dh_stm32mp1/board.c | 14 ++++++++++---- configs/stm32mp15_dhcor_basic_defconfig | 2 ++ include/configs/stm32mp15_common.h | 7 ++++++- include/configs/stm32mp15_dh_dhsom.h | 16 ++++++++++++++++ 5 files changed, 45 insertions(+), 5 deletions(-)

2 1

[PULL] u-boot-sh/master
by Marek Vasut 13 Dec '21

13 Dec '21

This is long overdue PR for current release with a few clean ups for the RZG2 The following changes since commit a1c01b17c59ec03c678073e145fbd094c7606dc8: Merge tag 'efi-2022-01-rc4-2' of https://source.denx.de/u-boot/custodians/u-boot-efi (2021-12-10 07:58:43 -0500) are available in the Git repository at: git://source.denx.de/u-boot-sh.git master for you to fetch changes up to d5f1beb058a48fb057d3a62dc751a19c1a3db279: configs: beacon-rzg2m: Config to address new aliases (2021-12-13 00:37:28 +0100) ---------------------------------------------------------------- Adam Ford (5): net: ravb: Support multiple clocks arm: dts: beacon-rzg2: Resync device trees with Linux 5.16-rc3 arm: dts: Create common rz-g2-beacon-u-boot file ARM: rmobile: Fix rzg2_beacon_defconfig to address new aliases configs: beacon-rzg2m: Config to address new aliases arch/arm/dts/beacon-renesom-baseboard.dtsi | 16 ++++++++++++---- arch/arm/dts/beacon-renesom-som.dtsi | 45 +++++++++++---------------------------------- arch/arm/dts/r8a774a1-beacon-rzg2m-kit-u-boot.dtsi | 32 ++------------------------------ arch/arm/dts/r8a774a1-beacon-rzg2m-kit.dts | 3 +++ arch/arm/dts/r8a774b1-beacon-rzg2n-kit-u-boot.dtsi | 32 ++------------------------------ arch/arm/dts/r8a774b1-beacon-rzg2n-kit.dts | 3 +++ arch/arm/dts/r8a774e1-beacon-rzg2h-kit-u-boot.dtsi | 42 ++---------------------------------------- arch/arm/dts/r8a774e1-beacon-rzg2h-kit.dts | 3 +++ arch/arm/dts/rz-g2-beacon-u-boot.dtsi | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ board/beacon/beacon-rzg2m/MAINTAINERS | 10 ++++++++++ configs/rzg2_beacon_defconfig | 1 - drivers/net/ravb.c | 10 +++++----- include/configs/beacon-rzg2m.h | 2 +- 13 files changed, 129 insertions(+), 145 deletions(-) create mode 100644 arch/arm/dts/rz-g2-beacon-u-boot.dtsi

2 1

[PULL] Pull request for u-boot next / v2022.04 = u-boot-stm32-20211130
by Patrice CHOTARD 13 Dec '21

13 Dec '21

Hi Tom Please pull the STM32 related patches for u-boot/next, v2022.04 : u-boot-stm32-20211130 CI status: https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/10049 Thanks Patrice The following changes since commit 2402c93130c09b881f9cc1369459fb49d9fa0f74: Merge tag 'v2022.01-rc3' into next (2021-11-29 12:00:57 -0500) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-stm.git tags/u-boot-stm32-20211130 for you to fetch changes up to c7c06fa776b3a553df922259908fad12cfa0e1e8: board: stm32mp1: add support of nor1 device in dfu command (2021-11-30 16:43:28 +0100) ---------------------------------------------------------------- - add nor1 device support for DFU command - remove CONFIG_STM32_IPCC from stm32mp15 defconfigs - enable simple framebuffer node for splashscreen for stm32mp1 - use lower-case hex for address for stm32 MCU and MPU's device tree - define LOG_CATEGORY for stmfx pinctrl driver - add support for probing bus voltage level translator - add custom PHY reset bindings on AV96 - enable KSZ90x1 PHY driver on DHCOR - stm32mp1 DDR update: - add DDR read data eye training - remove DDR calibration result - remove DDR tuning support - compute DDR size from DDRCTL registers - DHSOM boards: - increase USB power-good delay - add update_sf script to install U-Boot into SF - increase PHY auto-negotiation timeout to 20 seconds - fix SoM and board coding strap GPIO handling - auto-detect uSD level translator ---------------------------------------------------------------- Marek Vasut (8): ARM: stm32: Increase USB power-good delay on DHSOM ARM: stm32: Add update_sf script to install U-Boot into SF on DHSOM ARM: stm32: Increase PHY auto-negotiation timeout to 20s on DHSOM ARM: stm32: Fix SoM and board coding strap GPIO handling on DHSOM ARM: dts: stm32: Add custom PHY reset bindings on AV96 ARM: stm32: Enable KSZ90x1 PHY driver on DHCOR mmc: stm32_sdmmc2: Add support for probing bus voltage level translator ARM: dts: stm32: Auto-detect DHSOM with uSD level translator Patrice Chotard (8): ARM: dts: stm32: Use lower-case hex for address for stm32mp15-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32f769-disco-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32746-disco-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32f7-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32f469-disco-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32f429-disco-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32f746g-eval-u-boot.dtsi ARM: dts: stm32: Use lower-case hex for address for stm32429i-eval-u-boot.dtsi Patrick Delaunay (15): pinctrl: stmfx: define LOG_CATEGORY stm32mp1: ram: add read valid training support stm32mp1: ram: remove the support of calibration result stm32mp1: ram: remove tuning support Convert CONFIG_LCD_DT_SIMPLEFB to Kconfig common: rename lcd_simplefb.c file to fdt_simplefb.c common: rename functions lcd_dt_simplefb to fdt_simplefb video: Add video_is_active function common: add fdt_simplefb_enable_and_mem_rsv function video: stm32: stm32_ltdc: align framebuffer on 2MB board: stm32mp1: enable simple framebuffer node for splashscreen configs: stm32mp15: deactivate the CONFIG_STM32_IPCC ram: stm32mp1: compute DDR size from DDRCTL registers ram: stm32mp1: remove __maybe_unused on stm32mp1_ddr_setup board: stm32mp1: add support of nor1 device in dfu command arch/arm/dts/stm32429i-eval-u-boot.dtsi | 2 +- arch/arm/dts/stm32746g-eval-u-boot.dtsi | 2 +- arch/arm/dts/stm32f429-disco-u-boot.dtsi | 2 +- arch/arm/dts/stm32f469-disco-u-boot.dtsi | 6 +- arch/arm/dts/stm32f7-u-boot.dtsi | 4 +- arch/arm/dts/stm32f746-disco-u-boot.dtsi | 2 +- arch/arm/dts/stm32f769-disco-u-boot.dtsi | 6 +- arch/arm/dts/stm32mp15-ddr.dtsi | 30 - arch/arm/dts/stm32mp15-ddr3-1x4Gb-1066-binG.dtsi | 12 - arch/arm/dts/stm32mp15-ddr3-2x4Gb-1066-binG.dtsi | 12 - .../dts/stm32mp15-ddr3-dhsom-2x1Gb-1066-binG.dtsi | 12 - .../dts/stm32mp15-ddr3-dhsom-2x2Gb-1066-binG.dtsi | 12 - .../dts/stm32mp15-ddr3-dhsom-2x4Gb-1066-binG.dtsi | 12 - .../dts/stm32mp15-ddr3-icore-1x4Gb-1066-binG.dtsi | 12 - arch/arm/dts/stm32mp15-u-boot.dtsi | 8 +- arch/arm/dts/stm32mp15xx-dhcom-u-boot.dtsi | 4 + .../dts/stm32mp15xx-dhcor-avenger96-u-boot.dtsi | 15 + board/dhelectronics/dh_stm32mp1/board.c | 14 +- board/raspberrypi/rpi/rpi.c | 2 +- board/st/common/stm32mp_dfu.c | 4 + board/st/stm32mp1/stm32mp1.c | 4 + common/Kconfig | 9 + common/Makefile | 2 +- common/{lcd_simplefb.c => fdt_simplefb.c} | 37 +- configs/rpi_0_w_defconfig | 1 + configs/rpi_2_defconfig | 1 + configs/rpi_3_32b_defconfig | 1 + configs/rpi_3_b_plus_defconfig | 1 + configs/rpi_3_defconfig | 1 + configs/rpi_4_32b_defconfig | 1 + configs/rpi_4_defconfig | 1 + configs/rpi_arm64_defconfig | 1 + configs/rpi_defconfig | 1 + configs/stm32mp15-icore-stm32mp1-ctouch2_defconfig | 2 - .../stm32mp15-icore-stm32mp1-edimm2.2_defconfig | 2 - ...2mp15-microgea-stm32mp1-microdev2-of7_defconfig | 2 - ...stm32mp15-microgea-stm32mp1-microdev2_defconfig | 2 - configs/stm32mp15_basic_defconfig | 3 +- configs/stm32mp15_defconfig | 3 +- configs/stm32mp15_dhcom_basic_defconfig | 2 - configs/stm32mp15_dhcor_basic_defconfig | 4 +- configs/stm32mp15_trusted_defconfig | 3 +- doc/board/st/stm32mp1.rst | 18 +- .../memory-controllers/st,stm32mp1-ddr.txt | 32 - drivers/mmc/stm32_sdmmc2.c | 63 +- drivers/pinctrl/pinctrl-stmfx.c | 4 + drivers/ram/stm32mp1/Makefile | 1 - drivers/ram/stm32mp1/stm32mp1_ddr.c | 69 +- drivers/ram/stm32mp1/stm32mp1_ddr.h | 22 - drivers/ram/stm32mp1/stm32mp1_ddr_regs.h | 66 +- drivers/ram/stm32mp1/stm32mp1_interactive.c | 37 +- drivers/ram/stm32mp1/stm32mp1_ram.c | 217 ++- drivers/ram/stm32mp1/stm32mp1_tests.h | 3 - drivers/ram/stm32mp1/stm32mp1_tuning.c | 1540 -------------------- drivers/video/stm32/stm32_ltdc.c | 5 +- drivers/video/video-uclass.c | 14 + include/configs/rpi.h | 1 - include/configs/stm32mp15_common.h | 7 +- include/configs/stm32mp15_dh_dhsom.h | 16 + include/fdt_simplefb.h | 5 +- include/video.h | 7 + scripts/config_whitelist.txt | 1 - 62 files changed, 463 insertions(+), 1922 deletions(-) rename common/{lcd_simplefb.c => fdt_simplefb.c} (65%) delete mode 100644 drivers/ram/stm32mp1/stm32mp1_tuning.c

3 5

[PATCH v7 00/31] fdt: Make OF_BOARD a boolean option
by Simon Glass 13 Dec '21

13 Dec '21

With Ilias' efforts we have dropped OF_PRIOR_STAGE and OF_HOSTFILE so there are only three ways to obtain a devicetree: - OF_SEPARATE - the normal way, where the devicetree is built and appended to U-Boot - OF_EMBED - for development purposes, the devicetree is embedded in the ELF file (also used for EFI) - OF_BOARD - the board figures it out on its own The last one is currently set up so that no devicetree is needed at all in the U-Boot tree. Most boards do provide one, but some don't. Some don't even provide instructions on how to boot on the board. The problems with this approach are documented in another patch in this series: "doc: Add documentation about devicetree usage" In practice, OF_BOARD is not really distinct from OF_SEPARATE. Any board can obtain its devicetree at runtime, even it is has a devicetree built in U-Boot. This is because U-Boot may be a second-stage bootloader and its caller may have a better idea about the hardware available in the machine. This is the case with a few QEMU boards, for example. So it makes no sense to have OF_BOARD as a 'choice'. It should be an option, available with either OF_SEPARATE or OF_EMBED. This would allow rpi3, for example, to run with the devicetree provided by the prior bootloader. This series makes this change, adding various missing devicetree files (and placeholders) to make the build work. It also adds a run-time message showing where the devicetree came from, as well as warnings if the board's expected flow is not being used. This comes from the 'standard passage' series, which depends on this series. It also provides a few qemu clean-ups discovered along the way. The qemu-riscv64_spl problem is fixed. Please see [2] for discussion on the v6 series. I put Heinrich's Tested-by tag[3] for the series onto the three devicetree patches (ARM and RISC-V) that I think it most affects. It isn't possible to apply a tag to a whole series at present and in any case there are changes in v7. This series is available at u-boot-dm/ofb-working [1] https://patchwork.ozlabs.org/project/uboot/patch/20210919215111.3830278-3-s… [2] https://lore.kernel.org/u-boot/20211205133207.GW1220664@bill-the-cat/T/#mcd… [3] https://lore.kernel.org/u-boot/93913911-4d20-d28f-ee04-739985184c5e@canonic… Changes in v7: - Fix 'linst' typo - Switch to using an empty file for qemu virt - Switch to using an empty file for qemu virt - Switch to using an empty file for qemu virt - Reword commit message - Bring in files from Linux instead - Bring in files from Linux instead - Rewrite the commit message - Use 'empty' instead of 'fake' - Use 'empty' instead of 'fake' - Switch to using an empty file for qemu virt - Bring in files from Linux instead - Fix 'Is' typo in commit message - Drop FDTSRC_PASSAGE for now - Drop FDTSRC_PASSAGE for now - Add new patch to add a Kconfig for boards with a prior stage Changes in v6: - Fix description of OF_BOARD so it refers just to the current state - Explain that the 'two devicetrees' refers to two *control* devicetrees - Expand the commit message based on comments - Expand the commit message based on comments Changes in v5: - Bring into the OF_BOARD series - Rebase to master and drop mention of OF_PRIOR_STAGE, since removed - Refer to the 'control' DTB in the first paragraph - Use QEMU instead of qemu - Merge RISC-V and ARM patches since they are similar - Add new patches to clean up fdtdec_setup() and surrounds Changes in v3: - Clarify the 'bug' refered to at the top - Reword 'This means that there' paragraph to explain U-Boot-specific things - Move to doc/develop/devicetree now that OF_CONTROL is in the docs Changes in v2: - Fix typos per Sean (thank you!) and a few others - Add a 'Use of U-Boot /config node' section - Drop mention of dm-verity since that actually uses the kernel cmdline - Explain that OF_BOARD will still work after these changes (in 'Once this bug is fixed...' paragraph) - Expand a bit on the reason why the 'Current situation' is bad - Clarify in a second place that Linux and U-Boot use the same devicetree in 'To be clear, while U-Boot...' - Expand on why we should have rules for other projects in 'Devicetree in another project' - Add a comment as to why devicetree in U-Boot is not 'bad design' - Reword 'in-tree U-Boot devicetree' to 'devicetree source in U-Boot' - Rewrite 'Devicetree generated on-the-fly in another project' to cover points raised on v1 - Add 'Why does U-Boot have its nodes and properties?' - Add 'Why not have two devicetrees?' Simon Glass (31): doc: Add documentation about devicetree usage arm: qemu: Mention -nographic in the docs arm: riscv: qemu: Explain how to extract the generated dt arm: qemu: Add a devicetree file for qemu_arm arm: qemu: Add a devicetree file for qemu_arm64 virt riscv: qemu: Split devicetree files for qemu_riscv32/64 arm: rpi: Sync rpi dts files from Linux arm: vexpress: Add a devicetree files for juno arm: xenguest_arm64: Add a empty devicetree file arm: octeontx: Add an empty devicetree file arm: xilinx_versal_virt: Add a devicetree file arm: bcm7xxx: Add a devicetree file arm: qemu-ppce500: Add a devicetree file arm: highbank: Add devicetree files fdt: Make OF_BOARD a bool option Drop CONFIG_BINMAN_STANDALONE_FDT doc: Update info on devicetree update fdt: Move MULTI_DTB_FIT handling out of fdtdec_setup() fdt: Drop #ifdefs with MULTI_DTB_FIT fdt: Drop CONFIG_SPL_BUILD check in fdtdec_setup() fdt: Drop #ifdef around board_fdt_blob_setup() fdt: Use if() for fdtcontroladdr check fdt: Drop OF_CONTROL check in fdtdec_setup() fdt: Drop remaining preprocessor macros in fdtdec_setup() fdt: Don't call board_fdt_blob_setup() without OF_BOARD dm: core: Allow getting some basic stats fdt: Record where the devicetree came from fdt: Report the devicetree source fdt: Add a Kconfig for boards with a prior stage fdt: Avoid emitting an device tree when not needed fdt: Show build/runtime warnings based on devicetree source Makefile | 12 +- arch/arm/Kconfig | 8 + arch/arm/dts/Makefile | 20 +- arch/arm/dts/bcm2711-rpi-4-b.dts | 262 ++++ arch/arm/dts/bcm2711-rpi.dtsi | 74 ++ arch/arm/dts/bcm2711.dtsi | 1100 +++++++++++++++++ arch/arm/dts/bcm2835-common.dtsi | 207 ++++ arch/arm/dts/bcm2835-rpi-a-plus.dts | 18 +- arch/arm/dts/bcm2835-rpi-a.dts | 16 +- arch/arm/dts/bcm2835-rpi-b-plus.dts | 18 +- arch/arm/dts/bcm2835-rpi-b-rev2.dts | 16 +- arch/arm/dts/bcm2835-rpi-b.dts | 16 +- arch/arm/dts/bcm2835-rpi-cm1-io1.dts | 9 + arch/arm/dts/bcm2835-rpi-cm1.dtsi | 7 +- arch/arm/dts/bcm2835-rpi-common.dtsi | 12 + arch/arm/dts/bcm2835-rpi-zero-w.dts | 20 +- arch/arm/dts/bcm2835-rpi-zero.dts | 16 +- arch/arm/dts/bcm2835-rpi.dtsi | 35 +- arch/arm/dts/bcm2835.dtsi | 2 + arch/arm/dts/bcm2836-rpi-2-b.dts | 14 +- arch/arm/dts/bcm2836.dtsi | 2 + arch/arm/dts/bcm2837-rpi-3-a-plus.dts | 9 +- arch/arm/dts/bcm2837-rpi-3-b-plus.dts | 9 +- arch/arm/dts/bcm2837-rpi-3-b.dts | 5 +- arch/arm/dts/bcm2837-rpi-cm3-io3.dts | 9 + arch/arm/dts/bcm2837-rpi-cm3.dtsi | 9 + arch/arm/dts/bcm2837.dtsi | 2 + arch/arm/dts/bcm283x-rpi-usb-peripheral.dtsi | 7 + arch/arm/dts/bcm283x.dtsi | 224 +--- arch/arm/dts/bcm7xxx.dts | 15 + arch/arm/dts/ecx-common.dtsi | 231 ++++ arch/arm/dts/highbank.dts | 158 +++ arch/arm/dts/juno-base.dtsi | 831 +++++++++++++ arch/arm/dts/juno-clocks.dtsi | 46 + arch/arm/dts/juno-cs-r1r2.dtsi | 85 ++ arch/arm/dts/juno-motherboard.dtsi | 303 +++++ arch/arm/dts/juno-r2.dts | 322 +++++ arch/arm/dts/octeontx.dts | 14 + arch/arm/dts/qemu-arm.dts | 11 + arch/arm/dts/qemu-arm64.dts | 11 + arch/arm/dts/xenguest-arm64.dts | 15 + arch/arm/dts/xilinx-versal-virt.dts | 11 + arch/arm/mach-bcm283x/Kconfig | 1 + arch/powerpc/dts/Makefile | 1 + arch/powerpc/dts/qemu-ppce500.dts | 10 + arch/riscv/dts/Makefile | 2 +- .../dts/{qemu-virt.dts => qemu-virt32.dts} | 3 + arch/riscv/dts/qemu-virt64.dts | 11 + board/emulation/qemu-riscv/Kconfig | 1 + cmd/bdinfo.c | 2 + common/board_r.c | 24 + configs/bcm7260_defconfig | 1 + configs/bcm7445_defconfig | 1 + configs/highbank_defconfig | 2 +- configs/octeontx2_95xx_defconfig | 1 + configs/octeontx2_96xx_defconfig | 1 + configs/octeontx_81xx_defconfig | 1 + configs/octeontx_83xx_defconfig | 1 + configs/qemu-ppce500_defconfig | 2 + configs/qemu-riscv32_defconfig | 1 + configs/qemu-riscv32_smode_defconfig | 1 + configs/qemu-riscv32_spl_defconfig | 4 +- configs/qemu-riscv64_defconfig | 1 + configs/qemu-riscv64_smode_defconfig | 1 + configs/qemu-riscv64_spl_defconfig | 3 +- configs/qemu_arm64_defconfig | 1 + configs/qemu_arm_defconfig | 1 + configs/rpi_4_32b_defconfig | 1 + configs/rpi_4_defconfig | 1 + configs/rpi_arm64_defconfig | 1 + configs/vexpress_aemv8a_juno_defconfig | 1 + configs/xenguest_arm64_defconfig | 2 +- configs/xilinx_versal_virt_defconfig | 1 + doc/board/emulation/qemu-arm.rst | 10 +- doc/board/emulation/qemu-riscv.rst | 3 + doc/develop/devicetree/dt_qemu.rst | 48 + doc/develop/devicetree/dt_update.rst | 495 ++++++++ doc/develop/devicetree/index.rst | 2 + drivers/core/device.c | 11 + drivers/core/root.c | 7 + drivers/core/uclass.c | 13 + dts/Kconfig | 65 +- include/asm-generic/global_data.h | 12 + include/dm/device.h | 11 +- include/dm/root.h | 8 + include/dm/uclass-internal.h | 7 + include/dt-bindings/clock/bcm2835.h | 2 + include/fdtdec.h | 53 +- lib/fdtdec.c | 141 ++- test/dm/core.c | 41 + tools/binman/binman.rst | 20 - 91 files changed, 4879 insertions(+), 366 deletions(-) create mode 100644 arch/arm/dts/bcm2711-rpi-4-b.dts create mode 100644 arch/arm/dts/bcm2711-rpi.dtsi create mode 100644 arch/arm/dts/bcm2711.dtsi create mode 100644 arch/arm/dts/bcm2835-common.dtsi create mode 100644 arch/arm/dts/bcm2835-rpi-common.dtsi create mode 100644 arch/arm/dts/bcm283x-rpi-usb-peripheral.dtsi create mode 100644 arch/arm/dts/bcm7xxx.dts create mode 100644 arch/arm/dts/ecx-common.dtsi create mode 100644 arch/arm/dts/highbank.dts create mode 100644 arch/arm/dts/juno-base.dtsi create mode 100644 arch/arm/dts/juno-clocks.dtsi create mode 100644 arch/arm/dts/juno-cs-r1r2.dtsi create mode 100644 arch/arm/dts/juno-motherboard.dtsi create mode 100644 arch/arm/dts/juno-r2.dts create mode 100644 arch/arm/dts/octeontx.dts create mode 100644 arch/arm/dts/qemu-arm.dts create mode 100644 arch/arm/dts/qemu-arm64.dts create mode 100644 arch/arm/dts/xenguest-arm64.dts create mode 100644 arch/arm/dts/xilinx-versal-virt.dts create mode 100644 arch/powerpc/dts/qemu-ppce500.dts rename arch/riscv/dts/{qemu-virt.dts => qemu-virt32.dts} (94%) create mode 100644 arch/riscv/dts/qemu-virt64.dts create mode 100644 doc/develop/devicetree/dt_qemu.rst create mode 100644 doc/develop/devicetree/dt_update.rst -- 2.34.1.400.ga245620fadb-goog

8 59

[RESEND RFC PATCH 00/10] FWU: Add support for FWU Multi Bank Update feature
by Sughosh Ganu 13 Dec '21

13 Dec '21

(resending to including the first paragraph which got deleted for some reason). The patchset adds support for the FWU Multi Bank Update[1] feature. Certain aspects of the Dependable Boot[2] specification have also been implemented. The FWU multi bank update feature is used for supporting multiple sets(also called banks) of firmware image(s), allowing the platform to boot from a different bank, in case it fails to boot from the active bank. This functionality is supported by keeping the relevant information in a structure called metadata, which provides information on the images. Among other parameters, the metadata structure contains information on the currect active bank that is being used to boot image(s). Functionality is being added to work with the UEFI capsule driver in u-boot. The metadata is read to gather information on the update bank, which is the bank to which the firmware images would be flashed to. On a successful completion of the update of all components, the active bank field in the metadata is updated, to reflect the bank from which the platform will boot on the subsequent boots. Currently, the feature is being enabled on the STM32MP157C-DK2 board which boots a FIP image from a uSD card partitioned with the GPT partioning scheme. This also requires changes in the previous stage of bootloader, which parses the metadata and selects the bank to boot the image(s) from. Support is being added in tf-a(BL2 stage) for the STM32MP157C-DK2 board to boot the active bank images. These changes are under review currently[3]. Todo's ------ 1) Add a test(selftest) for the metadata access. 2) Add a tool for generation of the metadata. Not sure if this needs to be part of the u-boot repository though. 3) Add a tool for generation of the firmware accept/reject dummy capsule. Need to check if this can be added to the mkeficapsule tool in u-boot. [1] - https://developer.arm.com/documentation/den0118/a [2] - https://staging-git.codelinaro.org/linaro/firmware-dual-banked-updates/test [3] - https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/12566 Sughosh Ganu (10): GPT: Add function to get gpt header and partition entries stm32mp: dfu: Move the ram partitions to the end of the dfu_alt_info variable FWU: Add metadata structure and functions for accessing metadata FWU: Add metadata access functions for GPT partitioned block devices FWU: stm32mp1: Add helper functions for accessing metadata FWU: STM32MP1: Add support to read boot index from backup register EFI: FMP: Add provision to update image's ImageTypeId in image descriptor FWU: Add boot time checks as highlighted by the FWU specification FWU: Add support for FWU Multi Bank Update feature FWU: cmd: Add a command to read metadata arch/arm/mach-stm32mp/include/mach/stm32.h | 1 + board/st/common/stm32mp_dfu.c | 11 +- board/st/stm32mp1/stm32mp1.c | 70 ++ cmd/Kconfig | 6 + cmd/Makefile | 1 + cmd/fwu_metadata.c | 65 ++ common/board_r.c | 6 + disk/part_efi.c | 10 + include/fwu_metadata.h | 140 ++++ include/part.h | 14 + lib/Kconfig | 32 + lib/Makefile | 1 + lib/efi_loader/efi_capsule.c | 190 +++++- lib/efi_loader/efi_firmware.c | 76 ++- lib/fwu_updates/Makefile | 11 + lib/fwu_updates/fwu.c | 170 +++++ lib/fwu_updates/fwu_metadata.c | 275 ++++++++ lib/fwu_updates/fwu_metadata_gpt_blk.c | 716 +++++++++++++++++++++ 18 files changed, 1784 insertions(+), 11 deletions(-) create mode 100644 cmd/fwu_metadata.c create mode 100644 include/fwu_metadata.h create mode 100644 lib/fwu_updates/Makefile create mode 100644 lib/fwu_updates/fwu.c create mode 100644 lib/fwu_updates/fwu_metadata.c create mode 100644 lib/fwu_updates/fwu_metadata_gpt_blk.c -- 2.17.1

5 35