u-boot.git/arch/microblaze, branch v2026.04

Merge patch series "Update linker scripts to ensure appended device tree is correctly aligned"

2026-01-20T18:07:25Z

Tom Rini says: This series builds on top of what Beleswar Padhi did in [1]. While there's still discussion about the mkimage related parts, the linker portion appears to the reliable path forward. An alternative that I had mentioned before, and was part of previous discussions on this topic[2] is in the end I believe not reliable enough. While we can take an output file and pad it to where we think it needs to be, ultimately the linker needs to place the symbol where we want it and if that isn't where we pad to, we have a different problem. So what this series does (but each commit message elaborates on the arch-specific linker scripts being inconsistent) is make sure the linker script will place the required symbol at 8-byte alignment, and then also use an ASSERT to fail the build if this would not be true due to some unforseen event. [1]: https://lore.kernel.org/u-boot/20260112101102.1417970-1-b-padhi@ti.com/ [2]: https://source.denx.de/u-boot/u-boot/-/issues/30 Link: https://lore.kernel.org/r/20260115222828.3931345-1-trini@konsulko.com

microblaze: Update linker scripts to ensure appended device tree is aligned

2026-01-20T18:07:15Z

With commit 0535e46d55d7 ("scripts/dtc: Update to upstream version v1.7.2-35-g52f07dcca47c") it is now a fatal error to U-Boot if our device tree is not 8-byte aligned. In commit 85f586035d75 ("ARM: OMAP2+: Pad SPL binary to 8-byte alignment before DTB") Beleswar Padhi explains that we must have ALIGN(x) statements inside of a section to ensure that padding is included and not simply that the linker address counter is incremented. To that end, this patch: - Aligns the final section before _end (for U-Boot) or _image_binary_end (for xPL phases) by 8-bytes by adjusting the ALIGN(4) statement to be ALIGN(8) in the final section before the symbol. - Ensure that we do have alignment by adding an ASSERT so that when not aligned we fail to link (and explain why). Tested-by: Michal Simek Reviewed-by: Ilias Apalodimas Signed-off-by: Tom Rini

microblaze: Fix SPL device support

2026-01-19T08:17:00Z

Extend spl_boot_list[] only when SPL has support for it. Signed-off-by: Michal Simek Link: https://lore.kernel.org/r/d1c1d677b2eb4266290d31dbdf2e6e44c77a75ff.1768557507.git.michal.simek@amd.com

dtc: Add Kconfig option to pad device tree blob

2025-06-20T01:00:09Z

This will allow arch(s) that use device tree blobs to pad the end of the device tree so they can be modified by board files at run time. This will help prevent errors such as FDT_ERR_NOSPACE from occurring. Signed-off-by: Eric Schikschneit [trini: Change default order so that X86 && EFI_APP works correctly]

microblaze: drop volatile qualifier from gd pointer

2025-06-13T22:57:14Z

Signed-off-by: Rasmus Villemoes

dts: Deduplicate dtbs target

2024-10-15T01:32:04Z

The dtbs: target is almost identical in all architecture Makefiles. All architecture Makefiles include scripts/Makefile.dts . Deduplicate the dtbs: target into scripts/Makefile.dts . No functional change. Reviewed-by: Sumit Garg Signed-off-by: Marek Vasut Reviewed-by: Simon Glass Tested-by: Caleb Connolly #qcom, OF_UPSTREAM

arch: Use CONFIG_XPL_BUILD instead of CONFIG_SPL_BUILD

2024-10-11T17:44:47Z

Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: Simon Glass

lmb: do away with arch_lmb_reserve()

2024-09-03T20:08:50Z

All of the current definitions of arch_lmb_reserve() are doing the same thing -- reserve the region of memory occupied by U-Boot, starting from the current stack address to the ram_top. Introduce a function lmb_reserve_uboot_region() which does this, and do away with the arch_lmb_reserve() function. Instead of using the current value of stack pointer for starting the reserved region, have a fixed value, considering the stack size config value. Signed-off-by: Sughosh Ganu Reviewed-by: Simon Glass Acked-by: Ilias Apalodimas

lmb: make LMB memory map persistent and global

2024-09-03T20:08:50Z

The current LMB API's for allocating and reserving memory use a per-caller based memory view. Memory allocated by a caller can then be overwritten by another caller. Make these allocations and reservations persistent using the alloced list data structure. Two alloced lists are declared -- one for the available(free) memory, and one for the used memory. Once full, the list can then be extended at runtime. [sjg: Use a stack to store pointer of lmb struct when running lmb tests] Signed-off-by: Sughosh Ganu Signed-off-by: Simon Glass [sjg: Optimise the logic to add a region in lmb_add_region_flags()]

microblaze: Remove duplicate newlines

2024-07-15T18:12:18Z

Drop all duplicate newlines. No functional change. Signed-off-by: Marek Vasut