summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
13 daysimx93: adc: local variable ret should not be unsignedAndrew Goodbody
Local variable ret is declared as unsigned but is used to receive the return value of functions that return int. ret is then tested for being negative which must always fail. Change ret to be an int. This issue was found by Smatch. Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org>
13 daysboard: phytec: migrate imx8mm boards to standard bootYannic Moog
remove boot logic from shared env file for phyboard-polis and phygate-tauri. Adjust configs for both boards as well. Space at the beginning of addressable RAM is reserved for space used via standard boot env variables. CONFIG_SYS_LOAD_ADDR is set to the lowest address behind the standard boot variables reserved space. Signed-off-by: Yannic Moog <y.moog@phytec.de>
13 daysimx: power-domain: Fix crash due to uninitialized 'id' fieldFrieder Schrempf
In case of the i.MX8M power-domains (i.MX8MQ, MM, MN) there is only one power-domain for each device. Therefore the 'id' field in struct power_domain should always be zero. Currently if a power-domain is accessed after the initial bind, the 'id' field is left uninitialized. This didn't cause any problems until the following commits were introduced: 9086b64ca071 ("power-domain: Add support for refcounting (again)") a785ef24487b ("imx: power-domain: Enable refcounting on imx8mp") Now the 'id' field gets accessed in the power_domain_off() sequence and the invalid value causes "Synchronous Abort" failures. This was observed on a i.MX8MM board when running "usb start" and then "usb stop". Fix this issue by setting power_domain->id to '0' in imx8m_power_domain_of_xlate(). Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> Fixes: d08a194871fd ("imx: add support for i.MX8MQ power domain controller") Fixes: 9086b64ca071 ("power-domain: Add support for refcounting (again)") Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
13 daysconfigs: imx6dl_sielaff: Set CONFIG_SDP_LOADADDR to fix SDP bootFrieder Schrempf
We need to set CONFIG_SDP_LOADADDR to a reasonable value in order to successfully load the U-Boot proper image in SPL via SDP. Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> Acked-by: Peng Fan <peng.fan@nxp.com>
13 daysimx6dl-sielaff: Convert to OF_UPSTREAMFrieder Schrempf
Switch to OF_UPSTREAM to make use of the upstream devicetree. Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> Reviewed-by: Peng Fan <peng.fan@nxp.com>
13 daystoradex: tdx-cfg-block: add verdin i.mx8m mini 0216 pid4Vitor Soares
Add PID4 0216 Verdin iMX8M Mini Quad 2GB WB IT to config block handling. Signed-off-by: Vitor Soares <vitor.soares@toradex.com> Acked-by: Francesco Dolcini <francesco.dolcini@toradex.com>
13 daysboard: phytec: phycore-imx93: Drop unused include filesPrimoz Fiser
Drop unused include files from the PHYTEC phyCORE-i.MX93 board code. Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>
13 daysboard: phytec: phycore-imx93: Drop unused PMIC definePrimoz Fiser
Drop unused define for PCA9450 PMIC register which is already part of the header file <power/pca9450.h> since commit 1d0d25704345 ("imx93_evk: spl: update pmic settings"). Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>
13 daysfirmware: zynqmp: Simplify power-domain driver bindMichal Simek
CONFIG_IS_ENABLED macro is covering CONFIG_POWER_DOMAIN or CONFIG_SPL_POWER_DOMAIN Kconfig symbols based on build target which simplify logic around binding power domain driver. Signed-off-by: Michal Simek <michal.simek@amd.com> Link: https://lore.kernel.org/r/c75627e92eeaffedf0f7e682edd4f6f39f0b5706.1752826352.git.michal.simek@amd.com
13 daysarm64: zynqmp: Let fit-dtb.blob generated all the timeMichal Simek
There is a value to generate fit-dtb.blob even for cases without SPL because flows with FSBL also require it. Reviewed-by: Neha Malcom Francis <n-francis@ti.com> Signed-off-by: Michal Simek <michal.simek@amd.com> Link: https://lore.kernel.org/r/c2952da3c064d67821cd166d2392db39c1d23b2c.1752822270.git.michal.simek@amd.com
13 daysRevert "spi: cadence_qspi: Fix odd byte write issue in STIG mode"Prasanth Babu Mantena
The buffer that is being used to write into the flash needs to be handled properly with padding of 0xFF. The place that this is done can be at a more generic place like spi-nor core. This reverts commit cd9123507003e07b13e61d72e14e493bb338e827. Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com> Reviewed-by: Neha Malcom Francis <n-francis@ti.com> Reviewed-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com> Link: https://lore.kernel.org/r/20250716070407.2082524-1-p-mantena@ti.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysnet: xilinx: Fix kernel-doc for axi_mrmac function parametersVenkatesh Yadav Abbarapu
The kernel-doc comment for the axi_mrmac_recv function was missing the colon (':') after the '@packetp' parameter tag. The kernel-doc comment for the axi_mrmac_free_pkt function was missing the colon (':') after the 'length' parameter tag. This caused a Sparse warnings regarding the 'packetp' and 'length' parameters not being described. Fix the formatting to align with kernel-doc standards and resolve the warning. drivers/net/xilinx_axi_mrmac.c:357: warning: Function parameter or member 'packetp' not described in 'axi_mrmac_recv' drivers/net/xilinx_axi_mrmac.c:411: warning: Function parameter or member 'length' not described in 'axi_mrmac_free_pkt' Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com> Link: https://lore.kernel.org/r/20250717044855.1359443-1-venkatesh.abbarapu@amd.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysgpio: zynq: Fix the documentation warning in zynq_gpio_get_bank_pinVenkatesh Yadav Abbarapu
The 'dev' parameter in the zynq_gpio_get_bank_pin function was not described in its kernel-doc comment block, leading to a Sparse warning. drivers/gpio/zynq_gpio.c:194: warning: Function parameter or member 'dev' not described in 'zynq_gpio_get_bank_pin' Add a description for the 'dev' parameter to satisfy the documentation requirements and improve code clarity for this function. Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com> Link: https://lore.kernel.org/r/20250717044632.1353588-1-venkatesh.abbarapu@amd.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysconfigs: enable FPGA commands and drivers at sandbox_defconfigPieter Van Trappen
Enable to facilitate compiler checks on most FPGA-related sources. Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch> Link: https://lore.kernel.org/r/20250708152455.1214487-7-vtpieter@gmail.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysdrivers: fpga: fix function declaration without a prototypePieter Van Trappen
As reported by clang 20.1, fix multiple of the following: drivers/fpga/ivm_core.c:593:23: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes] 593 | long int ispVMDataSize() | ^ | void Also fix the following warning from checkpatch.pl: WARNING: Prefer 'long' over 'long int' as the int is unnecessary Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch> Link: https://lore.kernel.org/r/20250708152455.1214487-6-vtpieter@gmail.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysdrivers: fpga: cleanup printf usagePieter Van Trappen
Remove `fpga_no_sup` to get rid of Werror=unused-function when all FPGA configurations are enabled. Swap all printf calls to log_* as this is now preferred and includes the calling __func__. Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch> Link: https://lore.kernel.org/r/20250708152455.1214487-5-vtpieter@gmail.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysdrivers: fpga: correct compiler errors and warningsPieter Van Trappen
Errors reported by GCC 14.2 when enabling FPGA commands and drivers. Also many style fixes as reported by checkpatch.pl on the diffs. Most changes in stratixII.c which has been reorganized as well to avoid the top function prototypes. No functional changes. Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch> Link: https://lore.kernel.org/r/20250708152455.1214487-4-vtpieter@gmail.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysdrivers: fpga: add Kconfig dependencyPieter Van Trappen
FPGA_SOCFPGA requires ARCH_SOCFPGA cause socfpga.c contains arch/arm/mach-socfpga/* include macros. Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch> Link: https://lore.kernel.org/r/20250708152455.1214487-3-vtpieter@gmail.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 dayscmd: fpga: improve user feedback in case of bitstream load failurePieter Van Trappen
In cmd/fpga.c, change some `debug` calls to `log_err` for important user feedback and use CMD_RET_FAILURE in favor of CMD_RET_USAGE due to its long output which hides the actual, useful return message. Change the remaining `debug` calls to `log_debug`. Remove all 'fpga:' and __func__ strings as log_* has this covered. For `do_fpga_loads`, move up the `do_fpga_check_params` call for more consistent command output; use a constant instead of multiple '5' use. In drivers/fpga/zynq*.c, change 'up to' to 'above' which corrects this confusing/wrong statement. Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch> Link: https://lore.kernel.org/r/20250708152455.1214487-2-vtpieter@gmail.com Signed-off-by: Michal Simek <michal.simek@amd.com>
13 daysxilinx: zynqmp: Remove PSCI_RESET from mini configurationsMichal Simek
There is no reason to call reset in these size constrained configurations that's why remove it to get some space. Signed-off-by: Michal Simek <michal.simek@amd.com> Link: https://lore.kernel.org/r/cb5189d676852cad7ab3c0691490b2d0dac618b4.1751014928.git.michal.simek@amd.com
13 daysFix emmc error state after mmc write timeoutIulian Banaga
This is a fix for the sporadic mmc write failure: mmc write failed 0 blocks written: ERROR After this happens the emmc will remain in an error state where subsequent read/writes fail with a timeout. The mmc driver sends CMD25 - WRITE_MULTIPLE_BLOCK which can sporadically timeout. When this happens, the mmc driver aborts the transfer and returns the above error messages. But the emmc still remains in data transfer mode, since the timeout was decided by uboot, not by the emmc. Fix this by sending the STOP_TRANSMISSION command (CMD12) and waiting for the emmc to be in ready state again (CMD13). Transferring data blocks after a CMD25 can take anywhere between 5 and +15s on Samsung EMMCs and the current timeout is not enough. Increase the timeout by 2x to accommodate the long transfer times observed. Signed-off-by: Iulian Banaga <iulianeugen.banaga@mobileye.com> Acked-by: Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com> Reviewed-by: Peng Fan <peng.fan@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
13 daysmmc: exynos_dw_mmc: add exynos5420 compatiblesJaehoon Chung
The exynos5420 DTSes in linux kernel uses the compatibles samsung,exynos5420-dw-mshc{,-smu} instead of just samsung,exynos-dwmmc. Match the additional compatibles in the driver to make it possible to use it with DTSes from Linux kernel. Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com> [ grimler: rebase after clksel reg abstraction and re-write commit message ] Signed-off-by: Henrik Grimler <henrik@grimler.se> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org> Reviewed-by: Anand Moon <linux.amoon@gmail.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
13 daysmmc: s5p_sdhci: add samsung,exynos4210-sdhci compatibleHenrik Grimler
the Exynos4210 devices in u-boot uses samsung,exynos4412-sdhci as sdhci compatible in their DTSes, while the upstream DTSes uses samsung,exynos4210-sdhci. Add samsung,exynos4210-sdhci compatible string for s5p_sdhci driver as well so that it can be used with upstream DTSes. Signed-off-by: Henrik Grimler <henrik@grimler.se> Reviewed-by: Anand Moon <linux.amoon@gmail.com> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org> Signed-off-by: Peng Fan <peng.fan@nxp.com>
13 daysmmc: s5p_sdhci: remove duplicated card detect codeHenrik Grimler
The common sdhci infrastructure is already parsing the cd-gpios property, since commit 451931ea7002 ("mmc: sdhci: Read cd-gpio from devicetree"). The s5p code is therefore duplicated, and also broken since it assumes that the GPIO value is inverted, while the sdhci code correctly follows the ACTIVE_LOW/ACTIVE_HIGH flag specified in the device tree. This fix was originally authored by Simon Shields: https://github.com/fourkbomb/u-boot/commit/2eac9dea7903 The change has been tested on exynos4210-i9100, a device similar to exynos4210-trats. Signed-off-by: Henrik Grimler <henrik@grimler.se> Reviewed-by: Anand Moon <linux.amoon@gmail.com> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org> Signed-off-by: Peng Fan <peng.fan@nxp.com>
14 daysblock: Remove blk_find_first/nextGreg Malysa
In [0], Andrew noted a code quality issue in the implementation of blk_find_first and blk_find_next. This led to the observation that the logic of these functions was also likely incorrect, and based on a quick check it seemed the functions were unused outside of test code, which did not exercise the potential failure case, so we felt they should be removed. In [1], a test patch which illustrates the failure in sandbox is provided for reference. Because a more thorough check agrees that these functions are unused, they are currently incorrect, and fixed/removable flags on block devices prior to probe are unreliable, just remove these functions instead of fixing them. All potential users should have used blk_first_device_err instead anyway. CI results at [2]. [0] https://patchwork.ozlabs.org/project/uboot/patch/20250714-blk-uclass-v1-1-d21428c5f762@linaro.org/ [1] https://gist.github.com/gmalysa/b05e73a5c14bc18c5741a0e0e06a2992 [2] https://gitlab.com/gmalysa/lnxdsp-u-boot/-/pipelines/1931210857 Signed-off-by: Greg Malysa <malysagreg@gmail.com> Reviewed-by: Andrew Goodbody <andrew.goodbody@linaro.org>
14 dayssysreset: psci: Fix SPL dependencyMichal Simek
SYSRESET_PSCI should select SPL_ARM_PSCI_FW only when SPL_SYSRESET is enabled/required. This change saves 1.6kB on Xilinx ZynqMP Kria platform. Signed-off-by: Michal Simek <michal.simek@amd.com> Reviewed-by: Tom Rini <trini@konsulko.com>
14 dayscmd: gpt: Fix off by 1 errorsAndrew Goodbody
The buffer for a name to be copied into must also contain the terminating 0 byte but strlen returns the length of the string without counting that 0 byte. Adjust the length checks to take this into account. This issue found by Smatch. Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org>
14 daysabuf: Remove code that prevented test code runningAndrew Goodbody
When abuf was introduced some test code was prevented from running using a 'return 0' early in the functions. A comment said it crashed on sandbox due to a 'bug' in realloc. Some time later a bug in abuf_realloc was fixed but this test code was never enabled. Remove the early 'return 0' instances so that the test code can run. Also remove some checks that relied on the implementation details of the U-Boot memory code as these can fail on sandbox which uses system memory code. Besides that this code should be testing abuf implementation not the underlying memory code which has its own tests. Finally use a new #define for the allocs that are meant to fail to ensure they do fail on all CI platforms. This issue found by Smatch. Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org>
14 daysAzure: Temporarily switch to GitHub mirror of u-boot-test-hooksTom Rini
In order to unblock this CI workflow for the moment, switch to using a mirror of u-boot-test-hooks on GitHub rather than source.denx.de. Signed-off-by: Tom Rini <trini@konsulko.com>
14 dayspatman: Update test for Anatolij's new email addressTom Rini
This test was failing due to matching on Anatolij's old email address. Switch to the new one. Signed-off-by: Tom Rini <trini@konsulko.com>
14 daysMerge patch series "mkimage: validate default configuration reference"Tom Rini
Aristo Chen <jj251510319013@gmail.com> says: This patch series introduces a validation step in `mkimage` to ensure that the `default` property under the `/configurations` node in a FIT image references a valid subnode. If the referenced node does not exist, mkimage now prints an error and fails early. This helps prevent runtime failures when U-Boot attempts to boot using an undefined configuration. The first patch implements the validation logic in `fit_image.c`. The second patch fixes an invalid default configuration reference exposed by this new check in the `k3-am65-iot2050-boot-image.dtsi`. The final patch adds a test case to verify that mkimage correctly fails when an invalid default configuration is present in the ITS file. This series improves the robustness of FIT image generation and helps catch malformed image trees during build time. Link: https://lore.kernel.org/r/20250715130317.3886-1-aristo.chen@canonical.com
14 daystest: fit: add test case for invalid default configuration referenceAristo Chen
Recent changes to mkimage introduced a validation step to ensure that the 'default' property under the /configurations node in a FIT image references a valid configuration subnode. If the referenced node is missing, mkimage will now return an error. This patch adds a Python test case to verify that mkimage correctly fails when the 'default' configuration does not exist. The test creates a minimal ITS with an invalid default reference and checks that mkimage produces the expected error message. Signed-off-by: Aristo Chen <aristo.chen@canonical.com>
14 daystools: fit_image: validate existence of default configuration nodeAristo Chen
When a FIT image declares a default configuration via the 'configurations/default' property, it must reference a valid subnode under the /configurations node. If the named default does not exist, U-Boot will fail to boot the image when no explicit configuration is provided. This patch adds a validation step in mkimage to check that the referenced default configuration node is present. If not, mkimage will print an error and abort. This helps catch malformed or outdated ITS files early at build time instead of deferring failure to runtime. Signed-off-by: Aristo Chen <aristo.chen@canonical.com>
14 daysarm: k3-am65-iot2050: Fix invalid default configuration referenceAristo Chen
mkimage introduced a validation step to ensure that the 'default' property under the /configurations node in a FIT image refers to a valid subnode. This exposed an issue in the k3-am65-iot2050-boot-image.dtsi, where the 'default' property was set to "ti/k3-am6528-iot2050-basic" and "ti/k3-am6528-iot2050-basic-pg2", which do not correspond to actual configuration node names. This patch updates both /configurations nodes to reference the correct subnode. Without this fix, mkimage will fail with an error: "ERROR: Default configuration 'ti/k3-am6528-iot2050-basic' not found under /configurations" An upcoming commit will validate the if the default configuration exists Signed-off-by: Aristo Chen <aristo.chen@canonical.com>
2025-07-22Merge patch series "bootstd: rauc: Small fixes"Tom Rini
Martin Schwan <m.schwan@phytec.de> says: Fix some small bugs that I noticed during testing. Link: https://lore.kernel.org/r/20250714-wip-bootmeth-rauc-fixes-v1-0-69d2b80e7606@phytec.de
2025-07-22bootstd: rauc: Only scan all partitions instead of boot filesMartin Schwan
Only scan for the existence of all required partitions of a RAUC system, instead of searching for boot script files in all of them. Previously, it might have occurred, that a slot did not contain required files and RAUC already marked the corresponding slot as bad (not suitable for booting). In that case, scanning for a non-existence boot script would result in an error (and thus not booting anything), which was different behavior compared to the legacy RAUC boot. Signed-off-by: Martin Schwan <m.schwan@phytec.de>
2025-07-22bootstd: rauc: Fix segfault occurring during private struct accessMartin Schwan
Fix a potential segmentation fault, by not accessing the member of a null pointer to a private slot's name field. Signed-off-by: Martin Schwan <m.schwan@phytec.de>
2025-07-22bootstd: rauc: Fix potential memory leakMartin Schwan
Fix a potential memory leak, by checking the return value of realloc first, before assigning it to the private list of slots. Signed-off-by: Martin Schwan <m.schwan@phytec.de>
2025-07-22km: pg-wcom-ls1021xa: update MAINTAINERSHolger Brunck
The mainainers for these boards have changed. Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com> Signed-off-by: Tomas Alvarez Vanoli <tomas.alvarez-vanoli@hitachienergy.com>
2025-07-22km: pg-wcom-ls102xa: call qrio deblock cfg earlierTomas Alvarez Vanoli
Move the call to configure the qrio i2c deblock pins earlier. Before this, the call was happening after the first attempt to deblock the SDP EEPROM, which resulted in a not correct sequence. Signed-off-by: Tomas Alvarez Vanoli <tomas.alvarez-vanoli@hitachienergy.com> Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
2025-07-22km: pg-wcom-ls102xa: add netdev in board env fileHolger Brunck
Upcoming boards will have different ethernet interfaces. So we move this variable out of the common code. Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
2025-07-22arm: ls1021a-pg-wcom: add i2c mux node and eepromHolger Brunck
We are now using the DM code for the i2c mux and to read out the inventory eeprom. Therefore we need to add the nodes to the specific DTS files. Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
2025-07-22km: drop KM_RESERVED_PRAMHolger Brunck
This variable is unused since we dropped the support for the Kirkwood boards. Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
2025-07-22km: qrio: fix set_gpio read/modify/writeTomas Alvarez Vanoli
Setting GPIO by reading the value of the GPRT register, toggling the correct bit and then writing it causes input values to transfer to the output. Here's how (example): 1) set gpio 17 and 18 as input. 2) set gpio 17 output value to 0 (read gprt, change 17 to 0, write). 3) set gpio 18 output value to 0 (read gprt, change 18 to 0, write). The problem here is that because we set 17 as input, and it's a pull-up, when we read gprt in step 3, the bit 17 will be 1 and not 0. Instead of doing read/write/modify, the solution is to keep track internally of the user set GPIOs, and replace the read step with this static variable. Signed-off-by: Tomas Alvarez Vanoli <tomas.alvarez-vanoli@hitachienergy.com> Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
2025-07-22fastboot: Fix off by 1 errorAndrew Goodbody
strlen only reports length of string not including terminating 0 byte but this has to be included in length of receiving buffer on copy so adjust length check to be correct. This issue found by Smatch. Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org> Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
2025-07-22drivers: fastboot: Add support for SPI flash memoryAriel D'Alessandro
Fastboot currently supports MMC and NAND flash devices. Similarly, extend the support to SPI flash memories. Note that in this initial implementation, partitions on the device are not supported yet, but raw partitions can be set in U-Boot environment. To define a raw partition descriptor, add an environment variable similar to the MMC case: ``` fastboot_raw_partition_<raw partition name>=<offset> <size> ``` for example: ``` fastboot_raw_partition_boot=0x0 0x1000000 ``` Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
2025-07-22include: env: ti_common: remove bootm_sizeBryan Brattlof
As the size of 64b ARM kernels, DTs, vendor firmware, and initial ram disks continues to grow, the 256MB size limit set aside for image processing by the bootm command has become too small for some K3 reference boards. For ARMv7 removing this limit could introduce issues so move the bootm_size variable to ti_armv7_keystone2.env and remove the limit for any board using a TI K3 SoC. Signed-off-by: Bryan Brattlof <bb@ti.com>
2025-07-22binman: Fix typing for python >= 3.7Yannic Moog
To get the [] annotation working with python 3.7 and 3.8, import annotations. Reported-by: Tim Harvey <tharvey@gateworks.com> Fixes: 21bc3433a43d ("binman: rework dropping absent entries from packaged image") Reviewed-by: Bryan Brattlof <bb@ti.com> Signed-off-by: Yannic Moog <y.moog@phytec.de> Tested-by: Tim Harvey <tharvey@gateworks.com>
2025-07-22lmb: Remove unreachable codeAndrew Goodbody
Code after a break is unreachable so remove it. Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org>
2025-07-22arm: fix lmb region reservation when PRAM is definedHolger Brunck
PRAM usage is not taken into account when reserving lmb for ARM architecture, this means that predefined PRAM region is marked as reserved by the architecture and cannot be used by other users. Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
generated by cgit v1.2.3 (git 2.0.4) at 2025-08-06 12:40:11 +0000