summaryrefslogtreecommitdiff
path: root/include
AgeCommit message (Collapse)Author
10 daysMerge tag '09.02.00.010' into toradex_ti-u-boot-2023.04Max Krummenacher
RC Release 09.02.00.010 Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
2024-05-09dt-bindings: ti-serdes: Sync with kernelNishanth Menon
Sync with kernel please Signed-off-by: Nishanth Menon <nm@ti.com>
2024-05-08board: toradex: add aquila am69 supportEmanuele Ghidoli
This adds initial support for the Toradex Aquila AM69 module. Upstream-Status: Pending Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
2024-03-21common: Move framebuffer reservation to separate helperDevarsh Thakkar
Create separate helper for just reserving framebuffer region without creating or enabling simple-framebuffer node. This is useful for scenarios where user want to preserve the bootloader splash screen till OS boots up and display server gets started without displaying anything else in between and thus not requiring simple-framebuffer. Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
2024-03-21environment: ti: mmc_android: add vbmeta_vendor_dlkm partitionGuillaume La Roque
Add new partition to support avb on vendor_dlkm partition. Add for both Beagle Play and AM62X SK EVM. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> [mkorpershoek: added beagle play bits] Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2024-03-21environment: ti: mmc_android: add frp partitionGuillaume La Roque
Add new partition to support factory reset protection with android 14. It's needed to be able to do factory reset. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
2024-03-21environment: ti: mmc_android: update metadata partitionGuillaume La Roque
To fix vts_fs_test and be compliance with google requirements we need to move on f2fs partition type. fastboot format metadata fail with actual size so update it to 64MB. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
2024-03-21remoteproc: uclass: Add methods to load firmware to rproc and boot rprocMD Danish Anwar
Add APIs to set a firmware_name to a rproc and boot the rproc with the same firmware. Clients can call rproc_set_firmware() API to set firmware_name for a rproc whereas rproc_boot() will load the firmware set by rproc_set_firmware() to a buffer by calling request_firmware_into_buf(). rproc_boot() will then load the firmware file to the remote processor and start the remote processor. Also include "fs-loader.h" and make remoteproc driver select FS_LOADER in Kconfig so that we can call request_firmware_into_buf() from remoteproc driver. Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
2024-03-21arm: dts: ti: k3-j722s: Enable USB supportRavi Gunasekaran
Update the USB0, USB1 nodes and enable them. Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
2024-03-21env: ti: ti_armv7_common: Run main_cpsw0_qsgmii_phyinit conditionallyManorit Chawdhry
commit 0d72b0f2f83b788273c40ed4a64d1adf74877726 upstream. Since upstream U-Boot uses ti_common.env instead of ti_armv7_common.env, the implementation here differs in this aspect from the upstream commit. The main_cpsw0_qsgmii_phyinit command is defined only for certain TI SoCs which have the do_main_cpsw0_qsgmii_phyinit variable set. Add a check to ensure that the main_cpsw0_qsgmii_phyinit command is run only for such SoCs. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2024-03-21misc: k3_avs: add k3_check_opp functionReid Tonking
Useful when trying to check if an opp efuse is burned in or not. k3_avs driver checks opp_ids when probing and overwrites the voltage values in vd_data for the respective board. This can be called to check that data and returns 0 if valid. Reviewed-by: Udit Kumar <u-kumar1@ti.com> Signed-off-by: Reid Tonking <reidt@ti.com>
2024-03-21misc: k3_avs: Add opp_low supportReid Tonking
J7200 has support for opp_low, so adding the option here Reviewed-by: Udit Kumar <u-kumar1@ti.com> Signed-off-by: Reid Tonking <reidt@ti.com>
2024-03-21configs: introduce configs needed for the J722SJayesh Choudhary
Introduce the initial configs needed to support the J722S SoC family. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
2024-03-21arm: mach-k3: j722s: introduce clock and device files for J722S SoCJayesh Choudhary
Introduce support for J722S SoC. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
2024-03-07common: Move framebuffer reservation to separate helperDevarsh Thakkar
Create separate helper for just reserving framebuffer region without creating or enabling simple-framebuffer node. This is useful for scenarios where user want to preserve the bootloader splash screen till OS boots up and display server gets started without displaying anything else in between and thus not requiring simple-framebuffer. Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
2024-02-27environment: ti: mmc_android: add vbmeta_vendor_dlkm partitionGuillaume La Roque
Add new partition to support avb on vendor_dlkm partition. Add for both Beagle Play and AM62X SK EVM. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> [mkorpershoek: added beagle play bits] Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2024-02-22environment: ti: mmc_android: add frp partitionGuillaume La Roque
Add new partition to support factory reset protection with android 14. It's needed to be able to do factory reset. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
2024-02-22environment: ti: mmc_android: update metadata partitionGuillaume La Roque
To fix vts_fs_test and be compliance with google requirements we need to move on f2fs partition type. fastboot format metadata fail with actual size so update it to 64MB. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
2024-02-15remoteproc: uclass: Add methods to load firmware to rproc and boot rprocMD Danish Anwar
Add APIs to set a firmware_name to a rproc and boot the rproc with the same firmware. Clients can call rproc_set_firmware() API to set firmware_name for a rproc whereas rproc_boot() will load the firmware set by rproc_set_firmware() to a buffer by calling request_firmware_into_buf(). rproc_boot() will then load the firmware file to the remote processor and start the remote processor. Also include "fs-loader.h" and make remoteproc driver select FS_LOADER in Kconfig so that we can call request_firmware_into_buf() from remoteproc driver. Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
2024-02-15arm: dts: ti: k3-j722s: Enable USB supportRavi Gunasekaran
Update the USB0, USB1 nodes and enable them. Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
2024-01-20env: ti: ti_armv7_common: Run main_cpsw0_qsgmii_phyinit conditionallyManorit Chawdhry
commit 0d72b0f2f83b788273c40ed4a64d1adf74877726 upstream. Since upstream U-Boot uses ti_common.env instead of ti_armv7_common.env, the implementation here differs in this aspect from the upstream commit. The main_cpsw0_qsgmii_phyinit command is defined only for certain TI SoCs which have the do_main_cpsw0_qsgmii_phyinit variable set. Add a check to ensure that the main_cpsw0_qsgmii_phyinit command is run only for such SoCs. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2024-01-18headers: don't depend on errno.h being availableMax Krummenacher
These headers follow the pattern: | #if CONFIG_IS_ENABLED(FANCY_FEATURE) | void foo(void); | #else | static inline void foo(void) { return -ENOSYS; } | #endif In the #else path ENOSYS is used, however linux/errno.h is not included. If errno.h has not been included already the compiler errors out even if the inline function is not referenced. Make those headers self contained. Upstream-Status: Submitted [https://lore.kernel.org/all/20240118181106.4133924-1-max.oss.09@gmail.com/T/#u] Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
2023-12-26misc: k3_avs: add k3_check_opp functionReid Tonking
Useful when trying to check if an opp efuse is burned in or not. k3_avs driver checks opp_ids when probing and overwrites the voltage values in vd_data for the respective board. This can be called to check that data and returns 0 if valid. Reviewed-by: Udit Kumar <u-kumar1@ti.com> Signed-off-by: Reid Tonking <reidt@ti.com>
2023-12-26misc: k3_avs: Add opp_low supportReid Tonking
J7200 has support for opp_low, so adding the option here Reviewed-by: Udit Kumar <u-kumar1@ti.com> Signed-off-by: Reid Tonking <reidt@ti.com>
2023-12-19configs: introduce configs needed for the J722SJayesh Choudhary
Introduce the initial configs needed to support the J722S SoC family. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
2023-12-19arm: mach-k3: j722s: introduce clock and device files for J722S SoCJayesh Choudhary
Introduce support for J722S SoC. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
2023-12-11Merge tag '09.01.00.008' into toradex_ti-u-boot-2023.04-09.01.00.008Francesco Dolcini
RC Release 09.01.00.008
2023-12-01Merge tag '09.01.00.006' into toradex_ti-09.01.00.006Emanuele Ghidoli
RC Release 09.01.00.006
2023-11-30configs: am62x_evm_android: add extrasize for applying dt overlayGuillaume La Roque
Actually we just do a resize to fix issue when apply overlay on device tree without any free space but if overlay take more place as default extra size added fdt apply will fail. So to fix this issue add extra size corresponding to page size. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> Acked-by: Vishal Mahaveer <vishalm@ti.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Tested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-11-24environment: ti: k3_dfu_combined.env: add dfu_alt_info_ospi_nandRoger Quadros
Copy this over from k3_dfu.env. Signed-off-by: Roger Quadros <rogerq@kernel.org>
2023-11-24environment: ti: k3_dfu_combined.env: add dfu_alt_info_nandRoger Quadros
Copy this over from k3_dfu.env. Signed-off-by: Roger Quadros <rogerq@kernel.org>
2023-11-24configs: am64x_evm: provide NAND configurationRoger Quadros
Provide NAND device and NAND driver configuration for AM64x EVM. Signed-off-by: Roger Quadros <rogerq@kernel.org>
2023-11-22environment: ti: k3_dfu_combined.env: Fix env offset for eMMCJudith Mendez
The following shall be the eMMC layout for AM64x platform: boot0 partition 0x0+----------------------------------+ | tiboot3.bin (1 MB) | 0x800+----------------------------------+ | tispl.bin (2 MB) | 0x1800+-----------------------------------+ | u-boot.img (4 MB) | 0x3800+-----------------------------------+ | environment (128 KB) | 0x3900+-----------------------------------+ Move u-boot environment from 0x3400 to ox3800 since at 0x3400 it overlaps with u-boot.img. Signed-off-by: Judith Mendez <jm@ti.com>
2023-11-21include: configs: am62x_evm_android: Add am62b_p1_skevmMattijs Korpershoek
am62b_p1_skevm eeprom has been introduced with commit 09b2c79a8df8 ("board: ti: am62x: Add support to detect AM62B-P1 board") Since this support, board_name is updated and we can no longer boot android since we don't set the proper dtb_index. Add am62b_p1_skevm and load the same dtb as for am62x_skevm. Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Acked-by: Vishal Mahaveer <vishalm@ti.com>
2023-11-08configs: am62px: add android supportGuillaume La Roque
Add Android bootflow support for AM62PX SoC. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-10-30environment: ti: Find DTB files in dtb directories for legacy platformSinthu Raja
The dtb directory structure had been standardized by the TI arago distribution. The TI legacy platform still using the default mmc environment from the header file. Add the directory dtb/ to the DTB search path. Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
2023-10-25include: configs: omap5: Drop the prefix conf- for name_fit_configSinthu Raja
For legacy platforms the packaging of fitimage doesn't prefix the "conf-" in the DTB config section. So, drop the conf- prefix from the fdtfile name Fixes: 1eaf714ce2 "include: configs: Override get_fit_config to get FIT config for AM57x" Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
2023-10-24configs: introduce configs needed for the am62pxBryan Brattlof
Introduce the initial configs needed to support the am62px SoC family [bb@ti.com: rebased on TI's 2023.10 uboot] Signed-off-by: Bryan Brattlof <bb@ti.com>
2023-10-24arm: mach-k3: am62px: introduce clock and device files for wkup splBryan Brattlof
Include the clock and lpsc tree files needed for the wkup spl to initialize the proper PLLs and power domains to boot the SoC. [bb@ti.com: rebased to TI's 2023.04 uboot] Signed-off-by: Bryan Brattlof <bb@ti.com>
2023-10-12include: configs: omap5: Add support for FDT overlaySinthu Raja
As AM57x uses overlays for display and camera interfaces, add support to load DT overlay files to MMC boot. Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
2023-10-12configs: omap5: Enable custom mmc boot to distroboot for AM57xSinthu Raja
TI AM57x boards use a custom (though family common to TI boards) mechanism for booting Linux. Add support to enable custom MMC boot as a default option along with the distroboot approach. Also, add supporting mmc boot environment variables which shall be used for custom MMC boot Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
2023-10-09env: ti: ti_common.env: Fix get_overlaystring for FIT ImageManorit Chawdhry
commit 7ebbce535c774806b3db0bedd2ba3cfb95c07658 upstream. After the refactor with conf- nodes in fitImage, overlaystring wasn't didn't handle the new conf- nodes in FIT Booting. Fix get_overlaystring to handle conf- nodes. Fixes: 837833a724b7 ("environment: ti: Add get_fit_config command to get FIT config string") Reported-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Reviewed-by: Andrew Davis <afd@ti.com>
2023-10-07include: configs: Override get_fit_config to get FIT config for AM57xSinthu Raja
The get_fit_config is introduced [1] in ti_armv7_common.h to mangle the fdtfile name when used to select a config node from the OE made FIT image. The ti_armv7_common.h is common for both K3 and AM57xx platforms. AM57xx platforms' fdtfile name does not have '/' so the setexpr command fails and boot hangs. Override the get_fit_config in AM57x specific config header to get the FIT config name. [1]:472b8e71be84667201d0fb28649c3c6649ac49f8 Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
2023-09-26include: env: ti: mmc: Add 'ti' directory prefix for overlaysRavi Gunasekaran
DTBOs are stored in vendor specific directories in Linux. Add the vendor prefix to the path to load the overlay correctly. Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
2023-09-13include: configs: am62x_evm_android: Add Beagle Play supportMattijs Korpershoek
Beagle Play has a different dts and is also identified as board_name = am62x_beagleplay. It also has a different boot flow than the AM62x SK EVM. AM62x SK EVM: 1. Boot rom reads UDA (User Data Area), looking for tiboot3 2. Boot rom finds tiboot3 and loads it Beagle Play: 1. Boot rom looks for tiboot3 in mmc0boot0 2. Boot rom finds tiboot3 and loads it Because of this difference, we need to have another environment file for the Beagle Play, to describe the partitioning table. Add support for it to enable Android boot flow. Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-13environment: ti: mmc_android: relocate U-Boot environmentMattijs Korpershoek
The U-Boot environment is stored at offset 0x680000 (6.5MB) While this is fine for AM62x SK EVM (because its mmc0boot0 partition is 31.5MB), this does won't work on the Beagle Play, which only has 4MB. Booting Beagle Play shows: Loading Environment from MMC... MMC: block number 0x3500 exceeds max(0x2000) *** Warning - !read failed, using default environment Move the U-boot environment at lba 0x800 on mmc0boot0. This reserves 1MB so that tiboot3 to be on mmc0boot0 as well, which is the case for BeaglePlay. Also add a raw_partition label so that we can erase it with: fastboot erase bootenv The boot0 partition now looks as: blk boot0 partition (31.5 MB) 0x0+----------------------------------+ | empty (1 MB) | 0x800+----------------------------------+ | environment (128 KB) | | padding (384 KB) | 0xc00+----------------------------------+ | | | Remaining space (30.0 MB) | 0xfc00+----------------------------------+ pick Note: CONFIG_ENV_OFFSET is in bytes and fastboot_raw_* is in lba number. CONFIG_ENV_OFFSET=0x100000 -> lba 0x800 env size + padding = 512KB -> length of 0x400 lbas Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-13environment: ti: mmc_android: remove uboot-env partitionMattijs Korpershoek
The U-Boot environment is saved in mmc0boot0, not in a GPT user partition. Remove this un-needed partition here since it's misleading. Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-13include: environment: ti: mmc_android: set partition-type for metadataGuillaume La Roque
Some time when you try to format metadata partition it's not working because partition-type was not defined and found in mmc. So to fix it add variable to define metadata partition format to ext4. Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-13include: environment: ti: mmc_android: add init_boot partitionGuillaume La Roque
To fully support android 13 and fix vts_generic_boot_image_test we need to have an init_boot partition [1]. [1]: https://source.android.com/docs/core/architecture/partitions/generic-boot Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-13include: configs: am62x_evm: support boot image v4Safae Ouajih
- Add vendor_boot and init_boot partitions in partition table. - Rework Android bootflow to include vendor_boot image loading. Signed-off-by: Safae Ouajih <souajih@baylibre.com> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>