feat(Falcon-Mode): update OSPI boot instructions

With the commit 84a83907c5c2 ("mach-k3: common: support only MMC in R5
falcon mode") in ti-u-boot[1] disabling loading of tifalcon.bin from SPI
flash, update the docs accordingly.

[1]: TexasInstruments/ti-u-boot@84a8390

Signed-off-by: Anshul Dalal <[email protected]>

Author: ArchUsr64

source/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.rst

@@ -105,22 +105,19 @@ OSPI boot:
 
 .. ifconfig:: CONFIG_part_variant not in ('AM62AX')
 
-   For OSPI boot, the :file:`tiboot3.bin` and :file:`tifalcon.bin` files should be
-   flashed to the same addresses in flash as regular boot flow but the
-   :file:`fitImage` is read from the root filesystem's boot directory. The MMC
+   For OSPI boot, the :file:`tiboot3.bin` file should be flashed to the same
+   addresses in flash as regular boot flow whereas :file:`tifalcon.bin` and the
+   :file:`fitImage` are read from the root filesystem's boot directory. The MMC
    device is selected by the ``mmcdev`` env variable for R5 SPL.
 
-   Below U-Boot commands can be used to download :file:`tiboot3.bin` and
-   :file:`tifalcon.bin` over tftp and then flash those to OSPI at their respective
-   addresses.
+   Below U-Boot commands can be used to download :file:`tiboot3.bin` over tftp
+   and then flash it to OSPI.
 
    .. code-block:: console
 
      => sf probe
      => tftp ${loadaddr} tiboot3.bin
      => sf update $loadaddr 0x0 $filesize
-     => tftp ${loadaddr} tifalcon.bin
-     => sf update $loadaddr 0x80000 $filesize
 
 .. ifconfig:: CONFIG_part_variant in ('AM62AX')