January 2025 - U-Boot

[PATCH v3 0/6] Enable QCOM QCS9100 Ride platform support
by Varadarajan Narayanan 22 Jan '25

22 Jan '25

The following patch series enables support for QCOM QCS9100 based Ride platform. The QCS9100 SoC is a derivative of SA8775p and hence this series makes use of the SA8775p related code to enable the QCS9100 based Ride platform support. Use 'make qcs9100_defconfig' to generate '.config'. --- v3: * Added reviewed-by to dts cherry pick patch * Removed duplicates from configs/qcs9100_defconfig v2: * Added reviewed-by tags to some of the patches * Add separate patch to bring QCS9100 DT files from Linux * Dropped 'arch/arm/dts/sa8775p-*.dtsi' from first patch and use qcs9100 DT files instead * Added one more range to memory definition * Updated commit log to include linux version from where headers were taken --- Tengfei Fan (1): arm64: dts: qcom: qcs9100: Add support for the QCS9100 Ride and Ride Rev3 boards Varadarajan Narayanan (5): dts: qcs9100-ride-r3-u-boot: add override dtsi clk/qcom: add initial clock driver for qcs9100 phy: qcom: Add SA8775 to QMP UFS PHY driver qcom_defconfig: enable SA8775P clock driver configs: add qcs9100_defconfig arch/arm/dts/qcs9100-ride-r3-u-boot.dtsi | 20 ++ configs/qcom_defconfig | 1 + configs/qcs9100_defconfig | 18 ++ drivers/clk/qcom/Kconfig | 8 + drivers/clk/qcom/Makefile | 1 + drivers/clk/qcom/clock-sa8775p.c | 142 +++++++++++ .../phy/qcom/phy-qcom-qmp-qserdes-com-v5.h | 124 ++++++++++ .../phy/qcom/phy-qcom-qmp-qserdes-txrx-v5.h | 231 ++++++++++++++++++ drivers/phy/qcom/phy-qcom-qmp-ufs.c | 171 +++++++++++++ .../src/arm64/qcom/qcs9100-ride-r3.dts | 11 + dts/upstream/src/arm64/qcom/qcs9100-ride.dts | 11 + 11 files changed, 738 insertions(+) create mode 100644 arch/arm/dts/qcs9100-ride-r3-u-boot.dtsi create mode 100644 configs/qcs9100_defconfig create mode 100644 drivers/clk/qcom/clock-sa8775p.c create mode 100644 drivers/phy/qcom/phy-qcom-qmp-qserdes-com-v5.h create mode 100644 drivers/phy/qcom/phy-qcom-qmp-qserdes-txrx-v5.h create mode 100644 dts/upstream/src/arm64/qcom/qcs9100-ride-r3.dts create mode 100644 dts/upstream/src/arm64/qcom/qcs9100-ride.dts base-commit: 38a371110308ebeb277e20531a7b698b7981bbfa -- 2.34.1

3 9

[PATCH] spi: cadence_qspi: Add missing prototype for cadence_qspi_flash_reset
by Venkatesh Yadav Abbarapu 22 Jan '25

22 Jan '25

Add missing prototype to fix the sparse warning, warning: no previous prototype for 'cadence_qspi_flash_reset' [-Wmissing-prototypes]. Fixes: 6d234a79e9 ("cadence_qspi: Refactor the flash reset functionality") Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu(a)amd.com> --- drivers/spi/cadence_qspi.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/cadence_qspi.h b/drivers/spi/cadence_qspi.h index 693474a2871..1f9125cd239 100644 --- a/drivers/spi/cadence_qspi.h +++ b/drivers/spi/cadence_qspi.h @@ -307,7 +307,7 @@ int cadence_qspi_apb_dma_read(struct cadence_spi_priv *priv, const struct spi_mem_op *op); int cadence_qspi_apb_wait_for_dma_cmplt(struct cadence_spi_priv *priv); int cadence_qspi_apb_exec_flash_cmd(void *reg_base, unsigned int reg); -int cadence_qspi_versal_flash_reset(struct udevice *dev); +int cadence_qspi_flash_reset(struct udevice *dev); ofnode cadence_qspi_get_subnode(struct udevice *dev); void cadence_qspi_apb_enable_linear_mode(bool enable); -- 2.34.1

2 1

[PATCH v4] image: apply FDTOs on FDT image node without a load property
by Quentin Schulz 22 Jan '25

22 Jan '25

From: Quentin Schulz <quentin.schulz(a)cherry.de> A FIT image which is NOT using -E when created by mkimage - that is with image data within the FIT - will fail to apply FDTO if the base FDT image node does not specify a load property (which points to an address in DRAM). This is because we check that the FDT address we want to apply overlay to (i.e. modify and likely increase in size) is not inside the FIT and give up otherwise. This is assumed necessary because we may then overwrite other data when applying in-place. However, we can do better than giving up: relocating the FDT in another place in DRAM where it's safe to increase its size and apply FDTOs. While at it, do not discriminate anymore on whether the data is within the FIT data address space - that is FIT images created with mkimage -E - as that still may be susceptible to unintended data overwrites as mkimage -E simply concatenates all blobs after the FIT. If the FDT blob isn't the last, it'll result in overwriting later blobs when resizing. The side effect is that the load property in the FIT is only temporarily used to load the FDT but then relocated right before we start applying overlays. Suggested-by: Marek Vasut <marex(a)denx.de> Reviewed-by: Marek Vasut <marex(a)denx.de> Signed-off-by: Quentin Schulz <quentin.schulz(a)cherry.de> --- This actually forces the base FDT to always be relocated whenever FDTO are expected to be applied, regardless of the presence of the load property in the base FDT image node. Tested with extlinux with: - conf node with multiple fdt entries (scenario A) - conf node with base fdt + conf node with fdto (stored in fdt property) (scenario B) - conf node with multiple fdt entries with base fdt with load property (scenario C) - conf node with base fdt + conf node with fdto (stored in fdt property) with base fdt with load property (scenario D) """fit.its /dts-v1/; / { description = "Kernel fitImage for Jaguar"; #address-cells = <1>; images { kernel-1 { description = "Linux kernel"; data = /incbin/("arch/arm64/boot/Image.gz"); type = "kernel"; arch = "arm64"; os = "linux"; compression = "gzip"; load = <0x06000000>; entry = <0x06000000>; hash-1 { algo = "sha256"; }; }; fdt-rk3588-jaguar.dtb { description = "Flattened Device Tree blob"; data = /incbin/("arch/arm64/boot/dts/rockchip/rk3588-jaguar.dtb"); type = "flat_dt"; arch = "arm64"; compression = "none"; hash-1 { algo = "sha256"; }; }; fdt-rk3588-jaguar.dtb-load { description = "Flattened Device Tree blob"; data = /incbin/("arch/arm64/boot/dts/rockchip/rk3588-jaguar.dtb"); type = "flat_dt"; arch = "arm64"; compression = "none"; load = <0x12000000>; hash-1 { algo = "sha256"; }; }; fdt-rk3588-jaguar-pre-ict-tester.dtbo { description = "Flattened Device Tree blob"; data = /incbin/("arch/arm64/boot/dts/rockchip/rk3588-jaguar-pre-ict-tester.dtbo"); type = "flat_dt"; arch = "arm64"; compression = "none"; hash-1 { algo = "sha256"; }; }; }; configurations { default = "conf-rk3588-jaguar.dtb"; conf-rk3588-jaguar.dtb { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar.dtb-and-dtbo { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb", "fdt-rk3588-jaguar-pre-ict-tester.dtbo"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar.dtb-load { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb-load"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar.dtb-load-and-dtbo { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb-load", "fdt-rk3588-jaguar-pre-ict-tester.dtbo"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar-pre-ict-tester.dtbo { description = "0 FDT blob"; fdt = "fdt-rk3588-jaguar-pre-ict-tester.dtbo"; hash-1 { algo = "sha256"; }; }; }; }; """ """extlinux.conf (scenario A) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb-and-dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b50370 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ """extlinux.conf (scenario B) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb-load-and-dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb-load-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb-load-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb-load' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b79784 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Load Address: 0x12000000 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading fdt from 0x02b79784 to 0x12000000 Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ """extlinux.conf (scenario C) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb#conf-rk3588-jaguar-pre-ict-tester.dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b50370 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Using 'conf-rk3588-jaguar-pre-ict-tester.dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ """extlinux.conf (scenario D) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb-load#conf-rk3588-jaguar-pre-ict-tester.dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb-load' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb-load' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb-load' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b79784 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Load Address: 0x12000000 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading fdt from 0x02b79784 to 0x12000000 Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Using 'conf-rk3588-jaguar-pre-ict-tester.dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ Cc: Heiko Stuebner <heiko(a)sntech.de> --- Changes in v4: - of_flat_tree type changed to char* from void*, as v3 wouldn't compile, - add comment explaining why char * for of_flat_tree - Link to v3: https://lore.kernel.org/r/20250122-extlinux-relocate-dtb-when-dtbo-v3-1-46b… Changes in v3: - of_flat_tree type changed from char* to void*, - added Marek's Rb trailer, - Link to v2: https://lore.kernel.org/r/20250116-extlinux-relocate-dtb-when-dtbo-v2-1-d01… Changes in v2: - Indiscriminately relocate, regardless of location of FDT to be on the safe side wrt data overlap/overwrite, - print return value of boot_relocate_fdt when it fails, - Link to v1: https://lore.kernel.org/r/20241219-extlinux-relocate-dtb-when-dtbo-v1-1-fe5… --- boot/image-fit.c | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/boot/image-fit.c b/boot/image-fit.c index db7fb61bca948e42a4136b9ceb263a53362ad3f8..8ebe54fd663fc4cf09a0f744160b63554c787ff4 100644 --- a/boot/image-fit.c +++ b/boot/image-fit.c @@ -2348,10 +2348,17 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr, char *next_config = NULL; ulong load, len; #ifdef CONFIG_OF_LIBFDT_OVERLAY - ulong image_start, image_end; ulong ovload, ovlen, ovcopylen; const char *uconfig; const char *uname; + /* + * of_flat_tree is storing the void * returned by map_sysmem, then its + * address is passed to boot_relocate_fdt which expects a char ** and it + * is then cast into a ulong. Setting its type to void * would require + * to cast its address to char ** when passing it to boot_relocate_fdt. + * Instead, let's be lazy and use void *. + */ + char *of_flat_tree; void *base, *ov, *ovcopy = NULL; int i, err, noffset, ov_noffset; #endif @@ -2395,17 +2402,18 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr, /* we need to apply overlays */ #ifdef CONFIG_OF_LIBFDT_OVERLAY - image_start = addr; - image_end = addr + fit_get_size(fit); - /* verify that relocation took place by load address not being in fit */ - if (load >= image_start && load < image_end) { - /* check is simplified; fit load checks for overlaps */ - printf("Overlayed FDT requires relocation\n"); + /* Relocate FDT so resizing does not overwrite other data in FIT. */ + of_flat_tree = map_sysmem(load, len); + len = ALIGN(fdt_totalsize(load), SZ_4K); + err = boot_relocate_fdt(&of_flat_tree, &len); + if (err) { + printf("Required FDT relocation for applying DTOs failed: %d\n", + err); fdt_noffset = -EBADF; goto out; } - base = map_sysmem(load, len); + load = (ulong)of_flat_tree; /* apply extra configs in FIT first, followed by args */ for (i = 1; ; i++) { --- base-commit: 82d262ae162d859d3b0bbcd40a9464e890b009da change-id: 20241219-extlinux-relocate-dtb-when-dtbo-4c7536f880b2 Best regards, -- Quentin Schulz <quentin.schulz(a)cherry.de>

1 0

[PATCH v3] image: apply FDTOs on FDT image node without a load property
by Quentin Schulz 22 Jan '25

22 Jan '25

From: Quentin Schulz <quentin.schulz(a)cherry.de> A FIT image which is NOT using -E when created by mkimage - that is with image data within the FIT - will fail to apply FDTO if the base FDT image node does not specify a load property (which points to an address in DRAM). This is because we check that the FDT address we want to apply overlay to (i.e. modify and likely increase in size) is not inside the FIT and give up otherwise. This is assumed necessary because we may then overwrite other data when applying in-place. However, we can do better than giving up: relocating the FDT in another place in DRAM where it's safe to increase its size and apply FDTOs. While at it, do not discriminate anymore on whether the data is within the FIT data address space - that is FIT images created with mkimage -E - as that still may be susceptible to unintended data overwrites as mkimage -E simply concatenates all blobs after the FIT. If the FDT blob isn't the last, it'll result in overwriting later blobs when resizing. The side effect is that the load property in the FIT is only temporarily used to load the FDT but then relocated right before we start applying overlays. Suggested-by: Marek Vasut <marex(a)denx.de> Reviewed-by: Marek Vasut <marex(a)denx.de> Signed-off-by: Quentin Schulz <quentin.schulz(a)cherry.de> --- This actually forces the base FDT to always be relocated whenever FDTO are expected to be applied, regardless of the presence of the load property in the base FDT image node. Tested with extlinux with: - conf node with multiple fdt entries (scenario A) - conf node with base fdt + conf node with fdto (stored in fdt property) (scenario B) - conf node with multiple fdt entries with base fdt with load property (scenario C) - conf node with base fdt + conf node with fdto (stored in fdt property) with base fdt with load property (scenario D) """fit.its /dts-v1/; / { description = "Kernel fitImage for Jaguar"; #address-cells = <1>; images { kernel-1 { description = "Linux kernel"; data = /incbin/("arch/arm64/boot/Image.gz"); type = "kernel"; arch = "arm64"; os = "linux"; compression = "gzip"; load = <0x06000000>; entry = <0x06000000>; hash-1 { algo = "sha256"; }; }; fdt-rk3588-jaguar.dtb { description = "Flattened Device Tree blob"; data = /incbin/("arch/arm64/boot/dts/rockchip/rk3588-jaguar.dtb"); type = "flat_dt"; arch = "arm64"; compression = "none"; hash-1 { algo = "sha256"; }; }; fdt-rk3588-jaguar.dtb-load { description = "Flattened Device Tree blob"; data = /incbin/("arch/arm64/boot/dts/rockchip/rk3588-jaguar.dtb"); type = "flat_dt"; arch = "arm64"; compression = "none"; load = <0x12000000>; hash-1 { algo = "sha256"; }; }; fdt-rk3588-jaguar-pre-ict-tester.dtbo { description = "Flattened Device Tree blob"; data = /incbin/("arch/arm64/boot/dts/rockchip/rk3588-jaguar-pre-ict-tester.dtbo"); type = "flat_dt"; arch = "arm64"; compression = "none"; hash-1 { algo = "sha256"; }; }; }; configurations { default = "conf-rk3588-jaguar.dtb"; conf-rk3588-jaguar.dtb { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar.dtb-and-dtbo { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb", "fdt-rk3588-jaguar-pre-ict-tester.dtbo"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar.dtb-load { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb-load"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar.dtb-load-and-dtbo { description = "1 Linux kernel, FDT blob"; kernel = "kernel-1"; fdt = "fdt-rk3588-jaguar.dtb-load", "fdt-rk3588-jaguar-pre-ict-tester.dtbo"; hash-1 { algo = "sha256"; }; }; conf-rk3588-jaguar-pre-ict-tester.dtbo { description = "0 FDT blob"; fdt = "fdt-rk3588-jaguar-pre-ict-tester.dtbo"; hash-1 { algo = "sha256"; }; }; }; }; """ """extlinux.conf (scenario A) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb-and-dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b50370 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ """extlinux.conf (scenario B) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb-load-and-dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb-load-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb-load-and-dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb-load' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b79784 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Load Address: 0x12000000 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading fdt from 0x02b79784 to 0x12000000 Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ """extlinux.conf (scenario C) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb#conf-rk3588-jaguar-pre-ict-tester.dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b50370 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Using 'conf-rk3588-jaguar-pre-ict-tester.dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ """extlinux.conf (scenario D) LABEL rk3588-jaguar LINUX /boot/fit#conf-rk3588-jaguar.dtb-load#conf-rk3588-jaguar-pre-ict-tester.dtbo APPEND root=PARTLABEL=debos-rootfs rw rootwait net.ifnames=0 """ Log: """ Using 'conf-rk3588-jaguar.dtb-load' configuration Verifying Hash Integrity ... OK Trying 'kernel-1' kernel subimage Description: Linux kernel Type: Kernel Image Compression: gzip compressed Data Start: 0x020000cc Data Size: 11862415 Bytes = 11.3 MiB Architecture: AArch64 OS: Linux Load Address: 0x06000000 Entry Point: 0x06000000 Hash algo: sha256 Hash value: 51a2b828aec49d9ede09a2de2cd05226def258dedcc8e4c4098fa2ba38fb9690 Verifying Hash Integrity ... sha256+ OK Using 'conf-rk3588-jaguar.dtb-load' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar.dtb-load' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02b79784 Data Size: 168750 Bytes = 164.8 KiB Architecture: AArch64 Load Address: 0x12000000 Hash algo: sha256 Hash value: 96213ce3930a5f926b27c90671ca779fc327e2e62c2135f7ed7d8b6dd659b973 Verifying Hash Integrity ... sha256+ OK Loading fdt from 0x02b79784 to 0x12000000 Loading Device Tree to 00000000ece9d000, end 00000000ecec9fff ... OK Working FDT set to ece9d000 Using 'conf-rk3588-jaguar-pre-ict-tester.dtbo' configuration Verifying Hash Integrity ... OK Trying 'fdt-rk3588-jaguar-pre-ict-tester.dtbo' fdt subimage Description: Flattened Device Tree blob Type: Flat Device Tree Compression: uncompressed Data Start: 0x02ba2bb4 Data Size: 2753 Bytes = 2.7 KiB Architecture: AArch64 Hash algo: sha256 Hash value: e5eb1fe225d03b04e9bb27c04fe3278f294b48c6ab6757292c9650f6d3ce9f34 Verifying Hash Integrity ... sha256+ OK Booting using the fdt blob at 0xece9d000 Working FDT set to ece9d000 Uncompressing Kernel Image to 6000000 Loading Device Tree to 00000000ece70000, end 00000000ece9c62d ... OK Working FDT set to ece70000 """ Cc: Heiko Stuebner <heiko(a)sntech.de> --- Changes in v3: - of_flat_tree type changed from char* to void*, - added Marek's Rb trailer, - Link to v2: https://lore.kernel.org/r/20250116-extlinux-relocate-dtb-when-dtbo-v2-1-d01… Changes in v2: - Indiscriminately relocate, regardless of location of FDT to be on the safe side wrt data overlap/overwrite, - print return value of boot_relocate_fdt when it fails, - Link to v1: https://lore.kernel.org/r/20241219-extlinux-relocate-dtb-when-dtbo-v1-1-fe5… --- boot/image-fit.c | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/boot/image-fit.c b/boot/image-fit.c index db7fb61bca948e42a4136b9ceb263a53362ad3f8..5dd896d019a70742510dbf2a9987b0b6948181ea 100644 --- a/boot/image-fit.c +++ b/boot/image-fit.c @@ -2348,10 +2348,10 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr, char *next_config = NULL; ulong load, len; #ifdef CONFIG_OF_LIBFDT_OVERLAY - ulong image_start, image_end; ulong ovload, ovlen, ovcopylen; const char *uconfig; const char *uname; + void *of_flat_tree; void *base, *ov, *ovcopy = NULL; int i, err, noffset, ov_noffset; #endif @@ -2395,17 +2395,18 @@ int boot_get_fdt_fit(struct bootm_headers *images, ulong addr, /* we need to apply overlays */ #ifdef CONFIG_OF_LIBFDT_OVERLAY - image_start = addr; - image_end = addr + fit_get_size(fit); - /* verify that relocation took place by load address not being in fit */ - if (load >= image_start && load < image_end) { - /* check is simplified; fit load checks for overlaps */ - printf("Overlayed FDT requires relocation\n"); + /* Relocate FDT so resizing does not overwrite other data in FIT. */ + of_flat_tree = map_sysmem(load, len); + len = ALIGN(fdt_totalsize(load), SZ_4K); + err = boot_relocate_fdt(&of_flat_tree, &len); + if (err) { + printf("Required FDT relocation for applying DTOs failed: %d\n", + err); fdt_noffset = -EBADF; goto out; } - base = map_sysmem(load, len); + load = (ulong)of_flat_tree; /* apply extra configs in FIT first, followed by args */ for (i = 1; ; i++) { --- base-commit: 82d262ae162d859d3b0bbcd40a9464e890b009da change-id: 20241219-extlinux-relocate-dtb-when-dtbo-4c7536f880b2 Best regards, -- Quentin Schulz <quentin.schulz(a)cherry.de>

3 4

[PATCH v2 1/2] cyclic: Fix rollover every 72 min on 32 bits platforms
by Patrice Chotard 22 Jan '25

22 Jan '25

On 32 bits platforms, timer_get_us() returns an unsigned long which is a 32 bits. timer_get_us() wraps around every 72 minutes (2 ^ 32 / 1000000 =~ 4295 sec =~ 72 min). So the test "if time_after_eq64(now, cyclic->next_call)" is no more true when cyclic->next_call becomes above 32 bits max value (4294967295). At this point after 72 min, no more cyclic function are executed included watchdog one. Instead of using timer_get_us(), use get_timer_us() which returns a uint64_t, this allows a rollover every 584942 years. Signed-off-by: Patrice Chotard <patrice.chotard(a)foss.st.com> --- Changes in v2: _ Replace remaining timer_get_us() by get_timer_us(0) common/cyclic.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/common/cyclic.c b/common/cyclic.c index 196797fd61e..fad071a39c6 100644 --- a/common/cyclic.c +++ b/common/cyclic.c @@ -36,7 +36,7 @@ void cyclic_register(struct cyclic_info *cyclic, cyclic_func_t func, cyclic->func = func; cyclic->name = name; cyclic->delay_us = delay_us; - cyclic->start_time_us = timer_get_us(); + cyclic->start_time_us = get_timer_us(0); hlist_add_head(&cyclic->list, cyclic_get_list()); } @@ -61,13 +61,13 @@ static void cyclic_run(void) * Check if this cyclic function needs to get called, e.g. * do not call the cyclic func too often */ - now = timer_get_us(); + now = get_timer_us(0); if (time_after_eq64(now, cyclic->next_call)) { /* Call cyclic function and account it's cpu-time */ cyclic->next_call = now + cyclic->delay_us; cyclic->func(cyclic); cyclic->run_cnt++; - cpu_time = timer_get_us() - now; + cpu_time = get_timer_us(0) - now; cyclic->cpu_time_us += cpu_time; /* Check if cpu-time exceeds max allowed time */ -- 2.25.1

2 5

[PATCH] spi: cadence_qspi: Fix OSPI DDR mode alignment issue
by Padmarao Begari 22 Jan '25

22 Jan '25

If the least significant bit of the address is set to one when using the DDR protocol for data transfer then the results are indeterminate for few flash devices. To fix this the least significant bit of the address is set to zero. Signed-off-by: Padmarao Begari <padmarao.begari(a)amd.com> --- drivers/spi/cadence_ospi_versal.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/drivers/spi/cadence_ospi_versal.c b/drivers/spi/cadence_ospi_versal.c index 222f828f54..8827a24ee6 100644 --- a/drivers/spi/cadence_ospi_versal.c +++ b/drivers/spi/cadence_ospi_versal.c @@ -24,6 +24,13 @@ int cadence_qspi_apb_dma_read(struct cadence_spi_priv *priv, u8 opcode, addr_bytes, *rxbuf, dummy_cycles; n_rx = op->data.nbytes; + + if (op->addr.dtr && (op->addr.val % 2)) { + n_rx += 1; + writel(op->addr.val & ~0x1, + priv->regbase + CQSPI_REG_INDIRECTRDSTARTADDR); + } + rxbuf = op->data.buf.in; rx_rem = n_rx % 4; bytes_to_dma = n_rx - rx_rem; @@ -104,6 +111,11 @@ int cadence_qspi_apb_dma_read(struct cadence_spi_priv *priv, memcpy(rxbuf, &data, rx_rem); } + if (op->addr.dtr && (op->addr.val % 2)) { + rxbuf -= bytes_to_dma; + memcpy(rxbuf, rxbuf + 1, n_rx - 1); + } + return 0; } -- 2.25.1

2 1

[PATCH v2 0/2] Fix bridge gmii2rgmii
by Tapio Reijonen 22 Jan '25

22 Jan '25

When taken in use U-Boot v2023.04 one our board's ethernet stop to work in U-Boot, which was working in v2022.01. In v2022.01 the gmii2rgmii was called before PHY was created. This patch change back the order and fix the problem. Also the ethernet-phy-id driver is taken in use in gmii2rgmii driver. (no changes since v1) Tapio Reijonen (2): net: phy: Let gmiitorgmii converter create additional PHY net: phy: gmii2rgmii: Add support for phy ethernet id configuration drivers/net/phy/phy.c | 8 ++++---- drivers/net/phy/xilinx_gmii2rgmii.c | 12 +++++++++--- 2 files changed, 13 insertions(+), 7 deletions(-) -- 2.39.5

2 3

[PATCH v1 0/2] Fix bridge gmii2rgmii
by Tapio Reijonen 22 Jan '25

22 Jan '25

When taken in use U-Boot v2023.04 one our board's ethernet stop to work in U-Boot, which was working in v2022.01. In v2022.01 the gmii2rgmii was called before PHY was created. This patch change back the order and fix the problem. Also the ethernet-phy-id driver is taken in use in gmii2rgmii driver. Tapio Reijonen (2): net: phy: Let gmiitorgmii converter create additional PHY net: phy: gmii2rgmii: Add support for phy ethernet id configuration drivers/net/phy/phy.c | 8 ++++---- drivers/net/phy/xilinx_gmii2rgmii.c | 11 ++++++++--- 2 files changed, 12 insertions(+), 7 deletions(-) -- 2.39.5

3 7

[PATCH 0/3] sunxi: switch three SoC families to OF_UPSTREAM
by Andre Przywara 22 Jan '25

22 Jan '25

This series converts boards with the Allwinner F1C100s/F1C200s, A10, A10s and A13s SoCs over to OF_UPSTREAM. The .dts and .dtsi files were identical between the kernel and U-Boot repository, so this is a no-brainer. However there are four boards (tablets, I guess) that do not have a .dts file in the kernel repository. For now I kept them using the "old style", so they continue working. This requires to keep a copy of the SoC .dtsi file, I would be grateful for any advice as how to handle this situation best. Ideally we would submit the DTs to the kernel, but I don't know how feasible this is, given their age, the missing device availability and their basic DT nature. I compiled all boards with and without this series applied: the resulting u-boot.dtb files were always identical. Please have a look! Cheers, Andre Andre Przywara (3): suniv: switch Allwinner F1Cx00 boards to OF_UPSTREAM sunxi: switch Allwinner A10 boards to OF_UPSTREAM sunxi: switch Allwinner A10s/A13 boards to OF_UPSTREAM arch/arm/dts/Makefile | 48 +-- arch/arm/dts/sun4i-a10-a1000.dts | 255 ------------- arch/arm/dts/sun4i-a10-ba10-tvbox.dts | 151 -------- arch/arm/dts/sun4i-a10-chuwi-v7-cw0825.dts | 159 -------- arch/arm/dts/sun4i-a10-cubieboard.dts | 255 ------------- arch/arm/dts/sun4i-a10-dserve-dsrv9703c.dts | 218 ----------- arch/arm/dts/sun4i-a10-gemei-g9.dts | 192 ---------- arch/arm/dts/sun4i-a10-hackberry.dts | 140 ------- arch/arm/dts/sun4i-a10-hyundai-a7hd.dts | 115 ------ arch/arm/dts/sun4i-a10-inet1.dts | 229 ----------- arch/arm/dts/sun4i-a10-inet97fv2.dts | 203 ---------- arch/arm/dts/sun4i-a10-inet9f-rev03.dts | 357 ------------------ .../dts/sun4i-a10-itead-iteaduino-plus.dts | 126 ------- arch/arm/dts/sun4i-a10-jesurun-q5.dts | 181 --------- arch/arm/dts/sun4i-a10-marsboard.dts | 182 --------- arch/arm/dts/sun4i-a10-mini-xplus.dts | 144 ------- arch/arm/dts/sun4i-a10-mk802.dts | 144 ------- arch/arm/dts/sun4i-a10-mk802ii.dts | 111 ------ arch/arm/dts/sun4i-a10-olinuxino-lime.dts | 225 ----------- arch/arm/dts/sun4i-a10-pcduino.dts | 200 ---------- arch/arm/dts/sun4i-a10-pcduino2.dts | 67 ---- arch/arm/dts/sun4i-a10-pov-protab2-ips9.dts | 206 ---------- arch/arm/dts/sun4i-a10-topwise-a721.dts | 242 ------------ arch/arm/dts/sun5i-a10s-auxtek-t003.dts | 137 ------- arch/arm/dts/sun5i-a10s-auxtek-t004.dts | 149 -------- arch/arm/dts/sun5i-a10s-mk802.dts | 127 ------- arch/arm/dts/sun5i-a10s-olinuxino-micro.dts | 272 ------------- arch/arm/dts/sun5i-a10s-r7-tv-dongle.dts | 118 ------ arch/arm/dts/sun5i-a10s-wobo-i5.dts | 195 ---------- arch/arm/dts/sun5i-a10s.dtsi | 173 --------- arch/arm/dts/sun5i-a13-difrnce-dit4350.dts | 50 --- .../dts/sun5i-a13-empire-electronix-d709.dts | 190 ---------- .../dts/sun5i-a13-empire-electronix-m712.dts | 51 --- arch/arm/dts/sun5i-a13-hsg-h702.dts | 182 --------- arch/arm/dts/sun5i-a13-inet-98v-rev2.dts | 50 --- arch/arm/dts/sun5i-a13-licheepi-one.dts | 214 ----------- arch/arm/dts/sun5i-a13-olinuxino-micro.dts | 141 ------- arch/arm/dts/sun5i-a13-olinuxino.dts | 247 ------------ .../dts/sun5i-a13-pocketbook-touch-lux-3.dts | 258 ------------- arch/arm/dts/sun5i-a13-q8-tablet.dts | 80 ---- arch/arm/dts/sun5i-a13-utoo-p66.dts | 116 ------ arch/arm/dts/sun5i-a13.dtsi | 118 ------ arch/arm/dts/sun5i-gr8-chip-pro.dts | 238 ------------ arch/arm/dts/sun5i-gr8-evb.dts | 333 ---------------- arch/arm/dts/sun5i-gr8.dtsi | 126 ------- arch/arm/dts/sun5i-r8-chip.dts | 282 -------------- arch/arm/dts/sun5i-r8.dtsi | 47 --- .../dts/sun5i-reference-design-tablet.dtsi | 194 ---------- arch/arm/dts/suniv-f1c100s-licheepi-nano.dts | 73 ---- arch/arm/dts/suniv-f1c100s.dtsi | 330 ---------------- arch/arm/dts/suniv-f1c200s-lctech-pi.dts | 76 ---- arch/arm/dts/suniv-f1c200s-popstick-v1.1.dts | 81 ---- arch/arm/mach-sunxi/Kconfig | 3 + configs/A10-OLinuXino-Lime_defconfig | 2 +- configs/A10s-OLinuXino-M_defconfig | 2 +- configs/A13-OLinuXinoM_defconfig | 2 +- configs/A13-OLinuXino_defconfig | 2 +- configs/Ampe_A76_defconfig | 1 + configs/Auxtek-T003_defconfig | 2 +- configs/Auxtek-T004_defconfig | 2 +- configs/CHIP_defconfig | 2 +- configs/CHIP_pro_defconfig | 2 +- configs/Chuwi_V7_CW0825_defconfig | 2 +- configs/Cubieboard_defconfig | 2 +- configs/Empire_electronix_d709_defconfig | 2 +- configs/Empire_electronix_m712_defconfig | 2 +- configs/Hyundai_A7HD_defconfig | 2 +- configs/Linksprite_pcDuino_defconfig | 2 +- configs/Marsboard_A10_defconfig | 2 +- configs/Mele_A1000_defconfig | 2 +- configs/Mini-X_defconfig | 2 +- configs/UTOO_P66_defconfig | 2 +- configs/Wobo_i5_defconfig | 2 +- configs/ba10_tv_box_defconfig | 2 +- configs/difrnce_dit4350_defconfig | 2 +- configs/dserve_dsrv9703c_defconfig | 2 +- configs/iNet_3F_defconfig | 1 + configs/iNet_3W_defconfig | 1 + configs/iNet_86VS_defconfig | 1 + configs/inet1_defconfig | 2 +- configs/inet97fv2_defconfig | 2 +- configs/inet98v_rev2_defconfig | 2 +- configs/inet9f_rev03_defconfig | 2 +- configs/jesurun_q5_defconfig | 2 +- configs/lctech_pi_f1c200s_defconfig | 2 +- configs/licheepi_nano_defconfig | 2 +- configs/mk802_a10s_defconfig | 2 +- configs/mk802_defconfig | 2 +- configs/mk802ii_defconfig | 2 +- configs/pov_protab2_ips9_defconfig | 2 +- configs/q8_a13_tablet_defconfig | 2 +- configs/r7-tv-dongle_defconfig | 2 +- configs/sunxi_Gemei_G9_defconfig | 2 +- 93 files changed, 45 insertions(+), 8832 deletions(-) delete mode 100644 arch/arm/dts/sun4i-a10-a1000.dts delete mode 100644 arch/arm/dts/sun4i-a10-ba10-tvbox.dts delete mode 100644 arch/arm/dts/sun4i-a10-chuwi-v7-cw0825.dts delete mode 100644 arch/arm/dts/sun4i-a10-cubieboard.dts delete mode 100644 arch/arm/dts/sun4i-a10-dserve-dsrv9703c.dts delete mode 100644 arch/arm/dts/sun4i-a10-gemei-g9.dts delete mode 100644 arch/arm/dts/sun4i-a10-hackberry.dts delete mode 100644 arch/arm/dts/sun4i-a10-hyundai-a7hd.dts delete mode 100644 arch/arm/dts/sun4i-a10-inet1.dts delete mode 100644 arch/arm/dts/sun4i-a10-inet97fv2.dts delete mode 100644 arch/arm/dts/sun4i-a10-inet9f-rev03.dts delete mode 100644 arch/arm/dts/sun4i-a10-itead-iteaduino-plus.dts delete mode 100644 arch/arm/dts/sun4i-a10-jesurun-q5.dts delete mode 100644 arch/arm/dts/sun4i-a10-marsboard.dts delete mode 100644 arch/arm/dts/sun4i-a10-mini-xplus.dts delete mode 100644 arch/arm/dts/sun4i-a10-mk802.dts delete mode 100644 arch/arm/dts/sun4i-a10-mk802ii.dts delete mode 100644 arch/arm/dts/sun4i-a10-olinuxino-lime.dts delete mode 100644 arch/arm/dts/sun4i-a10-pcduino.dts delete mode 100644 arch/arm/dts/sun4i-a10-pcduino2.dts delete mode 100644 arch/arm/dts/sun4i-a10-pov-protab2-ips9.dts delete mode 100644 arch/arm/dts/sun4i-a10-topwise-a721.dts delete mode 100644 arch/arm/dts/sun5i-a10s-auxtek-t003.dts delete mode 100644 arch/arm/dts/sun5i-a10s-auxtek-t004.dts delete mode 100644 arch/arm/dts/sun5i-a10s-mk802.dts delete mode 100644 arch/arm/dts/sun5i-a10s-olinuxino-micro.dts delete mode 100644 arch/arm/dts/sun5i-a10s-r7-tv-dongle.dts delete mode 100644 arch/arm/dts/sun5i-a10s-wobo-i5.dts delete mode 100644 arch/arm/dts/sun5i-a10s.dtsi delete mode 100644 arch/arm/dts/sun5i-a13-difrnce-dit4350.dts delete mode 100644 arch/arm/dts/sun5i-a13-empire-electronix-d709.dts delete mode 100644 arch/arm/dts/sun5i-a13-empire-electronix-m712.dts delete mode 100644 arch/arm/dts/sun5i-a13-hsg-h702.dts delete mode 100644 arch/arm/dts/sun5i-a13-inet-98v-rev2.dts delete mode 100644 arch/arm/dts/sun5i-a13-licheepi-one.dts delete mode 100644 arch/arm/dts/sun5i-a13-olinuxino-micro.dts delete mode 100644 arch/arm/dts/sun5i-a13-olinuxino.dts delete mode 100644 arch/arm/dts/sun5i-a13-pocketbook-touch-lux-3.dts delete mode 100644 arch/arm/dts/sun5i-a13-q8-tablet.dts delete mode 100644 arch/arm/dts/sun5i-a13-utoo-p66.dts delete mode 100644 arch/arm/dts/sun5i-a13.dtsi delete mode 100644 arch/arm/dts/sun5i-gr8-chip-pro.dts delete mode 100644 arch/arm/dts/sun5i-gr8-evb.dts delete mode 100644 arch/arm/dts/sun5i-gr8.dtsi delete mode 100644 arch/arm/dts/sun5i-r8-chip.dts delete mode 100644 arch/arm/dts/sun5i-r8.dtsi delete mode 100644 arch/arm/dts/sun5i-reference-design-tablet.dtsi delete mode 100644 arch/arm/dts/suniv-f1c100s-licheepi-nano.dts delete mode 100644 arch/arm/dts/suniv-f1c100s.dtsi delete mode 100644 arch/arm/dts/suniv-f1c200s-lctech-pi.dts delete mode 100644 arch/arm/dts/suniv-f1c200s-popstick-v1.1.dts -- 2.46.2

3 10

[PATCH] configs: am62ax_evm_a53_defconfig: enable USB DFU support
by Siddharth Vadapalli 22 Jan '25

22 Jan '25

The config fragment "am62x_a53_usbdfu.config" which adds USB DFU support for AM62x SoC is applicable to the AM62Ax SoC as well. Hence, include it in "am62ax_evm_a53_defconfig" in order to enable support for USB DFU flash and boot. Signed-off-by: Siddharth Vadapalli <s-vadapalli(a)ti.com> --- Hello, This patch is based on commit 82d262ae162 Merge patch series "MediaTek MT7629 OF_UPSTREAM migration (v2)" of the master branch of Mainline U-Boot. Patch has been tested for SD Boot on AM62A7-SK to ensure that the change to am62ax_evm_a53_defconfig in this patch doesn't introduce a regression. Logs: https://gist.github.com/Siddharth-Vadapalli-at-TI/c8879ebb33417458cc39e262c… Regards, Siddharth. configs/am62ax_evm_a53_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/configs/am62ax_evm_a53_defconfig b/configs/am62ax_evm_a53_defconfig index bf6e9639901..a2f6d904df4 100644 --- a/configs/am62ax_evm_a53_defconfig +++ b/configs/am62ax_evm_a53_defconfig @@ -107,3 +107,5 @@ CONFIG_SYSRESET=y CONFIG_SPL_SYSRESET=y CONFIG_SYSRESET_TI_SCI=y CONFIG_FS_FAT_MAX_CLUSTSIZE=16384 + +#include <configs/am62x_a53_usbdfu.config> -- 2.43.0

1 0