August 2021 - U-Boot

[PATCH v3] board: apalis-tk1: launch toradex easy installer in usb recovery
by Marcel Ziswiler 12 Aug '21

12 Aug '21

From: Marcel Ziswiler <marcel.ziswiler(a)toradex.com> The USB recovery mode is used by Toradex to load the Toradex Easy Installer image which supports further system images installation. Prepare for loading and launching the Toradex Easy Installer if the USB Recovery mode is activated. Signed-off-by: Marcel Ziswiler <marcel.ziswiler(a)toradex.com> Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov(a)toradex.com> --- Changes in v3: - Switch very long lines to multiline to make checkpatch happy as suggested by Stefano. board/toradex/apalis-tk1/apalis-tk1.c | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/board/toradex/apalis-tk1/apalis-tk1.c b/board/toradex/apalis-tk1/apalis-tk1.c index b97617cfca3..2769b546010 100644 --- a/board/toradex/apalis-tk1/apalis-tk1.c +++ b/board/toradex/apalis-tk1/apalis-tk1.c @@ -38,8 +38,24 @@ int arch_misc_init(void) { if (readl(NV_PA_BASE_SRAM + NVBOOTINFOTABLE_BOOTTYPE) == - NVBOOTTYPE_RECOVERY) - printf("USB recovery mode\n"); + NVBOOTTYPE_RECOVERY) { + printf("USB recovery mode, attempting to boot Toradex Easy " + "Installer\n"); + env_set("bootdelay", "-2"); + env_set("defargs", "pcie_aspm=off user_debug=30"); + env_set("fdt_high", ""); + env_set("initrd_high", ""); + + env_set("setup", "env set setupargs igb_mac=${ethaddr} " + "consoleblank=0 no_console_suspend=1 " + "console=${console},${baudrate}n8 ${memargs}"); + env_set("teziargs", "rootfstype=squashfs root=/dev/ram quiet " + "autoinstall"); + env_set("vidargs", "video=HDMI-A-1:640x480-16@60D"); + env_set("bootcmd", "run setup; env set bootargs ${defargs} " + "${setupargs} ${vidargs} ${teziargs}; bootm 0x80208000" + "#config(a)${soc}-${fdt_module}-${fdt_board}.dtb"); + } /* PCB Version Indication: V1.2 and later have GPIO_PV0 wired to GND */ gpio_request(TEGRA_GPIO(V, 0), "PCB Version Indication"); -- 2.26.2

4 4

RFC: Support for U-Boot phases in Kconfig
by Simon Glass 11 Aug '21

11 Aug '21

Hi, U-Boot can be configured to build the source multiple times to product multiple 'phases'. The main phase is the full U-Boot, but an 'SPL' (Secondary Program Loader) build can produce a cut-down image only suitable for loading U-Boot proper. SPL does not want to use the same Kconfig options, since that would produce the same binary. Instead we have two copies of some options, one with an SPL prefix, that can be configured independently. In the source code we can use a macro to see if code should be run: if (CONFIG_IS_ENABLED(SYS_STDIO_DEREGISTER)) { ... } This expands to check either checking SYS_STDIO_DEREGISTER or SPL_SYS_STDIO_DEREGISTER, depending on which phase is being built. U-Boot also has TPL (Tertiary Program Loader) which works a similar way. This is causing quite an expansion of the Kconfig source, with quite a bit of duplication. Each time a new feature needs to be supported in SPL, it involves a patch to add the same options again but for SPL. Here are some proposed changes to make it easier to deal with SPL/TPL: 1. Kconfig support At present we do things like this when we need to control an option separately in U-Boot proper and SPL: config SYS_STDIO_DEREGISTER bool "Allow deregistering stdio devices" depends on DM_DEVICE_REMOVE default y if USB_KEYBOARD help Generally there is no need to deregister stdio devices since they are never deactivated. But if a stdio device is used which can be removed (for example a USB keyboard) then this option can be enabled to ensure this is handled correctly. config SPL_SYS_STDIO_DEREGISTER bool "Allow deregistering stdio devices in SPL" depends on SPL_DM_DEVICE_REMOVE help Generally there is no need to deregister stdio devices since they are never deactivated. But if a stdio device is used which can be removed (for example a USB keyboard) then this option can be enabled to ensure this is handled correctly. This is very rarely needed in SPL. This is a pain. Apart from the duplication, sometimes the SPL version is in a different file or a different part of the file, making it hard to find related options or update them in sync. Instead, we can add a 'phase' command to the Kconfig language, so we can do: config SYS_STDIO_DEREGISTER bool "Allow deregistering stdio devices" phases depends on p.DM_DEVICE_REMOVE phase MAIN default y if USB_KEYBOARD help Generally there is no need to deregister stdio devices since they are never deactivated. But if a stdio device is used which can be removed (for example a USB keyboard) then this option can be enabled to ensure this is handled correctly. 'phases' means this Kconfig option exists in all phases. You can also say 'phases MAIN SPL' to select just MAIN (U-Boot) and SPL. 'p.DM_DEVICE_REMOVE' means to prefix the phase with each symbol, so for U-Boot (which uses SYS_STDIO_DEREGISTER) this means DM_DEVICE_REMOVE (p is empty) and for SPL (which uses SPL_SYS_STDIO_DEREGISTER) it means SPL_DM_DEVICE_REMOVE (p is SPL_). This is somewhat similar in style to the special-case 'depends on m' in Kconfig. To make this work, we tell Kconfig that SPL is a phase with 'def_phase': config SPL def_phase depends on SUPPORT_SPL prompt "Enable SPL" help If you want to build SPL as well as the normal image, say Y. It works just the same as a bool, but kconfig also uses it to automatically add new Kconfigs for each phase. In the above example it creates both SYS_STDIO_DEREGISTER and SPL_SYS_STDIO_DEREGISTER. The option name has the text '(SPL) ' shown before the SPL option. This can easily handle Kconfigs with similar dependencies and even different ones. If the Kconfig options are not actually very similar we can still create two separate copies instead, as now. This allows us to substantially reduce the size and duplication in the Kconfig defintions. It also reduces the pain of adding another phase to U-Boot. Note: This change needs to be done in Linux, which owns Kconfig upstream. 2.Rename SPL_TPL_ This Makefile variable is used to reduce the number of duplicate rules in makefiles: obj-$(CONFIG_$(SPL_TPL_)FIT_SIGNATURE) += fdt_region.o The SPL_TPL_ expands to empty for U-Boot and either SPL_ or TPL_ for the other phases. This is confusing though, since CONFIG_SPL_BUILD it set even for TPL builds, so for example. with: obj-$(CONFIG_$(SPL_)FIT_SIGNATURE) += fdt_region.o the file is built for both SPL and TPL. To help with this, We can rename SPL_TPL to PHASE_: obj-$(CONFIG_$(PHASE_)FIT_SIGNATURE) += fdt_region.o or perhaps P_ which is more readable: obj-$(CONFIG_$(P_)FIT_SIGNATURE) += fdt_region.o 3. Rename CONFIG_IS_ENABLED() This macro is used to determine whether an option is enabled in the current build phase: if (CONFIG_IS_ENABLED(FIT_SIGNATURE)) { printf("## Checking hash(es) for Image %s ... ", fit_get_name(fit, node, NULL)); It is quite long-winded and people sometimes add CONFIG_ to the option inside the brakets by mistake. It is also a bit confusing that IS_ENABLED() and CONFIG_IS_ENABLED() mean completely different things. Instead we can rename it to CONFIG: if (CONFIG(FIT_SIGNATURE)) { printf("## Checking hash(es) for Image %s ... ", fit_get_name(fit, node, NULL)); This is shorter and looks more like CONFIG_FIT_SIGATURE so people should find it easier to understand. Being shorter is a big help when converting from use #if to if(), since an indentation is always enabled. This change makes the CONFIG() check no longer than IS_ENABLED(). It also makes CONFIG(OPTION) not much longer than CONFIG_OPTION, which makes things much more convenient, since ideally if the toolchain permitted it, we would just use CONFIG_OPTION in the code. This is not possible at present since the option may not be defined, so can cause a compiler error. Over time, perhaps the existing IS_ENABLED() will phase out, since in many cases SPL will have its own options. We already see that CONFIG_IS_ENABLED is more popular / useful: $ git grep -w IS_ENABLED |wc -l 902 $ git grep -w CONFIG_IS_ENABLED |wc -l 2282 4. Add macros to help avoid more #ifdefs We sometimes have to use #ifdefs in structs or drivers: struct spl_image_loader { #ifdef CONFIG_SPL_LIBCOMMON_SUPPORT const char *name; #endif ... }; UCLASS_DRIVER(spi) = { .id = UCLASS_SPI, .name = "spi", .flags = DM_UC_FLAG_SEQ_ALIAS, #if CONFIG_IS_ENABLED(OF_CONTROL) && !CONFIG_IS_ENABLED(OF_PLATDATA) .post_bind = dm_scan_fdt_dev, #endif ... }; This is a pain. We can add an IF_CONFIG macro to help with this: struct spl_image_loader { IF_CONFIG(LIBCOMMON_SUPPORT, const char *name;) ... }; UCLASS_DRIVER(spi) = { .id = UCLASS_SPI, .name = "spi", .flags = DM_UC_FLAG_SEQ_ALIAS, IF_CONFIG(REAL, .post_bind = dm_scan_fdt_dev,) ... }; It still isn't wonderfully readable but it seems like an improvement. The IF_CONFIG() macros could be implemented easily with the current CONFIG_IS_EANBLED() macro. 5. IF_CONFIG_INT() or similar See here: https://lists.denx.de/pipermail/u-boot/2020-May/412950.html 6. Discarding static functions We sometimes see code like this: #if CONFIG_IS_ENABLED(OF_REAL) static const struct udevice_id apl_ns16550_serial_ids[] = { { .compatible = "intel,apl-ns16550" }, { }, }; #endif U_BOOT_DRIVER(intel_apl_ns16550) = { .name = "intel_apl_ns16550", .id = UCLASS_SERIAL, .of_match = of_match_ptr(apl_ns16550_serial_ids), .plat_auto = sizeof(struct apl_ns16550_plat), .priv_auto = sizeof(struct ns16550), ... }; The of_match_ptr() avoids an #ifdef in the driver declaration since it evaluates to NULL if !CONFIG_IS_ENABLED(OF_REAL) but we still need an #ifdef around the function, since it is static and would otherwise produce a warning. One solution is to drop the 'static'. But this is not very nice, since the structure clearly should not be used from another file. We can add STATIC_IF_CONFIG() to help with this: STATIC_IF_CONFIG(OF_REAL) const struct udevice_id apl_ns16550_serial_ids[] = { { .compatible = "intel,apl-ns16550" }, { }, }; #endif It expands to 'static' if CONFIG(OF_REAL) is enabled, otherwise it expand to nothing, in the hope that the compiler drops the data. Failing that it would also be possible to have it expand to '__section(".discard.config")' so at least the struct is discarded, even if the compatible string is not. The behaviour of gcc/binutils in this area is not always as might be hoped. Comments welcome! - Simon

4 24

Please pull u-boot-cfi-flash/master
by Stefan Roese 11 Aug '21

11 Aug '21

Hi Tom, please pull the next batch of CFI flash related patches. Here the summary log: ---------------------------------------------------------------- - Some CFI flash related fixups (Kconfig & header) (Bin) - Enable CFI flash support on the QEMU RISC-V virt machine. (Bin) ---------------------------------------------------------------- Here the Azure build, without any issues: https://dev.azure.com/sr0718/u-boot/_build/results?buildId=107&view=results Thanks, Stefan The following changes since commit 3e5b62f78888740530e6f3a2e989f4c361a9d52b: configs: Resync with savedefconfig (2021-08-10 15:08:46 -0400) are available in the Git repository at: git@source.denx.de:u-boot/custodians/u-boot-cfi-flash.git for you to fetch changes up to d248627f9d4218688e7430bc714405a23885abfa: riscv: qemu: Enable MTD NOR flash support (2021-08-11 10:36:10 +0200) ---------------------------------------------------------------- Bin Meng (3): mtd: kconfig: Fix CFI_FLASH dependency flash.h: Remove CONFIG_SYS_FLASH_CFI from flash_info_t riscv: qemu: Enable MTD NOR flash support board/emulation/qemu-riscv/Kconfig | 2 ++ drivers/mtd/Kconfig | 1 + include/configs/qemu-riscv.h | 2 ++ include/flash.h | 2 -- 4 files changed, 5 insertions(+), 2 deletions(-)

2 1

Please pull u-boot-marvell/master
by Stefan Roese 11 Aug '21

11 Aug '21

Hi Tom, please pull the next batch of Marvell MVEBU related patches. Here the summary log: ---------------------------------------------------------------- - Convert GoFlex Home Ethernet and SATA to Driver Model (Tony) - mvebu: Automatically detect CONFIG_SYS_TCLK (Pavel) - mvebu: sata_mv: Fix HDD identication during cold start (Tony) - a37xx: pci: Fix handling PIO config error responses (Pavel) - Other minor misc changes and board maintainer updates ---------------------------------------------------------------- Here the Azure build, without any issues: https://dev.azure.com/sr0718/u-boot/_build/results?buildId=106&view=results Thanks, Stefan The following changes since commit 3e5b62f78888740530e6f3a2e989f4c361a9d52b: configs: Resync with savedefconfig (2021-08-10 15:08:46 -0400) are available in the Git repository at: git@source.denx.de:u-boot/custodians/u-boot-marvell.git for you to fetch changes up to e21c74f24be5b6d0387d79cb8cf66de0b9b6b0d3: arm: kirkwood: Goflex Home: Update board maintainer (2021-08-11 08:42:26 +0200) ---------------------------------------------------------------- Pali Rohár (7): arm: mvebu: a38x: Detect CONFIG_SYS_TCLK from SAR register arm: mvebu: a37x: Detect CONFIG_SYS_TCLK from SAR register arm: mvebu: msys: Set CONFIG_SYS_TCLK globally arm: mvebu: axp: Set CONFIG_SYS_TCLK globally arm: kirkwood: Do not overwrite CONFIG_SYS_TCLK arm: a37xx: pci: Fix handling PIO config error responses arm: mvebu: Hang if ddr3_init() fails Tony Dinh (6): arm: kirkwood: GoFlex Home: Add DM Ethernet, remove IDE, and add DM SATA configs arm: kirkwood: GoFlex Home: Add DM SATA configs arm: kirkwood: GoFlex Home: Use Ethernet PHY name and address from device tree arm: mvebu: sata_mv failed to identify HDDs during cold start arm: kirkwood: Dockstar: Update board maintainer arm: kirkwood: Goflex Home: Update board maintainer arch/arm/mach-kirkwood/include/mach/kw88f6281.h | 2 - arch/arm/mach-mvebu/include/mach/soc.h | 15 ++++--- arch/arm/mach-mvebu/spl.c | 6 ++- board/Seagate/dockstar/MAINTAINERS | 2 +- board/Seagate/goflexhome/MAINTAINERS | 2 +- board/Seagate/goflexhome/goflexhome.c | 57 +++++++++++++++++++------ configs/goflexhome_defconfig | 5 ++- drivers/ata/sata_mv.c | 29 ++++++++++++- drivers/pci/pci-aardvark.c | 52 +++++++++++----------- include/configs/clearfog.h | 1 - include/configs/controlcenterdc.h | 2 - include/configs/crs3xx-98dx3236.h | 1 - include/configs/db-88f6720.h | 1 - include/configs/db-88f6820-amc.h | 2 - include/configs/db-88f6820-gp.h | 2 - include/configs/db-mv784mp-gp.h | 1 - include/configs/db-xc3-24g4xg.h | 1 - include/configs/ds414.h | 1 - include/configs/goflexhome.h | 6 +++ include/configs/helios4.h | 1 - include/configs/lacie_kw.h | 5 --- include/configs/lsxl.h | 2 - include/configs/maxbcm.h | 1 - include/configs/theadorable.h | 1 - include/configs/turris_omnia.h | 1 - include/configs/x530.h | 2 - 26 files changed, 125 insertions(+), 76 deletions(-)

2 1

[PULL u-boot] Please pull u-boot-amlogic-202107810
by Neil Armstrong 11 Aug '21

11 Aug '21

Hi Tom, Here's a bunch of changes concerning: - single fix for odroid-n2+ detection - HW reboot_reason drop in favor of BCB for Android boot state tracking - meson64_android config cleanups and support for A/V, AVB and fastbootd via recovery While the actual meson64_android config removes distro defaults targets and makes booting non-Android possible but complex, we are working toward either adding back the default targets or trying to leverage boot_android at some point to avoid building android-only u-boot binaries. The CI job is at https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic/pipelines/8655 Thanks, Neil The following changes since commit bbcacdf4cd23f2e5deb9ef916096c956c955243d: Merge branch '2021-07-28-build-improvements' (2021-07-28 18:51:16 -0400) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-amlogic.git tags/u-boot-amlogic-20210810 for you to fetch changes up to 33b51765583e6cbe1888f068da795bea599bad18: configs: sei510/610: android bootflow via abootimg (2021-08-10 10:43:54 +0200) ---------------------------------------------------------------- - odroid-n2: fix fdtfile suffix for n2-plus - sei610 & meson64_android cleanups to prepare android 11 boot support - use Android BCB mechanism for reboot reason instead of HW reboot flag - Switch meson64_android boot flow to use abootimg for A/B, AVB and DTBO support ---------------------------------------------------------------- Christian Hewitt (1): board: amlogic: odroid-n2: fix fdtfile suffix for n2-plus Guillaume La Roque (2): configs: meson64_android: boot android via abootimg configs: sei510/610: android bootflow via abootimg Mattijs Korpershoek (18): configs: sei610: fix typo in header comment configs: meson64_android: fix bad indent in EXTRA_ENV_SETTINGS configs: meson64_android: use CONFIG_FASTBOOT_USB_DEV configs: meson64_android: use boot part label instead of index configs: meson64_android: use logo part label instead of index configs: meson64_android: don't set console bootargs configs: meson64_android: use BCB for reboot to bootloader configs: meson64_android: implement recovery boot via BCB configs: meson64_android: reboot to fastbootd from bootloader configs: sei610/sei510: set CONFIG_CMD_BCB=y Revert "ARM: meson: Add support for fastboot_set_reboot_flag()" configs: meson64: permit redefining SYS_MALLOC_LEN configs: meson64_android: increase SYS_MALLOC_LEN to 128M for AVB configs: meson64_android: implement AVB support configs: meson64_android: implement A/B slot support configs: meson64_android: define BOOT_CMD macro configs: sei510/sei610: reformat PARTS_default configs: sei510/sei610: don't use hard-coded gpt uuids arch/arm/mach-meson/board-common.c | 34 ------ board/amlogic/odroid-n2/odroid-n2.c | 2 +- configs/odroid-n2_defconfig | 2 +- configs/sei510_defconfig | 6 + configs/sei610_defconfig | 6 + include/configs/meson64.h | 2 + include/configs/meson64_android.h | 215 ++++++++++++++++++++++++++++++------ include/configs/sei510.h | 23 ++-- include/configs/sei610.h | 25 ++--- 9 files changed, 220 insertions(+), 95 deletions(-)

2 1

Building U-Boot for Compulab's imx8mm-cl-iot-gate board
by Fabio Estevam 11 Aug '21

11 Aug '21

Hi Paul, I am trying to build U-Boot 2021.07-rc5 for the imx8mm-cl-iot-gate_defconfig target and I am following the imx8mm-evk readme: doc/board/freescale/imx8mm_evk.rst for the build instructions and this is the output: make[1]: Nothing to be done for 'SPL'. BINMAN all Image 'main-section' is missing external blobs and is non-functional: blob-ext Some images are invalid This happens because I did not provide the fip.bin binary. Is it OK if I remove the fip.bin entry like this? Would the board still boot? --- a/arch/arm/dts/imx8mm-cl-iot-gate-u-boot.dtsi +++ b/arch/arm/dts/imx8mm-cl-iot-gate-u-boot.dtsi @@ -217,18 +217,6 @@ }; }; - fip { - description = "Trusted Firmware FIP"; - type = "firmware"; - arch = "arm64"; - compression = "none"; - load = <0x40310000>; - - fip_blob: blob-ext{ - filename = "fip.bin"; - }; - }; - fdt { description = "NAME"; type = "flat_dt"; Could you please let me know the process for generating fip.bin? It would be nice to have a doc/board/compulab/imx8mm-iot-gate.rst README file with these details. I can help with that but need your help to clarify the generation of fip.bin. Also, is it OK if I use the ATF firmware and LPDDR binaries version as specified in doc/board/freescale/imx8mm_evk.rst ? Thanks, Fabio Estevam

2 8

[RFC PATCH v1] phy: rockchip: add basic rk3328 support to phy-rockchip-inno-usb2.c
by Johan Jonker 11 Aug '21

11 Aug '21

The rk3328 uses a usb phy simulair to rk3399 with only 1 instead of 2 usb ports. Reuse existing U-boot driver and add basic rk3328 support to phy-rockchip-inno-usb2.c Signed-off-by: Johan Jonker <jbx6244(a)gmail.com> --- drivers/phy/rockchip/phy-rockchip-inno-usb2.c | 29 +++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/drivers/phy/rockchip/phy-rockchip-inno-usb2.c b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c index 62b8ba3a4a..bfb531d3cd 100644 --- a/drivers/phy/rockchip/phy-rockchip-inno-usb2.c +++ b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c @@ -243,6 +243,31 @@ static int rockchip_usb2phy_bind(struct udevice *dev) return ret; } +static const struct rockchip_usb2phy_cfg rk3328_usb2phy_cfgs[] = { + { + .reg = 0x100, + .port_cfgs = { + [USB2PHY_PORT_OTG] = { + .phy_sus = { 0x0100, 8, 0, 0, 0x1d1 }, + .bvalid_det_en = { 0x0110, 2, 2, 0, 1 }, + .bvalid_det_st = { 0x0114, 2, 2, 0, 1 }, + .bvalid_det_clr = { 0x0118, 2, 2, 0, 1 }, + .utmi_avalid = { 0x0120, 10, 10, 0, 1 }, + .utmi_bvalid = { 0x0120, 9, 9, 0, 1 }, + }, + [USB2PHY_PORT_HOST] = { + .phy_sus = { 0x104, 8, 0, 0, 0x1d1 }, + .ls_det_en = { 0x110, 1, 1, 0, 1 }, + .ls_det_st = { 0x114, 1, 1, 0, 1 }, + .ls_det_clr = { 0x118, 1, 1, 0, 1 }, + .utmi_ls = { 0x120, 17, 16, 0, 1 }, + .utmi_hstdet = { 0x120, 19, 19, 0, 1 } + } + }, + }, + { /* sentinel */ } +}; + static const struct rockchip_usb2phy_cfg rk3399_usb2phy_cfgs[] = { { .reg = 0xe450, @@ -291,6 +316,10 @@ static const struct rockchip_usb2phy_cfg rk3399_usb2phy_cfgs[] = { static const struct udevice_id rockchip_usb2phy_ids[] = { { + .compatible = "rockchip,rk3328-usb2phy", + .data = (ulong)&rk3328_usb2phy_cfgs + }, + { .compatible = "rockchip,rk3399-usb2phy", .data = (ulong)&rk3399_usb2phy_cfgs, }, -- 2.11.0

2 2

[PATCH 0/3] Add support for the GST ESPRESSOBin-Ultra board
by Gerald Kerma 11 Aug '21

11 Aug '21

From: Kerma Gérald <gandalf(a)gk2.net> Add support for the GST ESPRESSOBin-Ultra board Kerma Gérald (3): cmd: mvebu: Implement the Marvell hw_info command arm: mvebu: mvebu_armada-37xx: Define the loadaddr environment variable arm: mvebu: Initial ESPRESSOBin-Ultra board support arch/arm/dts/Makefile | 1 + .../arm/dts/armada-3720-espressobin-ultra.dts | 202 ++++++++++++ board/Marvell/mvebu_armada-37xx/MAINTAINERS | 9 + board/Marvell/mvebu_armada-37xx/board.c | 92 +++++- cmd/mvebu/Kconfig | 23 ++ cmd/mvebu/Makefile | 2 + cmd/mvebu/hw_info.c | 312 ++++++++++++++++++ .../mvebu_espressobin-ultra-88f3720_defconfig | 92 ++++++ include/configs/mvebu_armada-37xx.h | 1 + lib/hashtable.c | 2 +- 10 files changed, 729 insertions(+), 7 deletions(-) create mode 100644 arch/arm/dts/armada-3720-espressobin-ultra.dts create mode 100644 cmd/mvebu/hw_info.c create mode 100644 configs/mvebu_espressobin-ultra-88f3720_defconfig -- 2.30.2

3 5

[PATCH 1/3] mtd: kconfig: Fix CFI_FLASH dependency
by Bin Meng 11 Aug '21

11 Aug '21

The DM version CFI flash driver is in driver/mtd/cfi_flash.c, which only gets built when FLASH_CFI_DRIVER is on. If CFI_FLASH is on but FLASH_CFI_DRIVER is not, nothing is enabled at all. Fix this dependency by selecting FLASH_CFI_DRIVER when CFI_FLASH is enabled. Signed-off-by: Bin Meng <bmeng.cn(a)gmail.com> --- drivers/mtd/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig index ad50c5e870..b303fabe0f 100644 --- a/drivers/mtd/Kconfig +++ b/drivers/mtd/Kconfig @@ -42,6 +42,7 @@ config FLASH_CFI_DRIVER config CFI_FLASH bool "Enable Driver Model for CFI Flash driver" depends on DM_MTD + select FLASH_CFI_DRIVER help The Common Flash Interface specification was developed by Intel, AMD and other flash manufactures. It provides a universal method -- 2.25.1

2 8

[PATCH v7 0/6] rockchip_sfc: add support for Rockchip SFC
by Jon Lin 11 Aug '21

11 Aug '21

Changes in v7: - Make sfc-use-dma configurable - Remove SPI_NOR_HAS_TB and SPI_NOR_HAS_LOCK - Make px30 SFC clock configurable Changes in v6: - Fix dma transfer logic - Fix the error of the way to wait for dma transfer finished status Changes in v5: - Support dma transfer - Add CONFIG_IS_ENABLED(CLK) limitation - Support spinand devices - Support SFC ver4 ver5 - Using "rockchip, sfc" as compatible id - Get clock from the index to compatible with those case which's clock-names is not parsed - px30 use "rockchip, sfc" as compatible id Changes in v4: - None Changes in v3: - Added "rockchip_sfc_adjust_op_work()" function from proposed Linux driver to fix potential issue on hardware. Note I never noticed this issue while testing, so I cannot test if it fixed any specific issue for me. - Updated of-compatible string back to "rockchip,sfc" to match what is currently proposed for upstream driver. The hardware itself has multiple versions but a register is present in the hardware that is read by the driver to set version specific functionality. - Updated px30.dtsi and rk3266-odroid-go2.dts device-trees so that sfc nodes match what is in upstream. Changes in v2: - Resending due to glitch with patch file truncating final two lines on patch 1/5 and incorrect patch version number on patch 5/5. Changes in v1: - Reworked code to utilize spi-mem framework, and based it closely off of work in progress code for mainline Linux. - Removed DMA, as it didn't offer much performance benefit for booting (in my test cases), added complexity to the code, and interfered with A-TF. - Updated the names of the bindings to match the work in progress Linux code. - Moved alias to u-boot specific device-tree for Odroid Go Advance. Alias is updated with the spi0 node pointing to the SFC to help the sf command as well as facilitate booting from the SFC. - Note 2 below no longer applies, as rebasing this off of upstream code should allow the device to work for NAND, and by utilizing the spi-mem framework it no longer has to extract the parameters Chris Morgan (5): spi: rockchip_sfc: add support for Rockchip SFC rockchip: px30: Add support for using SFC rockchip: px30: add the serial flash controller mtd: spi-nor-ids: Add XTX XT25F128B rockchip: px30: add support for SFC for Odroid Go Advance Jon Lin (1): rockchip: px30: Support configure SFC arch/arm/dts/px30.dtsi | 38 ++ arch/arm/dts/rk3326-odroid-go2-u-boot.dtsi | 17 + arch/arm/dts/rk3326-odroid-go2.dts | 16 + arch/arm/mach-rockchip/px30/px30.c | 64 ++ drivers/clk/rockchip/clk_px30.c | 32 + drivers/mtd/spi/Kconfig | 6 + drivers/mtd/spi/spi-nor-ids.c | 4 + drivers/spi/Kconfig | 8 + drivers/spi/Makefile | 1 + drivers/spi/rockchip_sfc.c | 646 +++++++++++++++++++++ 10 files changed, 832 insertions(+) create mode 100644 drivers/spi/rockchip_sfc.c -- 2.17.1

5 22