July 2021 - U-Boot

[PATCH u-boot-mvebu] arm: mvebu: armada-3720: remove unused config option
by Marek Behún 09 Jul '21

09 Jul '21

The config option CONFIG_DEBUG_UART_CLOCK is not used by Armada 3720's serial driver (it wasn't even before the recent update of that driver). Remove it. Signed-off-by: Marek Behún <marek.behun(a)nic.cz> Cc: Stefan Roese <sr(a)denx.de> Cc: Pali Rohár <pali(a)kernel.org> --- configs/mvebu_db-88f3720_defconfig | 1 - configs/mvebu_espressobin-88f3720_defconfig | 1 - configs/turris_mox_defconfig | 1 - configs/uDPU_defconfig | 1 - 4 files changed, 4 deletions(-) diff --git a/configs/mvebu_db-88f3720_defconfig b/configs/mvebu_db-88f3720_defconfig index c9935da102..ff4668e837 100644 --- a/configs/mvebu_db-88f3720_defconfig +++ b/configs/mvebu_db-88f3720_defconfig @@ -11,7 +11,6 @@ CONFIG_ENV_SECT_SIZE=0x10000 CONFIG_DM_GPIO=y CONFIG_DEFAULT_DEVICE_TREE="armada-3720-db" CONFIG_DEBUG_UART_BASE=0xd0012000 -CONFIG_DEBUG_UART_CLOCK=25804800 CONFIG_DEBUG_UART=y CONFIG_AHCI=y CONFIG_DISTRO_DEFAULTS=y diff --git a/configs/mvebu_espressobin-88f3720_defconfig b/configs/mvebu_espressobin-88f3720_defconfig index 157a4b7cb2..dc199cfe50 100644 --- a/configs/mvebu_espressobin-88f3720_defconfig +++ b/configs/mvebu_espressobin-88f3720_defconfig @@ -11,7 +11,6 @@ CONFIG_ENV_SECT_SIZE=0x10000 CONFIG_DM_GPIO=y CONFIG_DEFAULT_DEVICE_TREE="armada-3720-espressobin" CONFIG_DEBUG_UART_BASE=0xd0012000 -CONFIG_DEBUG_UART_CLOCK=25804800 CONFIG_DEBUG_UART=y CONFIG_AHCI=y CONFIG_DISTRO_DEFAULTS=y diff --git a/configs/turris_mox_defconfig b/configs/turris_mox_defconfig index 2c6f4938db..b3458acb98 100644 --- a/configs/turris_mox_defconfig +++ b/configs/turris_mox_defconfig @@ -11,7 +11,6 @@ CONFIG_ENV_SECT_SIZE=0x10000 CONFIG_DM_GPIO=y CONFIG_DEFAULT_DEVICE_TREE="armada-3720-turris-mox" CONFIG_DEBUG_UART_BASE=0xd0012000 -CONFIG_DEBUG_UART_CLOCK=25804800 CONFIG_DEBUG_UART=y CONFIG_OF_BOARD_FIXUP=y CONFIG_DISTRO_DEFAULTS=y diff --git a/configs/uDPU_defconfig b/configs/uDPU_defconfig index cdf6b2274c..649248d74d 100644 --- a/configs/uDPU_defconfig +++ b/configs/uDPU_defconfig @@ -10,7 +10,6 @@ CONFIG_ENV_SECT_SIZE=0x10000 CONFIG_DM_GPIO=y CONFIG_DEFAULT_DEVICE_TREE="armada-3720-uDPU" CONFIG_DEBUG_UART_BASE=0xd0012000 -CONFIG_DEBUG_UART_CLOCK=25804800 CONFIG_DEBUG_UART=y CONFIG_AHCI=y CONFIG_DISTRO_DEFAULTS=y -- 2.31.1

2 2

[PATCH] Makefile: add support to build dedicated devicetree
by Kory Maincent 09 Jul '21

09 Jul '21

Add the support to build a dedicated devicetree located in arch/$(ARCH)/dts This devicetree does not need to be listed in the relevant devicetree makefile. Just run the following command to build the foo devicetree placed before at the right path: $ make foo.dtb Signed-off-by: Kory Maincent <kory.maincent(a)bootlin.com> --- Makefile | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Makefile b/Makefile index 027e31e09e..2ebeaee515 100644 --- a/Makefile +++ b/Makefile @@ -1136,6 +1136,12 @@ dtbs: dts/dt.dtb dts/dt.dtb: u-boot $(Q)$(MAKE) $(build)=dts dtbs +ifneq ($(wildcard $(srctree)/arch/$(ARCH)/dts/),) +dtstree := arch/$(ARCH)/dts +%.dtb: u-boot + $(Q)$(MAKE) $(build)=$(dtstree) $(dtstree)/$@ +endif + quiet_cmd_copy = COPY $@ cmd_copy = cp $< $@ -- 2.25.1

1 0

[PATCH v3 00/20] TI/Cadence: Add Sierra/Torrent SERDES driver
by Kishon Vijay Abraham I 09 Jul '21

09 Jul '21

Patch series adds Sierra and Torrent SERDES driver for the SERDES used in TI's K3 platforms. This SERDES is used by USB3, PCIe and Ethernet. This series is mostly an adaptation of drivers added in upstream Linux kernel. Changes from v2: 1) Re-worked "Handle gracefully NULL pointers" to fix Simons comments 2) Ported the part that allows creating clocks without explicit sub-nodes in DT from the upstream linux kernel. Changes from v1: 1) Fixed string comparison strncmp() to remove "==" 2) Added a test for node name comparison to ignore unit address in test/dm 3) Added better commit message in "drivers: reset: Handle gracefully NULL pointers" Alan Douglas (1): phy: cadence: Add driver for Sierra PHY Aswath Govindraju (7): dt-bindings: phy: Add definitions for additional phy types phy: cadence: Add driver for Torrent SERDES board: ti: j721e: Add support for probing and configuring Torrent serdes on J7200 arm: dts: k3-j7200-main: Add DT node for torrent serdes arm: dts: k3-j7200-common-proc-board: Enable SERDES DT arm: dts: k3-j7200-common-proc-board-u-boot: Add u-boot tags for torrent serdes configs: j7200_evm_a72_defconfig: Add config for torrent serdes and common clock framework Jean-Jacques Hiblot (2): phy: ti: j721e-wiz: Add support for WIZ module present in TI J721E SoC configs: j721e_evm_a72: Enable the drivers required for the USB3 support Kishon Vijay Abraham I (10): dm: core: Add helper to compare node names dm: test: Add test case to check node name ignoring unit address drivers: reset: Handle gracefully NULL pointers dt-bindings: phy: Add defines for AM64 SERDES Wrapper dt-bindings: phy: cadence-torrent: Add defines for refclk driver dt-bindings: ti-serdes-mux: Add defines for AM64 SoC usb: cdns3: cdns3-ti: Fix clk_get_by_name() to get the correct name ARM: dts: k3-j721e: Add the entries required for USB3 support on USB0 env: ti: j721e-evm: Add env variable to power on & reset QSGMII PHY in J7200 EVM configs: j7200_evm_a72: Enhance bootcmd to configure ethernet PHY .../k3-j7200-common-proc-board-u-boot.dtsi | 12 + arch/arm/dts/k3-j7200-common-proc-board.dts | 23 + arch/arm/dts/k3-j7200-main.dtsi | 63 + .../k3-j721e-common-proc-board-u-boot.dtsi | 19 +- board/ti/j721e/evm.c | 34 +- configs/j7200_evm_a72_defconfig | 9 +- configs/j721e_evm_a72_defconfig | 6 + drivers/core/ofnode.c | 13 + drivers/phy/Kconfig | 3 + drivers/phy/Makefile | 2 + drivers/phy/cadence/Kconfig | 11 + drivers/phy/cadence/Makefile | 2 + drivers/phy/cadence/phy-cadence-sierra.c | 757 +++++ drivers/phy/cadence/phy-cadence-torrent.c | 2468 +++++++++++++++++ drivers/phy/ti/Kconfig | 9 + drivers/phy/ti/Makefile | 1 + drivers/phy/ti/phy-j721e-wiz.c | 1154 ++++++++ drivers/reset/reset-uclass.c | 35 +- drivers/usb/cdns3/cdns3-ti.c | 2 +- include/configs/j721e_evm.h | 16 +- include/dm/ofnode.h | 10 + include/dt-bindings/mux/ti-serdes.h | 5 + include/dt-bindings/phy/phy-cadence.h | 20 + include/dt-bindings/phy/phy-ti.h | 21 + include/dt-bindings/phy/phy.h | 1 + test/dm/core.c | 14 + 26 files changed, 4700 insertions(+), 10 deletions(-) create mode 100644 drivers/phy/cadence/Kconfig create mode 100644 drivers/phy/cadence/Makefile create mode 100644 drivers/phy/cadence/phy-cadence-sierra.c create mode 100644 drivers/phy/cadence/phy-cadence-torrent.c create mode 100644 drivers/phy/ti/Kconfig create mode 100644 drivers/phy/ti/Makefile create mode 100644 drivers/phy/ti/phy-j721e-wiz.c create mode 100644 include/dt-bindings/phy/phy-cadence.h create mode 100644 include/dt-bindings/phy/phy-ti.h -- 2.17.1

3 35

[PATCH v2 0/6] This patch set fixes minor issues related to tapdelays
by Ashok Reddy Soma 09 Jul '21

09 Jul '21

This patch set fixes below issues in zynq_sdhc driver - Fix issues in tap delay functions where it returns uninitialized values - Allow configuring zero tap delay values - Split tapdelay functions to set input and output tap delay's separately. - Fix kernel doc warnings - Make local structures as static structures Changes in v2: - Changed "@degree" to "@degrees:" in function descriptions of tap delay functions - Removed @degree warning from commit description since it is fixed in patch 1/6. Ashok Reddy Soma (4): mmc: zynq_sdhci: Resolve uninitialized return value mmc: zynq_sdhci: Allow configuring zero Tap values mmc: zynq_sdhci: Use Mask writes for Tap delays mmc: zynq_sdhci: Split set_tapdelay function to in and out Michal Simek (2): mmc: zynq_sdhci: Fix kernel doc warnings mmc: zynq_sdhci: Make variables/structure static board/xilinx/zynqmp/tap_delays.c | 73 ++++++++-------- drivers/mmc/zynq_sdhci.c | 144 ++++++++++++++++--------------- include/zynqmp_tap_delay.h | 7 +- 3 files changed, 115 insertions(+), 109 deletions(-) -- 2.17.1

3 10

[PATCH 0/6] This patch set fixes minor issues related to tapdelays
by Ashok Reddy Soma 09 Jul '21

09 Jul '21

This patch set fixes below issues in zynq_sdhc driver - Fix issues in tap delay functions where it returns uninitialized values - Allow configuring zero tap delay values - Split tapdelay functions to set input and output tap delay's separately. - Fix kernel doc warnings - Make local structures as static structures Ashok Reddy Soma (4): mmc: zynq_sdhci: Resolve uninitialized return value mmc: zynq_sdhci: Allow configuring zero Tap values mmc: zynq_sdhci: Use Mask writes for Tap delays mmc: zynq_sdhci: Split set_tapdelay function to in and out Michal Simek (2): mmc: zynq_sdhci: Fix kernel doc warnings mmc: zynq_sdhci: Make variables/structure static board/xilinx/zynqmp/tap_delays.c | 73 ++++++++-------- drivers/mmc/zynq_sdhci.c | 144 ++++++++++++++++--------------- include/zynqmp_tap_delay.h | 7 +- 3 files changed, 115 insertions(+), 109 deletions(-) -- 2.17.1

3 12

[PATCH 0/4] Add support for eMMC on ST-Ericsson Ux500(v2)
by Stephan Gerhold 09 Jul '21

09 Jul '21

This patch series adds support for the eMMC on ST-Ericsson Ux500: 1. Some minor fixes+cleanup for the arm_pl180_mmci driver. 3. Add the necessary configuration for ST-Ericsson Ux500v2. This was tested on the u8500 "stemmy" board that is already present in U-Boot. Stephan Gerhold (4): mmc: arm_pl180_mmci: Don't bind to all arm,primecell devices mmc: arm_pl180_mmci: Simplify code using dev_read_addr_ptr() mmc: arm_pl180_mmci: Simplify code using mmc_of_parse() mmc: arm_pl180_mmci: Add configuration for ST-Ericsson Ux500v2 drivers/mmc/arm_pl180_mmci.c | 48 ++++++++++++++++-------------------- drivers/mmc/arm_pl180_mmci.h | 1 + 2 files changed, 22 insertions(+), 27 deletions(-) -- 2.32.0

4 13

[PATCH] xilinx: zynq, zynqmp: Return ENVL_NOWHERE instead of ENVL_UNKNOWN
by Mike Looijmans 09 Jul '21

09 Jul '21

The system refuses to boot without any environment, so return ENVL_NOWHERE when there's nowhere to store the environment instead of ENVL_UNKNOWN. This fixes that the board won't boot from eMMC when CONFIG_ENV_IS_IN_FAT is not defined, for example. Similar for other combinations. Fixes: 1025bd098aa8 "xilinx: zynqmp: Add support for saving variables" Signed-off-by: Mike Looijmans <mike.looijmans(a)topic.nl> --- board/xilinx/zynq/board.c | 6 +++--- board/xilinx/zynqmp/zynqmp.c | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/board/xilinx/zynq/board.c b/board/xilinx/zynq/board.c index e2e9b3f0f7..61e0a90c11 100644 --- a/board/xilinx/zynq/board.c +++ b/board/xilinx/zynq/board.c @@ -134,18 +134,18 @@ enum env_location env_get_location(enum env_operation op, int prio) return ENVL_FAT; if (IS_ENABLED(CONFIG_ENV_IS_IN_EXT4)) return ENVL_EXT4; - return ENVL_UNKNOWN; + return ENVL_NOWHERE; case ZYNQ_BM_NAND: if (IS_ENABLED(CONFIG_ENV_IS_IN_NAND)) return ENVL_NAND; if (IS_ENABLED(CONFIG_ENV_IS_IN_UBI)) return ENVL_UBI; - return ENVL_UNKNOWN; + return ENVL_NOWHERE; case ZYNQ_BM_NOR: case ZYNQ_BM_QSPI: if (IS_ENABLED(CONFIG_ENV_IS_IN_SPI_FLASH)) return ENVL_SPI_FLASH; - return ENVL_UNKNOWN; + return ENVL_NOWHERE; case ZYNQ_BM_JTAG: default: return ENVL_NOWHERE; diff --git a/board/xilinx/zynqmp/zynqmp.c b/board/xilinx/zynqmp/zynqmp.c index ee4d0c85e6..a5210035a2 100644 --- a/board/xilinx/zynqmp/zynqmp.c +++ b/board/xilinx/zynqmp/zynqmp.c @@ -710,18 +710,18 @@ enum env_location env_get_location(enum env_operation op, int prio) return ENVL_FAT; if (IS_ENABLED(CONFIG_ENV_IS_IN_EXT4)) return ENVL_EXT4; - return ENVL_UNKNOWN; + return ENVL_NOWHERE; case NAND_MODE: if (IS_ENABLED(CONFIG_ENV_IS_IN_NAND)) return ENVL_NAND; if (IS_ENABLED(CONFIG_ENV_IS_IN_UBI)) return ENVL_UBI; - return ENVL_UNKNOWN; + return ENVL_NOWHERE; case QSPI_MODE_24BIT: case QSPI_MODE_32BIT: if (IS_ENABLED(CONFIG_ENV_IS_IN_SPI_FLASH)) return ENVL_SPI_FLASH; - return ENVL_UNKNOWN; + return ENVL_NOWHERE; case JTAG_MODE: default: return ENVL_NOWHERE; -- 2.17.1

2 1

Illegal instruction - While starting Linux kernel.
by Venkatakrishnan Sutharsan 09 Jul '21

09 Jul '21

Hi, I have been writing SPI Driver in U-Boot for a RISCV Board and is currently trying to use that to boot linux kernel from SD Card. Right now, I have the card detected and can view files in various partitions in the SD Card. After that I try to copy the uImage (created using mkimage command and vmlinux image file) and dtb into the memory and start the kernel using the following command (the kernel encounters illegal instruction and terminates): => ext4load mmc 0:1 ${kernel_addr_r} /boot/uImage; ext4load mmc 0:1 ${fdt_addr_r} /boot/shakti_100t.dtb; bootm ${kernel_addr_r} - ${fdt_addr_r} 16131968 bytes read in 1227747 ms (12.7 KiB/s) 2852 bytes read in 504 ms (4.9 KiB/s) ## Booting kernel from Legacy Image at 84000000 ... Image Name: Shakti-Vajra Image Type: RISC-V Linux Kernel Image (uncompressed) Data Size: 16131904 Bytes = 15.4 MiB Load Address: 84000000 Entry Point: 84000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Kernel Image Using Device Tree in place at 0000000088000000, end 0000000088003b23 Starting kernel ... Unhandled exception: Illegal instruction EPC: 0000000084000000 RA: 000000008ff9905c TVAL: 00000000464c457f EPC: 0000000074268000 RA: 000000008020105c reloc adjusted resetting ... reset not supported yet ### ERROR ### Please RESET the board ### And to check the dump I was not able to create the dump using riscv64-unknown-elf-objdump command in my computer so I used the md.b command to get the dump from the RAM in the board. The dump were as follows : 84000000: 27 05 19 56 02 e3 5d 33 60 e2 a7 a5 00 f6 27 40 '..V..]3`.....'@ 84000010: 84 00 00 00 84 00 00 00 ee 5e 8f 20 05 1a 02 00 .........^. .... 84000020: 53 68 61 6b 74 69 2d 56 61 6a 72 61 00 00 00 00 Shakti-Vajra.... 84000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000040: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 .ELF............ 84000050: 02 00 f3 00 01 00 00 00 00 00 00 00 e0 ff ff ff ................ 84000060: 40 00 00 00 00 00 00 00 00 22 f6 00 00 00 00 00 @........"...... 84000070: 00 00 00 00 40 00 38 00 04 00 40 00 15 00 14 00 ....@.8...@..... 84000080: 01 00 00 00 05 00 00 00 00 10 00 00 00 00 00 00 ................ 84000090: 00 00 00 00 e0 ff ff ff 00 00 00 00 00 00 00 00 ................ 840000a0: f4 ab 01 00 00 00 00 00 f4 ab 01 00 00 00 00 00 ................ 840000b0: 00 10 00 00 00 00 00 00 01 00 00 00 07 00 00 00 ................ 840000c0: 00 c0 01 00 00 00 00 00 00 b0 01 00 e0 ff ff ff ................ 840000d0: 00 b0 01 00 00 00 00 00 c0 a4 e6 00 00 00 00 00 ................ 840000e0: c0 a4 e6 00 00 00 00 00 00 10 00 00 00 00 00 00 ................ 840000f0: 04 00 00 00 04 00 00 00 c0 78 e1 00 00 00 00 00 .........x...... 84000100: c0 68 e1 00 e0 ff ff ff c0 68 e1 00 00 00 00 00 .h.......h...... 84000110: 3c 00 00 00 00 00 00 00 3c 00 00 00 00 00 00 00 <.......<....... 84000120: 04 00 00 00 00 00 00 00 51 e5 74 64 06 00 00 00 ........Q.td.... 84000130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000150: 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00 ................ 84000160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 840001a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 840001b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 840001c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 840001d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 840001e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 840001f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000230: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000250: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 84000260: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ while the FDT loading seems to happen correctly as below. There is a huge number of zeros in the above dump after which there is some data(after 0x84001078). I can also say that what I see in my hex editor in my computer can be seen in md.b dump in the RAM which conveys the working of the SPI Driver. => md.b ${fdt_addr_r} 88000000: d0 0d fe ed 00 00 0b 24 00 00 00 38 00 00 08 54 .......$...8...T 88000010: 00 00 00 28 00 00 00 11 00 00 00 10 00 00 00 00 ...(............ 88000020: 00 00 02 d0 00 00 08 1c 00 00 00 00 00 00 00 00 ................ 88000030: 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 ................ 88000040: 00 00 00 03 00 00 00 04 00 00 00 00 00 00 00 02 ................ 88000050: 00 00 00 03 00 00 00 04 00 00 00 0f 00 00 00 02 ................ 88000060: 00 00 00 03 00 00 00 16 00 00 00 1b 73 68 61 6b ............shak 88000070: 74 69 2c 73 70 69 6b 65 2d 62 61 72 65 2d 64 65 ti,spike-bare-de 88000080: 76 00 00 00 00 00 00 03 00 00 00 12 00 00 00 26 v..............& 88000090: 73 68 61 6b 74 69 2c 73 70 69 6b 65 2d 62 61 72 shakti,spike-bar 880000a0: 65 00 00 00 00 00 00 01 63 70 75 73 00 00 00 00 e.......cpus.... 880000b0: 00 00 00 03 00 00 00 04 00 00 00 00 00 00 00 01 ................ 880000c0: 00 00 00 03 00 00 00 04 00 00 00 0f 00 00 00 00 ................ 880000d0: 00 00 00 03 00 00 00 04 00 00 00 2c 00 00 80 00 ...........,.... 880000e0: 00 00 00 01 63 70 75 40 30 00 00 00 00 00 00 03 ....cpu@0....... 880000f0: 00 00 00 04 00 00 00 3f 63 70 75 00 00 00 00 03 .......?cpu..... 88000100: 00 00 00 04 00 00 00 4b 00 00 00 00 00 00 00 03 .......K........ 88000110: 00 00 00 05 00 00 00 4f 6f 6b 61 79 00 00 00 00 .......Ookay.... 88000120: 00 00 00 03 00 00 00 06 00 00 00 1b 72 69 73 63 ............risc 88000130: 76 00 00 00 00 00 00 03 00 00 00 09 00 00 00 56 v..............V 88000140: 72 76 36 34 69 6d 61 63 00 00 00 00 00 00 00 03 rv64imac........ 88000150: 00 00 00 0b 00 00 00 60 72 69 73 63 76 2c 73 76 .......`riscv,sv 88000160: 33 39 00 00 00 00 00 03 00 00 00 04 00 00 00 69 39.............i 88000170: 02 fa f0 80 00 00 00 01 69 6e 74 65 72 72 75 70 ........interrup 88000180: 74 2d 63 6f 6e 74 72 6f 6c 6c 65 72 00 00 00 00 t-controller.... 88000190: 00 00 00 03 00 00 00 04 00 00 00 79 00 00 00 01 ...........y.... 880001a0: 00 00 00 03 00 00 00 00 00 00 00 8a 00 00 00 03 ................ 880001b0: 00 00 00 0f 00 00 00 1b 72 69 73 63 76 2c 63 70 ........riscv,cp 880001c0: 75 2d 69 6e 74 63 00 00 00 00 00 03 00 00 00 04 u-intc.......... 880001d0: 00 00 00 9f 00 00 00 01 00 00 00 02 00 00 00 02 ................ 880001e0: 00 00 00 02 00 00 00 01 6d 65 6d 6f 72 79 40 38 ........memory@8 880001f0: 30 30 30 30 30 30 30 00 00 00 00 03 00 00 00 07 0000000......... Also, I printed the FDT using the fdt print command. => load mmc 0:1 ${fdt_addr_r} /boot/shakti_100t.dtb 2852 bytes read in 519 ms (4.9 KiB/s) => fdt print No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! => fdt addr ${fdt_addr_r} => fdt print / { #address-cells = <0x00000002>; #size-cells = <0x00000002>; compatible = "shakti,spike-bare-dev"; model = "shakti,spike-bare"; cpus { #address-cells = <0x00000001>; #size-cells = <0x00000000>; timebase-frequency = <0x00008000>; cpu@0 { device_type = "cpu"; reg = <0x00000000>; status = "okay"; compatible = "riscv"; riscv,isa = "rv64imac"; mmu-type = "riscv,sv39"; clock-frequency = <0x02faf080>; interrupt-controller { #interrupt-cells = <0x00000001>; interrupt-controller; compatible = "riscv,cpu-intc"; phandle = <0x00000001>; }; }; }; memory@80000000 { device_type = "memory"; reg = <0x00000000 0x80000000 0x00000000 0x10000000>; }; soc { #address-cells = <0x00000002>; #size-cells = <0x00000002>; compatible = "shakti,spike-bare-soc", "simple-bus"; ranges; clint@2000000 { compatible = "riscv,clint0"; interrupts-extended = <0x00000001 0x00000003 0x00000001 0x00000007>; reg = <0x00000000 0x02000000 0x00000000 0x000c0000>; }; interrupt-controller@c000000 { #interrupt-cells = <0x00000002>; compatible = "riscv,plic0"; interrupt-controller; reg = <0x00000000 0x0c000000 0x00000000 0x04000000>; interrupts-extended = <0x00000001 0x0000000b 0x00000001 0x00000009>; reg-names = "control"; riscv,max-priority = <0x00000007>; riscv,ndev = <0x0000001d>; phandle = <0x00000002>; }; ethernet@44000 { #address-cells = <0x00000002>; #size-cells = <0x00000002>; device_type = "network"; compatible = "xlnx,xps-ethernetlite-3.00.a", "xlnx,xps-ethernetlite-1.00.a"; interrupt-parent = <0x00000002>; interrupts = <0x0000001d 0x00000001>; local-mac-address = [00 0a 35 00 00 00]; phy-handle = <0x00000003>; reg = <0x00000000 0x00044000 0x00000000 0x00004000>; xlnx,duplex = <0x00000001>; xlnx,include-global-buffers = <0x00000001>; xlnx,include-internal-loopback = <0x00000001>; xlnx,include-mdio = <0x00000001>; xlnx,instance = "axi_ethernetlite_inst"; xlnx,rx-ping-pong = <0x00000001>; xlnx,s-axi-id-width = <0x00000001>; xlnx,tx-ping-pong = <0x00000001>; threshold = <0x00000040>; sensitivity = <0x00000006>; mdio { #address-cells = <0x00000001>; #size-cells = <0x00000000>; phy@1 { device_type = "ethernet-phy"; compatible = "ethernet-phy-ieee802.3-c22"; ti,rx-internal-delay = <0x3b9aca00>; ti,tx-internal-delay = <0x3b9aca00>; ti,fifo-depth = <0x00001000>; reg = <0x00000001>; status = "okay"; phandle = <0x00000003>; }; }; }; oscillator { #clock-cells = <0x00000000>; compatible = "fixed-clock"; clock-frequency = <0x02faf080>; phandle = <0x00000004>; }; spi@20100 { compatible = "shakti,spi1"; reg = <0x00000000 0x00020100 0x00000000 0x00000100>; clocks = <0x00000004>; shakti,controller = <0x00000001>; shakti,spi-frequency = <0x001e8480>; shakti,lsb-first = <0x00000000>; shakti,communication-mode = <0x00000003>; shakti,cpha = <0x00000000>; shakti,cpol = <0x00000000>; shakti,cs-high = <0x00000001>; shakti,fifo-depth = <0x0000001f>; mmc-slot@0 { compatible = "mmc-spi-slot"; reg = <0x00000000>; voltage-ranges = <0x00000ce4 0x00000ce4>; spi-max-frequency = <0x002625a0>; }; }; }; uart { compatible = "shakti,uart0"; reg = <0x00000000 0x00011300 0x00000000 0x00001000>; }; }; >From this I think that the SPI Driver is working, but I still cannot figure why the kernel is not booting. Any suggestions/comments on how to solve this issue is highly appreciated. Thanks in advance. *Regards,* *Venkatakrishnan Sutharsan*

1 0

[PATCH] octeontx: do not require cavium BDK node to be present
by Tim Harvey 09 Jul '21

09 Jul '21

The cavium,bdk node is a non-standard dt node used by the BDK and therefore it is removed from the dt before booting Linux. Do not require this node to exist as it won't for standard dt's. Signed-off-by: Tim Harvey <tharvey(a)gateworks.com> --- board/Marvell/octeontx/board-fdt.c | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/board/Marvell/octeontx/board-fdt.c b/board/Marvell/octeontx/board-fdt.c index 0b05ef11e9..1db2a4a267 100644 --- a/board/Marvell/octeontx/board-fdt.c +++ b/board/Marvell/octeontx/board-fdt.c @@ -281,20 +281,16 @@ int ft_board_setup(void *blob, struct bd_info *bd) } if (blob) { + /* delete cavium,bdk node if it exists */ offset = fdt_path_offset(blob, "/cavium,bdk"); - if (offset < 0) { - printf("ERROR: FDT BDK node not found\n"); - return offset; - } - - /* delete node */ - ret = fdt_del_node(blob, offset); - if (ret < 0) { - printf("WARNING : could not remove bdk node\n"); - return ret; + if (offset >= 0) { + ret = fdt_del_node(blob, offset); + if (ret < 0) { + printf("WARNING : could not remove bdk node\n"); + return ret; + } + debug("%s deleted bdk node\n", __func__); } - - debug("%s deleted bdk node\n", __func__); } return 0; -- 2.17.1

2 2

[PATCH u-boot-marvell 0/5] Support higher baudrates on Armada 3720 UART
by Marek Behún 09 Jul '21

09 Jul '21

This series adds support for more baudrates on Armada 3720 UART (up to 6 MBaud). Marek Behún (1): clk: armada-37xx: Set DM_FLAG_PRE_RELOC Pali Rohár (4): serial: a37xx: Fix parent clock rate value and divider calculation serial: a37xx: Use TBG as parent clock serial: a37xx: Switch to XTAL clock when booting Linux kernel arm: mvebu: a37xx: Enable more baudrates drivers/clk/mvebu/armada-37xx-periph.c | 1 + drivers/clk/mvebu/armada-37xx-tbg.c | 1 + drivers/serial/serial_mvebu_a3700.c | 179 ++++++++++++++++++++++++- include/configs/mvebu_armada-37xx.h | 9 +- include/configs/turris_mox.h | 9 +- 5 files changed, 190 insertions(+), 9 deletions(-) -- 2.26.3

3 13