Signed-off-by: Nishanth Menon <nm@ti.com>

Fix up mmc alias as mmc0 is considered emmc and mmc1 is sdhci

Signed-off-by: Nishanth Menon <nm@ti.com>

Basic board dts support for BeagleY-AI

Add support for both DVT and EVT boards.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Nishanth Menon <nm@ti.com>

Allow other boards to reuse the binman definition by using macros for
the board names

Signed-off-by: Nishanth Menon <nm@ti.com>

Use mac address for cpsw_port1

Signed-off-by: Nishanth Menon <nm@ti.com>

Sync with kernel please

Signed-off-by: Nishanth Menon <nm@ti.com>

func(TI_MMC) is just a hack, drop it.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Nishanth Menon <nm@ti.com>

When booting Android from eMMC, loading the splashscreen file fails:

  U-Boot SPL 2023.04 (Mar 18 2024 - 13:00:32 +0000)
  SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.5--v09.02.05 (Kool Koala)')
  SPL initial stack usage: 1856 bytes
  MMC: no card present
  ** Bad device specification mmc 1 **
  Couldn't find partition mmc 1:1
  Error: could not access storage.
  Trying to boot from DFU
  Authentication passed
  Authentication passed

Since commit b66b2032 ("video: Fill video handoff in video post probe"),
U-Boot proper crashes because of this:

  U-Boot 2023.04 (Mar 18 2024 - 13:00:32 +0000)

  SoC:  AM62X SR1.0 HS-FS
  Model: Texas Instruments AM625 SK
  EEPROM not available at 80, trying to read at 81
  Board: AM62B-SKEVM-P1 rev A
  DRAM: initcall sequence 00000000808ada08 failed at call 000000008082740c (err=-2)
  ### ERROR ### Please RESET the board ###

Disable splashcreen for Android to fix the crash.

Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Reviewed-by: Devarsh Thakkar <devarsht@ti.com>

Don't propagate error on bloblist failure as it is possible that splash
logo file may not have been present in expected location since common
defconfig is being used for other bootmodes too.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Move the DM entry in tispl.bin FIT image from default fetching an
external blob entry to fetching using ti-dm entry type. This way, the
DM entry will be populated by the TI_DM pathname if provided. Else it
will resort to the ti-dm.bin file.

Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Reviewed-by: Neha Malcom Francis <n-francis@ti.com>

J7200  has SR1.0 and SR2.0 having three variants of each GP, HS-FS and
HS-SE. Current build does not generate HS-SE SR1.0 and HS-FS SR1.0 so
add support for them.

Reported-by: Suman Anna <s-anna@ti.com>
Reported-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>

J721E has SR1.1 and SR2.0 having three variants of each GP, HS-FS and
HS-SE. Current build does not generate HS-SE SR2.0 and HS-FS SR1.1 so
add support for them.

Reported-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>

- Enable BMP and Splash screen related configs
- Enable bloblist support to pass video blob from SPL stage
to U-boot proper.
- Use same memory map for enabling splash screen as used for
AM62x[1] :
-> Create space for loading bmp image file by moving the malloc
area
and BSS region down to 0x80b80000 and 0x80c80000 respectively
-> Increase the SPL size limit and SPL stack size to 512 KiB and
2KiB
respectively to accommodate splash support
-> Set stack above the malloc region and report stack overflow by
setting CONFIG_SPL_SYS_REPORT_STACK_F_USAGE
- Enable simple malloc() for A53 SPL
- Enable simplefb and fb reservation for A53 SPL

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Run `make savedefconfig` to sort the defconfig.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Enable microtips mf101hie OLDI panel and link it with DSS ports to
enable splash screen on AM62x LP SK.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

The NAND flash utility functions under CONFIG_CMD_NAND should not be
compiled at SPL stage as the underlying functions are under separate
Kconfigs viz. CONFIG_ENV_IS_IN_NAND and hence are not supported at
SPL stage right now for splash screen.

Long term, the NAND flash utility functions and their dependencies need
to be tied with splash screen specific Kconfigs too as splash logo
file can be present in NAND storage before bootup.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Update size of tiboot3.bin is exceeding allocated
area of 512KB, 1MB assigned to tiboot3.bin. Default offset for
tispl.bin will not work for OSPI NAND. Add config for tispl.bin
offset.

Signed-off-by: Apurva Nandan <a-nandan@ti.com>

commit 2764be43 ("remoteproc: uclass: Add methods to load
firmware to rproc and boot rproc") selects FS_LOADER in Kconfig
and this breaks R5 build for some defconfigs across multiple platforms.

Enabling CONFIG_SPL_FS_LOADER does not help for all cases.

Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Tested-by: MD Danish Anwar <danishanwar@ti.com>

Enable simple-framebuffer support for AM62x and AM62p platforms which
have early splash screen enabled. This updates the simple-framebuffer
node in Linux device-tree on the fly with framebuffer address and
meta-data and also reserves framebuffer region in device-tree.

Also disable the simple-framebuffer support in am62p's prune
splashscreen config fragment as it is not required without splashscreen
support.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Run `make savedefconfig` to sort the A53 defconfig files for AM62x and
AM62p.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Update simple-framebuffer device-tree node by enumerating framebuffer
related information in existing simple-framebuffer node in Linux
device-tree file and enabling it.

While at it, ignore error return value for framebuffer related DT node
updates as a non-zero return value for ft_board_setup is treated as a fatal
error causing board reset.

In case there is no simple-framebuffer stub detected in Linux kernel
device-tree and video is still active, then update the device-tree to
reserve the framebuffer region for the active splash screen.

This helps preserve the splash screen till the display server takes over
after OS is booted.

In case the simplefb node update or the framebuffer reservation fails we
treat it as a non-fatal error and avoid returning error to parent
function as the non-zero return value of ft_board_setup is treated as
fatal error which leads to board reset

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

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>

Enable and update simple-framebuffer node using the video handoff
bloblist if video was enabled at SPL stage and corresponding video
bloblist was received at u-boot proper with necessary parameters.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

If SPL is passing video handoff structure to U-boot then it is safe to
assume that SPL has already enabled video and that's why it is passing
video handoff structure to U-boot so that U-boot can preserve the
framebuffer.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Fill video handoff fields in video_post_probe as at this point we have
full framebuffer-related information.

Also fill all the fields available in video hand-off struct as those
were missing earlier and U-boot framework expects them to be filled for
some of the functionalities.

While filling framebuffer size in video hand-off structure use the
actual framebuffer region size as derived from gd->video_top and
gd->video_bottom instead of directly using the size populated in
video_uc_plat as it contains unaligned size.

Reported-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

The SDRAM_IDX in DDRSS_V2A_CTL_REG describes the number of address
bits minus 16 that are used to determine the mask used to detect
memory rollover and prevent aliasing and false coherency issues.

Set SDRAM_IDX using the device private data, ddr_ram_size for AM64x,
AM62x and AM62x SIP.

Signed-off-by: Santhosh Kumar K <s-k6@ti.com>
Acked-by: Bryan Brattlof <bb@ti.com>

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>

Factory Reset Protection (frp) is a required Android partition in order to
support factory reset via the SystemUI.

It's been added to am62x SK EVM partition list in
commit bc8e096e ("environment: ti: mmc_android: add frp partition")

Add it to the Beagle Play partitioning table as well.

Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>

commit d1857c85 ("environment: ti: mmc_android: update metadata partition")
switched the metadata partition to use f2fs file system.
This requires a size increase of the partition to avoid the following flash error:

  Flashing metadata partition
  Warning: skip copying metadata image avb footer (metadata partition size: 16777216, metadata image size: 63963136).
  Sending 'metadata' (62464 KB)                      OKAY [  2.477s]
  Writing 'metadata'                                 FAILED (remote: 'too large for partition')
  fastboot: error: Command failed

Increase the metadata partition size for Beagle Play as well.

Fixes: d1857c85 ("environment: ti: mmc_android: update metadata partition")
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>

Bump up malloc length to 3MiB for R5 SPL, as the size of tispl.bin is
increased now after introduction of splash and caching support and with
display-cluster enabled DM firmware, R5 SPL fails to load tispl.bin with
below issue :

"U-Boot SPL 2023.04-g7d05009917 (Feb 15 2024 - 18:08:11 +0000) SYSFW
ABI: 3.1 (firmware rev 0x0009 '9.2.1--v09.02.01 (Kool Koala)') SPL
initial stack usage: 17072 bytes Trying to boot from MMC2 alloc space
exhausted SPL: failed to boot from all boot devices"

Fixes: a7e8f56a ("board: ti: am62p: Add splash screen support")
Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

Fixes below warning by including cpu_funcs.h:

"board/ti/am62px/evm.c: In function `spl_board_init`:
board/ti/am62px/evm.c:83:9: warning: implicit declaration of function
`enable_caches` [-Wimplicit-function-declaration]
   83 |         enable_caches();"
      |         ^~~~~~~~~~~~~

While at it, also sort the include headers by placing video.h at the
end.

Fixes: a7e8f56a ("board: ti: am62p: Add splash screen support")
Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>

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>

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>

The default DM firmware path is non-optional as of now. Make it
optional so that users that choose to provide DM via TI_DM argument
instead of BINMAN_INDIRS can do so without build errors.

Cc: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
Tested-by: Chirag Shilwant <c-shilwant@ti.com>

Move bus-width property to *main.dtsi, above the OTAP/ITAP
delay values. While there is no error with where it is
currently at, it is easier to read the MMC node if the
bus-width property is located above the OTAP/ITAP delay
values consistently across MMC nodes.

Add missing bus-width DTS property for sdchi2 in k3-am62-main.

Signed-off-by: Judith Mendez <jm@ti.com>

Move ti,clkbuf-sel property above the OTAP/ITAP delay values.
While there is no error with where it is currently at, it is
easier to read the MMC node if ti,clkbuf-sel is located above
the OTAP/ITAP delay values consistently across MMC nodes.

Add missing ti,clkbuf-sel DTS property for sdhci0 in k3-am64-main.

Signed-off-by: Judith Mendez <jm@ti.com>

Remove DLL properties which are not applicable for soft PHYs
since these PHYs do not have a DLL to enable.

Signed-off-by: Judith Mendez <jm@ti.com>

Update MMC OTAP/ITAP values according to the datasheet
[0], refer to Table 7-79 for MMC0 and Table 7-97 for MMC1/MMC2.

[0] https://www.ti.com/lit/ds/symlink/am62p.pdf



Signed-off-by: Judith Mendez <jm@ti.com>

Update MMC0/MMC1 OTAP/ITAP delay values according to the
datasheet [0], refer to Table 7-79 for MMC0 and Table 7-97
for MMC1.

[0] https://www.ti.com/lit/ds/symlink/am62a7.pdf



Signed-off-by: Judith Mendez <jm@ti.com>

Update MMC0/MMC1 OTAP/ITAP values according to the datasheet
[0], refer to Table 7-68 for MMC0 and Table 7-77 for MMC1.

Move ITAPDLY values after OTAPDLY values to make MMC
nodes more uniform across devices.

[0] https://www.ti.com/lit/ds/symlink/am6442.pdf



Signed-off-by: Judith Mendez <jm@ti.com>