| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
Update the USB0, USB1 nodes and enable them.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Introduce support for J722S SoC.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
|
|
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>
|
|
RC Release 09.01.00.008
|
|
RC Release 09.01.00.006
|
|
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>
|
|
Copy this over from k3_dfu.env.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
Copy this over from k3_dfu.env.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
Provide NAND device and NAND driver configuration for AM64x EVM.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
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>
|
|
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>
|
|
Add Android bootflow support for AM62PX SoC.
Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
- 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>
|
|
RC Release 09.00.00.008
|
|
Add update_tiboot3, update_tispl and update_uboot wrappers to update
R5 SPL, A53 SPL and A53 U-boot respectively.
Usage example:
> tftpboot ${loadaddr} tiboot3-am62x-gp-verdin.bin
> run update_tiboot3
> tftpboot ${loadaddr} tispl.bin
> run update_tispl
> tftpboot ${loadaddr} u-boot.img
> run update_uboot
Upstream-Status: Pending
This patch will be submitted after the
Verdin AM62 initial support series is upstreamed.
https://lore.kernel.org/all/20230803140016.52846-1-marcel@ziswiler.com/
Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
|
|
Add android boot flow support for AM62X board based on misc partition
to detect reboot reason and boot.img version 2 from android build
system.
Also add device tree overlay support for Android to enable CSI camera,
LVDS screen, HDMI Audio output.
This assumes that the `dtbo_index` env variable is a space-separated
list of indices.
Example:
=> env set dtbo_index "0 2"
=> run distro_bootcmd
Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
[mkorpershoek: move parts to am62x.env file]
Co-developed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
|
|
Enable DFU support for the A53, for the R5 due to the smaller available
size create a new configuration just for DFU support. Also enable USB
device aka gadget and USB host support.
Upstream-Status: Pending
USB support missing upstream
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This adds initial support for the Toradex Verdin AM62 Quad 1GB WB IT
V1.0A module. They are strapped to boot from their on-module eMMC.
U-Boot supports booting from the on-module eMMC only, DFU support is
disabled for now due to missing AM62x USB support.
Boot sequence is:
SYSFW ---> R5 SPL (both in tiboot3.bin) ---> ATF (TF-A) ---> OP-TEE
---> A53 SPL (part of tispl.bin) ---> U-boot proper (u-boot.img)
Upstream-Status: Pending
V2 has been sent [1] and a re-based V3 will be sent once the upstream
TI stuff sufficiently stabilizes.
[1] https://lore.kernel.org/all/20230612205444.363727-4-marcel@ziswiler.com
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Add OSPI NAND DFU partitions so as to be able to update images via dfu mtd backend.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
|
OSPI NAND belongs to spi-nand class of MTD devices and thus needs to be
assigned to spi-nand0. Without this mtdparts fails to list any
partitions.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
|
Add DFU support over GPMC NAND by providing necessary
dfu_alt_info_nand environment.
Signed-off-by: Nitin Yadav <n-yadav@ti.com>
|
|
Add support for AM62Q NAND card: X8 NAND EXPANSION
BOARD card (PROC143E1) for AM62x LP SK board. These
changes provide NAND Device configuration for AM62x
LP-SK board.
Signed-off-by: Nitin Yadav <n-yadav@ti.com>
|
|
Add UBIFS related environment variable to enable kernel
boot from UBIFS on GPMC NAND.
Signed-off-by: Nitin Yadav <n-yadav@ti.com>
|
|
Include GPMC NAND id in mtdids and Add GPMC NAND partition
partition table into mtdparts along with OSPI NAND.
Signed-off-by: Nitin Yadav <n-yadav@ti.com>
|
|
At first SPI transfers, multiple chip selects can be
enabled simultaneously. This is due to chip select
polarity, which is not properly initialized for all
channels. This patch fixes the issue.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
|
|
Since K3 devices are moving towards distroboot, remove duplicates and
add it in common file to import from.
Reviewed-by: Nikhil M Jain <n-jain1@ti.com>
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
|
|
This is helpful to go forward with distro_bootcmd as default boot.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
|
|
Some miscellaneous cleanups for boards.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
|
|
Lanes 0 and 2 of the J721S2 SerDes WIZ are reserved for USB type-C
lane swap if Lanes 1 and 3 are connected to the SerDes IP's USB PHY.
Remove the defines that state the Lane 0 and Lane 2 IPs are unused,
and instead define the Type C swap configuration macro.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
|
|
Use .env to fetch DFU args instead of .h file, while at that drop
redundant mmc.h inclusion
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
|
Drop the trail ";" as per the syntax at [0]. Else this results in error
when running dfu cmds
[0] doc/usage/dfu.rst
Fixes: 3e85631db7c5 ("include: environment: ti: Use .env for environment variables")
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
