u-boot.git/board/toradex, branch next

toradex: tdx-cfg-block: Remove product ID limitation

2026-08-21T23:26:35Z

In the progress of decoupling from the Toradex product ID table, the implemented product ID limitation is now obsolete, as no new entries will be made to the table. Therefore, the implemented limitation logic needs to be removed, as otherwise new PID's written to the config block will be assigned as unknown. This also means that `get_toradex_modules_idx()` is now obsolete and can be dropped. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: tdx-cfg-block: Remove validation against PID table

2026-08-21T23:26:35Z

As no new entries will be made to the Toradex product ID table, interactive config block creating should no longer depend on that table to accept a module ID. Remove the interactive lookup against the product ID table and prompt directly for the module PID4 instead. Only check that the entered module ID does not exceed four digits. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: common: Decouple board sysinfo from the product ID table

2026-08-21T23:26:35Z

The sysinfo currently uses the Toradex product ID table to print a detailed board model string. With various new SoMs that are released by Toradex, the PID table grows and needs maintenance effort which can be avoided. Rather than printing the board model based on the PID table, rely on the model property of the device tree and the data written to the config block during manufacturing, which already describes the HW correctly. For example, the printed board model string will change from: Model: Toradex 0075 Verdin AM62 Dual 1GB WB IT V1.2A Serial#: 15412798 and become: Model: Toradex Verdin AM62 WB on Verdin Development Board Toradex SoM: 0075 V1.2A (00751200) Serial#: 15412798 This removes detailed SKU information such as the number of cores, memory size, WB capability and temperature rating, but the PID4, PID8 and revision of the SoM are still printed. The detailed information of the SoM can still be looked up using the printed information on the official Toradex website. Decouple board sysinfo from the Toradex product ID table, making the 0243 Aquila iMX95 the last entry being made to it. Link: https://www.toradex.com/computer-on-modules Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: verdin-imx8mm: Set WiFi DTB as default for new PIDs

2026-08-21T23:26:35Z

Currently, the Verdin iMX8MM uses the Toradex product ID table to determine whether the module is a WiFi or a non-WiFi one and sets the DTB accordingly. In the progress of decoupling from the Toradex product PID table, use the WiFi DTB as the default for new PIDs. This change is safe, as on non-WiFi modules this leaves the WiFi and BT devices unprobed. Further, the SDIO/UART signals are exposed to the edge connector on non-WiFi modules and can be used on the carrier. However, no Toradex carrier board makes use of these interfaces on the carrier and it can only be achieved with a customized board. For customized boards, it's expected to override the default selection by setting the 'fdtfile' env variable. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: verdin-imx8mp: Set WiFi DTB as default for new PIDs

2026-08-21T23:26:35Z

Currently, the Verdin iMX8MP uses the Toradex product ID table to determine whether the module is a WiFi or a non-WiFi one and sets the DTB accordingly. In the progress of decoupling from the Toradex product PID table, use the WiFi DTB as the default for new PIDs. This change is safe, as on non-WiFi modules this leaves the WiFi and BT devices unprobed. Further, the SDIO/UART signals are exposed to the edge connector on non-WiFi modules and can be used on the carrier. However, no Toradex carrier board makes use of these interfaces on the carrier and it can only be achieved with a customized board. For customized boards, it's expected to override the default selection by setting the 'fdtfile' env variable. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: verdin-imx95: Set WiFi DTB as default for new PIDs

2026-08-21T23:26:35Z

Currently, the Verdin iMX95 uses the Toradex product ID table to determine whether the module is a WiFi or a non-WiFi one and sets the DTB accordingly. In the progress of decoupling from the Toradex product PID table, use the WiFi DTB as the default for new PIDs. This change is safe, as on non-WiFi modules this leaves the WiFi and BT devices unprobed. Further, the SDIO/UART signals are exposed to the edge connector on non-WiFi modules and can be used on the carrier. However, no Toradex carrier board makes use of these interfaces on the carrier and it can only be achieved with a customized board. For customized boards, it's expected to override the default selection by setting the 'fdtfile' env variable. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: verdin-am62p: Set WiFi DTB as default for new PIDs

2026-08-21T23:26:35Z

Currently, the Verdin AM62P uses the Toradex product ID table to determine whether the module is a WiFi or a non-WiFi one and sets the DTB accordingly. In the progress of decoupling from the Toradex product PID table, use the WiFi DTB as the default for new PIDs. This change is safe, as on non-WiFi modules this leaves the WiFi and BT devices unprobed. Further, the SDIO/UART signals are exposed to the edge connector on non-WiFi modules and can be used on the carrier. However, no Toradex carrier board makes use of these interfaces on the carrier and it can only be achieved with a customized board. For customized boards, it's expected to override the default selection by setting the 'fdtfile' env variable. Since there is only one Verdin AM62P PID, completely remove the PID based late selection. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: verdin-am62: Set WiFI DTB as default for new PIDs

2026-08-21T23:26:34Z

Currently, the Verdin AM62 uses the Toradex product ID table to determine whether the module is a WiFi or a non-WiFi one and sets the DTB accordingly. In the progress of decoupling from the Toradex product PID table, use the WiFi DTB as the default for new PIDs. This change is safe, as on non-WiFi modules this leaves the WiFi and BT devices unprobed. Further, the SDIO/UART signals are exposed to the edge connector on non-WiFi modules and can be used on the carrier. However, no Toradex carrier board makes use of these interfaces on the carrier and it can only be achieved with a customized board. For customized boards, it's expected to override the default selection by setting the 'fdtfile' env variable. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

toradex: apalis-imx8: select QP/QM device tree from OTP fuse

2026-08-14T19:20:09Z

The Apalis iMX8QM and iMX8QP can be distinguished reading out the OTP fuse word 6. This logic is already used for memory layout selection and can also be reused to select the corresponding device tree. Decouple the device tree selection from the Toradex product PID table by moving the OTP-based QP/QM detection into a helper function used by both memory layout and device tree selection. Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

board: toradex: aquila-imx95: add SPL quick boot autosave support

2026-08-14T19:19:13Z

Add support for the QuickBoot save feature in the SPL for Aquila iMX95 modules to speed up boot time by skipping DDR training if a valid QuickBoot save is found. When CONFIG_SPL_IMX_QB is enabled, the settings will be stored automatically from the SPL. Otherwise, the command 'qb save mmc 0:1' must be used. Signed-off-by: Stefan Eichenberger