December 2021 - U-Boot

[PATCH u-boot-marvell 0/2] arm: mvebu: Add maintainer entries for Marvell PCIe and serial drivers
by Pali Rohár 18 Dec '21

18 Dec '21

Hello Stefan! I did big cleanup of Marvell PCIe and serial drivers and I'm sending these two patches which adds me as author and co-maintainer of these two drivers. Pali Rohár (2): arm: mvebu: pci: Add me as co-maintainer and author of Marvell PCIe drivers arm: mvebu: serial: Add me as co-maintainer and author of Marvell serial drivers MAINTAINERS | 16 +++++++++++++++- drivers/pci/pci-aardvark.c | 1 + drivers/pci/pci_mvebu.c | 1 + drivers/serial/serial_mvebu_a3700.c | 1 + 4 files changed, 18 insertions(+), 1 deletion(-) -- 2.20.1

2 5

[PATCH 0/2] arm: mvebu: a38x: improve USB3 serdes configuration
by Stefan Eichenberger 18 Dec '21

18 Dec '21

This patchset improves the USB3 serdes configuration for the Armada 38x SoC from Marvell. The changes are based on the version from Marvell found here: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell Stefan Eichenberger (2): arm: mvebu: a38x: serdes: fix serdes config for USB3 arm: mvebu: a38x: serdes: Improve USB3 electrical configuration .../serdes/a38x/high_speed_env_spec.c | 38 ++++++++++++++----- arch/arm/mach-mvebu/serdes/a38x/sys_env_lib.h | 2 + 2 files changed, 31 insertions(+), 9 deletions(-) -- 2.30.2

2 5

[PATCH u-boot-marvell RESEND 00/11] Some mvebu comphy + mox + fdt_support changes
by Marek Behún 18 Dec '21

18 Dec '21

From: Marek Behún <marek.behun(a)nic.cz> Hello Stefan, as requested I am resending this series with board maintainers added in Ccs. Original message: Pali prepared patches that convert A3720 comphy driver to use Linux' DT bindings. (Yes, I have patches that convert the whole driver into using SMC calls into ATF, but haven't found time yet to rebase them since last year, and Pali has done this in the meantime :-D Maybe I'll look into my old patches sometimes, but this is now usable.) These patches needed some changes in Turris MOX board code, and I added some more changes to handling device-tree fixups, and this lead to adding some code into fdt_support, which can hopefully be used by other people as well. Marek Marek Behún (8): treewide: Use fdt_create_phandle() where appropriate fdt_support: Remove fdt_alloc_phandle() in favor of fdt_generate_phandle() fdt_support: Remove FDT_STATUS_FAIL_ERROR_CODE fdt_support: Fix comment for fdt_create_phandle() fdt_support: Add some useful functions arm: mvebu: turris_mox: Find DT nodes by compatible or alias instead of path arm: mvebu: turris_mox: Fix unstable board topology reading fdt_support: Add fdt_delete_disabled_nodes() and use in Turris MOX Pali Rohár (3): include/linux/byteorder: Fix compilation of __constant_cpu_to_be32() arm: mvebu: turris_mox: Enable eth1 in U-Boot if a network module is present phy: marvell: a3700: Convert to official DT bindings in COMPHY driver arch/arm/cpu/armv7/ls102xa/fdt.c | 6 +- arch/arm/dts/armada-3720-espressobin.dts | 21 +-- arch/arm/dts/armada-3720-turris-mox.dts | 25 +-- arch/arm/dts/armada-3720-uDPU.dts | 23 +-- arch/arm/dts/armada-37xx.dtsi | 20 +- board/CZ.NIC/turris_mox/turris_mox.c | 223 ++++++++--------------- board/Marvell/octeon_ebb7304/board.c | 5 +- board/freescale/lx2160a/eth_lx2160aqds.c | 8 +- board/freescale/lx2160a/eth_lx2162aqds.c | 8 +- board/gateworks/gw_ventana/common.c | 3 +- board/kontron/sl28/sl28.c | 2 +- common/fdt_support.c | 174 +++++++++++++++--- drivers/misc/fsl_portals.c | 10 +- drivers/pci/pcie_layerscape_fixup.c | 8 +- drivers/pci/pcie_layerscape_gen4_fixup.c | 8 +- drivers/phy/marvell/comphy_a3700.c | 133 ++++++++++++++ drivers/phy/marvell/comphy_core.c | 59 +----- drivers/phy/marvell/comphy_core.h | 23 +++ drivers/phy/marvell/comphy_cp110.c | 58 ++++++ include/fdt_support.h | 51 ++++-- include/linux/byteorder/swab.h | 4 + 21 files changed, 551 insertions(+), 321 deletions(-) -- 2.32.0

4 16

[PATCH 1/9] arm: mvebu: theadorable_debug_defconfig: Enable DM_I2C
by Stefan Roese 18 Dec '21

18 Dec '21

Move to the DM I2C version, so that this board will not get dropped from mainline. Signed-off-by: Stefan Roese <sr(a)denx.de> --- configs/theadorable_debug_defconfig | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/configs/theadorable_debug_defconfig b/configs/theadorable_debug_defconfig index 556c91fe3ed0..cfa1bac707c9 100644 --- a/configs/theadorable_debug_defconfig +++ b/configs/theadorable_debug_defconfig @@ -58,10 +58,8 @@ CONFIG_SATA_MV=y CONFIG_BOOTCOUNT_LIMIT=y CONFIG_BOOTCOUNT_RAM=y CONFIG_FPGA_ALTERA=y -CONFIG_SYS_I2C_LEGACY=y -CONFIG_SPL_SYS_I2C_LEGACY=y +CONFIG_DM_I2C=y CONFIG_SYS_I2C_MVTWSI=y -CONFIG_SYS_I2C_SLAVE=0x0 # CONFIG_MMC is not set CONFIG_SF_DEFAULT_SPEED=27777777 CONFIG_SPI_FLASH_MACRONIX=y -- 2.34.0

1 17

[BUG] doc: building htmldocs with sphinx-rtd-theme 1.0.0 fails
by Heinrich Schuchardt 18 Dec '21

18 Dec '21

When building 'make htmldocs' with package sphinx-rtd-theme 1.0.0 (https://pypi.org/project/sphinx-rtd-theme/1.0.0/) used by Ubuntu Jammy and Debian Bookworm the output is not well formatted. With version 0.5.1 everything looks fine. Best regards Heinrich

1 0

[BUG] patman: refused to send patches because of warnings
by Tony Dinh 18 Dec '21

18 Dec '21

Hi Simon, I tried to send in patches to add support for a new board. patman seems to hit a problem with "Bad divisor in main" error and refuses to send the patches. The warnings are not really important, are they? In some instances, we need camel cases because that is what the convention in the specs for MPPs. And the #ifdef or #if is necessary because the "if (IS_ENABLED(CONFIG...))" cannot be used to compile-out a function. And the warnings about MAINTAINERS seem unnecessary. Is there an option to tell patman to ignore the warnings or checks? Here is the patman log. ./tools/patman/patman -c8 send Cleaned 8 patches 0 errors, 1 warnings, 0 checks for 0001-arm-kirkwood-Pogoplug-V4-Add-DTS-files.patch: <patch>:29: warning: added, moved or deleted file(s), does MAINTAINERS need updating? 0 errors, 1 warnings, 0 checks for 0002-arm-kirkwood-Pogoplug-V4-Add-board-defconfig-file.patch: <patch>:16: warning: added, moved or deleted file(s), does MAINTAINERS need updating? 0 errors, 2 warnings, 0 checks for 0003-arm-kirkwood-Pogoplug-V4-Add-Kconfig-files.patch: arch/arm/mach-kirkwood/Kconfig:28: warning: please write a paragraph that describes the config symbol fully <patch>:39: warning: added, moved or deleted file(s), does MAINTAINERS need updating? 0 errors, 1 warnings, 0 checks for 0004-arm-kirkwood-Pogoplug-V4-Add-board-include-configs-f.patch: <patch>:17: warning: added, moved or deleted file(s), does MAINTAINERS need updating? 0 errors, 1 warnings, 0 checks for 0005-arm-kirkwood-Pogoplug-V4-Add-board-kwbimage-file.patch: <patch>:16: warning: added, moved or deleted file(s), does MAINTAINERS need updating? 0 errors, 1 warnings, 0 checks for 0006-arm-kirkwood-Pogoplug-V4-Add-board-implementation-he.patch: <patch>:19: warning: added, moved or deleted file(s), does MAINTAINERS need updating? 0 errors, 3 warnings, 3 checks for 0007-arm-kirkwood-Pogoplug-V4-Add-board-implementation.patch: <patch>:23: warning: added, moved or deleted file(s), does MAINTAINERS need updating? board/cloudengines/pogo_v4/pogo_v4.c:49: check: Avoid CamelCase: <MPP6_SYSRST_OUTn> board/cloudengines/pogo_v4/pogo_v4.c:63: check: Avoid CamelCase: <MPP20_SATA1_ACTn> board/cloudengines/pogo_v4/pogo_v4.c:64: check: Avoid CamelCase: <MPP21_SATA0_ACTn> board/cloudengines/pogo_v4/pogo_v4.c:137: warning: Use 'if (IS_ENABLED(CONFIG...))' instead of '#if or #ifdef' where possible board/cloudengines/pogo_v4/pogo_v4.c:170: warning: Use 'if (IS_ENABLED(CONFIG...))' instead of '#if or #ifdef' where possible 0 errors, 1 warnings, 0 checks for 0008-arm-kirkwood-Pogoplug-V4-Add-board-maintainer.patch: <patch>:16: warning: added, moved or deleted file(s), does MAINTAINERS need updating? checkpatch.pl found 0 error(s), 11 warning(s), 3 checks(s) Bad divisor in main::vcs_assign: 0 Not sending emails due to errors/warnings Thanks, Tony

2 2

Please pull u-boot-dm/next
by Simon Glass 18 Dec '21

18 Dec '21

Hi Tom, This is for the -next branch. https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/10299 The following changes since commit b9c9ce8a4064c8d88f714604db856cf1cd2b40b5: Merge tag 'u-boot-at91-2022.04-a' of https://source.denx.de/u-boot/custodians/u-boot-at91 into next (2021-12-17 07:25:34 -0500) are available in the Git repository at: git://git.denx.de/u-boot-dm.git tags/dm-pull-17dec21 for you to fetch changes up to 121cfe5a84d463893bd01da16417ab138f98666a: fdtgrep: Handle an empty output tree (2021-12-17 09:44:59 -0700) ---------------------------------------------------------------- binman support for ATF FIP fdtgrep fixes for empty devicetree ---------------------------------------------------------------- Andy Shevchenko (2): binman: Do not pollute source tree when build with `make O=...` binman: Use less hard coded magic when inserting new PATH Ivan Mikhaylov (1): iot2050: binman: add missing-msg for blobs Simon Glass (5): binman: Add a utility module for ATF FIP binman: Add support for ATF FIP Convert CONFIG_PHYSMEM to Kconfig fdtgrep: Correct alignment of struct section fdtgrep: Handle an empty output tree README | 8 - arch/Kconfig | 2 + arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 5 + boot/fdt_region.c | 43 ++- include/configs/edison.h | 3 - include/configs/sandbox.h | 2 - include/configs/x86-common.h | 2 - include/fdt_region.h | 1 + lib/Kconfig | 10 + scripts/config_whitelist.txt | 1 - tools/binman/entries.rst | 154 +++++++++++ tools/binman/etype/atf_fip.py | 273 +++++++++++++++++++ tools/binman/fip_util.py | 653 ++++++++++++++++++++++++++++++++++++++++++++++ tools/binman/fip_util_test.py | 405 ++++++++++++++++++++++++++++ tools/binman/ftest.py | 217 +++++++++++++++ tools/binman/main.py | 27 +- tools/binman/missing-blob-help | 11 + tools/binman/test/203_fip.dts | 21 ++ tools/binman/test/204_fip_other.dts | 22 ++ tools/binman/test/205_fip_no_type.dts | 15 ++ tools/binman/test/206_fip_uuid.dts | 22 ++ tools/binman/test/207_fip_ls.dts | 25 ++ tools/binman/test/208_fip_replace.dts | 33 +++ tools/binman/test/209_fip_missing.dts | 19 ++ tools/binman/test/210_fip_size.dts | 19 ++ tools/binman/test/211_fip_bad_align.dts | 18 ++ tools/binman/test/212_fip_collection.dts | 24 ++ tools/fdtgrep.c | 3 +- 28 files changed, 2008 insertions(+), 30 deletions(-) create mode 100644 tools/binman/etype/atf_fip.py create mode 100755 tools/binman/fip_util.py create mode 100755 tools/binman/fip_util_test.py create mode 100644 tools/binman/test/203_fip.dts create mode 100644 tools/binman/test/204_fip_other.dts create mode 100644 tools/binman/test/205_fip_no_type.dts create mode 100644 tools/binman/test/206_fip_uuid.dts create mode 100644 tools/binman/test/207_fip_ls.dts create mode 100644 tools/binman/test/208_fip_replace.dts create mode 100644 tools/binman/test/209_fip_missing.dts create mode 100644 tools/binman/test/210_fip_size.dts create mode 100644 tools/binman/test/211_fip_bad_align.dts create mode 100644 tools/binman/test/212_fip_collection.dts Regards, Simon

2 1

[PATCH v3] timer: Add a migration message
by Simon Glass 18 Dec '21

18 Dec '21

Some boards still use the old timer mechanism. Set a deadline for them to update to driver model. Point to some examples as well. This needs a bit of a strange rule to avoid an error on some boards. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- Changes in v3: - Push out the deadline Makefile | 4 ++++ doc/develop/driver-model/migration.rst | 12 ++++++++++++ 2 files changed, 16 insertions(+) diff --git a/Makefile b/Makefile index ab32efb4d11..7b24250103e 100644 --- a/Makefile +++ b/Makefile @@ -1124,6 +1124,10 @@ endif $(call deprecated,CONFIG_DM_ETH,Ethernet drivers,v2020.07,$(CONFIG_NET)) $(call deprecated,CONFIG_DM_I2C,I2C drivers,v2022.04,$(CONFIG_SYS_I2C_LEGACY)) $(call deprecated,CONFIG_DM_KEYBOARD,Keyboard drivers,v2022.10,$(CONFIG_KEYBOARD)) + @# CONFIG_SYS_TIMER_RATE has brackets in it for some boards which + @# confuses this rule. Use if() to send just a single character which + @# is enable to tell 'deprecated' that one of these symbols exists + $(call deprecated,CONFIG_TIMER,Timer drivers,v2023.01,$(if $(strip $(CONFIG_SYS_TIMER_RATE)$(CONFIG_SYS_TIMER_COUNTER)),x)) @# Check that this build does not use CONFIG options that we do not @# know about unless they are in Kconfig. All the existing CONFIG @# options are whitelisted, so new ones should not be added. diff --git a/doc/develop/driver-model/migration.rst b/doc/develop/driver-model/migration.rst index 3dbeea6537c..ed342bd4930 100644 --- a/doc/develop/driver-model/migration.rst +++ b/doc/develop/driver-model/migration.rst @@ -106,3 +106,15 @@ Deadline: 2022.10 This is a legacy option which has been replaced by driver model. Maintainers should submit patches switching over to using CONFIG_DM_KEYBOARD and other base driver model options in time for inclusion in the 2022.10 release. + +CONFIG_SYS_TIMER_RATE and CONFIG_SYS_TIMER_COUNTER +-------------------------------------------------- +Deadline: 2023.01 + +These are legacy options which have been replaced by driver model. +Maintainers should submit patches switching over to using CONFIG_TIMER and +other base driver model options in time for inclusion in the 2022.10 release. + +There is only one method to implement, unless you want to support bootstage, +in which case you need an early timer alsol. For example drivers, see +sandbox_timer.c and rockchip_timer.c -- 2.34.1.173.g76aa8bc2d0-goog

2 1

Re: Broken arc toolchain
by Alexey Brodkin 18 Dec '21

18 Dec '21

Hi Tom and Simon, So there're a couple of things involved indeed. 1. As Tom correctly mentioned we used to use SNSP pre-built tools for ARC in TravisCI previously. And frankly the reason was we needed something GCC 8.x based while on some other arches such a new GCC triggered extra problems, see https://lists.denx.de/pipermail/u-boot/2018-May/329577.html. So I updated ARC pre-built versions and we kept using it. 2. Now, that particular "mcpu" was never added into upstream GCC because we wanted to re-implement it a bit nicer, thus any up-to-date vanilla GCC won't accept it as opposed to tools built from SNPS' GCC port [which has it https://github.com/foss-for-synopsys-dwc-arc-processors/gcc/commit/84a3ee38…]. 3. IIRC "-mcpu=hs4x_rel31" is basically an umbrella option for some options combination based on generic "-mcpu=hs4x" so we may probably update HSDK-4xD flags to be buildable by vanialla GGC. But anyways the simples short-term solution is to use our pre-built tools, latest of which are avaialble here https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/…. And for U-Boot elf32 version is what I would suggest to use, so please use https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/…. Moreover since by default for ARC we use U-Boot built-in libgcc the same one little-endian toolchain might be safely used for building our big-endian configs equally well. If more info or actions needed, please let me know. -Alexey ________________________________ From: Tom Rini Sent: Saturday, July 10, 2021 11:22 PM To: Simon Glass Cc: U-Boot Mailing List; Alexey Brodkin; Eugeniy Paltsev Subject: Re: Broken arc toolchain On Sat, Jul 10, 2021 at 02:11:30PM -0600, Simon Glass wrote: > Hi, > > I see this: > > $ buildman --fetch-arch arc > > Downloading toolchain for arch 'arc' > Checking: https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/9.2.0/ > Downloading: https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/9.2.0/x86_64-gc… > Unpacking to: /home/sglass/.buildman-toolchains > Testing > - looking in > '/home/sglass/.buildman-toolchains/gcc-9.2.0-nolibc/arc-linux/.' > - looking in > '/home/sglass/.buildman-toolchains/gcc-9.2.0-nolibc/arc-linux/bin' > - found > '/home/sglass/.buildman-toolchains/gcc-9.2.0-nolibc/arc-linux/bin/arc-linux-gcc' > - looking in > '/home/sglass/.buildman-toolchains/gcc-9.2.0-nolibc/arc-linux/usr/bin' > Tool chain test: OK, arch='arc', priority 5 > > $ buildman -A hsdk_4xd > /home/sglass/.buildman-toolchains/gcc-9.2.0-nolibc/arc-linux/bin/arc-linux- > $ buildman hsdk_4xd > ... > arc-linux-gcc: error: unrecognized argument in option '-mcpu=hs4x_rel31 > > > Do you have any thoughts on what is wrong, please? There's two parts. The first part is I keep forgetting to update buildman to fetch the latest toolchains from kernel.org, it should be grabbing 11.1.0 now, not 9.2.0. The second part is that arc, nds32 and xtensa have non-standard toolchain locations, see tools/docker/Dockerfile for where to fetch. -- Tom

2 1

Timer migration to driver model
by Simon Glass 17 Dec '21

17 Dec '21

Hi, I've sent a patch to set a deadline for migration to CONFIG_TIMER, i.e. using driver model for timers. This catches quite a lot of boards, so please take a look. Regards, Simon

1 0