feat(linux): Update docs for AM62D 11.1 release

Update Foundation Components Kernel, UBoot, How to Guides, Overview
etc. for AM62D 11.1 release.

Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>

Author: paresh-bhagat

configs/AM62DX/AM62DX_linux_toc.txt

@@ -38,12 +38,12 @@ linux/Foundational_Components/U-Boot/Apps-SPL-Debug-OpenOCD
 linux/Foundational_Components_Kernel
 linux/Foundational_Components_Kernel_Drivers
 linux/Foundational_Components/Kernel/Kernel_Drivers/Audio
-linux/Foundational_Components/Kernel/Kernel_Drivers/EQEP
+#linux/Foundational_Components/Kernel/Kernel_Drivers/EQEP
 linux/Foundational_Components/Kernel/Kernel_Drivers/GPIO
 linux/Foundational_Components/Kernel/Kernel_Drivers/I2C
 #linux/Foundational_Components/Kernel/Kernel_Drivers/MCAN
 linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-Ethernet
-linux/Foundational_Components/Kernel/Kernel_Drivers/PWM
+#linux/Foundational_Components/Kernel/Kernel_Drivers/PWM
 #linux/Foundational_Components/Kernel/Kernel_Drivers/SPI
 #linux/Foundational_Components/Kernel/Kernel_Drivers/QSPI
 linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD
@@ -57,13 +57,15 @@ linux/Foundational_Components/Kernel/Kernel_Drivers/Watchdog
 
 linux/Foundational_Components_Kernel_Users_Guide
 linux/Foundational_Components_Kernel_LTP-DDT_Validation
-linux/Foundational_Components_Security
+#linux/Foundational_Components_Security
+#linux/Foundational_Components/System_Security/Auth_boot
 linux/Foundational_Components_Filesystem
 linux/Foundational_Components_Tools
 linux/Foundational_Components/Tools/Development_Tools
 linux/Foundational_Components/Tools/Pin_Mux_Tools
 linux/Foundational_Components/Tools/Flash_via_Fastboot
 linux/Foundational_Components_ATF
+linux/Foundational_Components_OPTEE
 
 linux/How_to_Guides
 linux/How_to_Guides_Developer_Notes

source/devices/AM62DX/linux/Overview/Download_and_Install_the_SDK.rst

@@ -83,10 +83,10 @@ by double clicking on it within your Linux host PC.
 **MCU+ SDK for RTOS/NO-RTOS**
 
 .. note::
-   AM62D Linux SDK contains only the Linux specific source and application intended
-   to run on A53/Linux core. For A53 based FreeRTOS side source and applications, refer **MCU+ SDK**
-
+   Processor SDK Linux AM62Dx has only the Linux specific source and application intended
+   to run on A53 or Linux core. For R5F and RTOS or NO-RTOS side source and applications, refer **MCU+ SDK**
+   package.
 
 **Instructions to set-up CCS**
 
-
+-  Refer MCU+SDK Installer `doc <https://software-dl.ti.com/mcu-plus-sdk/esd/AM62DX/11_01_00_16/exports/docs/api_guide_am62dx/GETTING_STARTED_BUILD.html>`__.

source/linux/Foundational_Components/Kernel/Kernel_Drivers/Audio.rst

@@ -886,7 +886,7 @@ Additional Information
     #. `Interfacing DRA7xx Audio to Analog Codecs
        <http://www.ti.com/lit/an/sprac09a/sprac09a.pdf>`__
 
-.. ifconfig:: CONFIG_part_family in ('J7_family', 'AM62X_family', 'AM62AX_family', 'AM62PX_family', 'AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('J7_family', 'AM62X_family', 'AM62AX_family', 'AM62DX_family', 'AM62PX_family', 'AM62LX_family')
 
     #. `Tools and Techniques for Audio Debugging
        <https://www.ti.com/lit/an/sprac10/sprac10.pdf>`__
@@ -911,3 +911,7 @@ Additional Information
        Differential Input/Output
        <http://www.ti.com/lit/ds/symlink/pcm3168a.pdf>`__
 
+.. ifconfig:: CONFIG_part_variant in ('AM62DX')
+
+    #. `TAD52512 - High-performance stereo audio DAC
+       <https://www.ti.com/lit/ds/symlink/tad5212.pdf>`__

source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-Ethernet.rst

@@ -41,7 +41,7 @@ of the CPSW Ethernet Subsystem:
 
    For further details regarding the CPSWng instance, refer :ref:`cpswng`
 
-.. ifconfig:: CONFIG_part_family in ('AM62X_family','AM62AX_family','AM64X_family','AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('AM62X_family','AM62AX_family','AM62DX_family','AM64X_family','AM62LX_family')
 
    CPSW3g
 
@@ -74,7 +74,7 @@ The CPSW Ethernet Subsystem supports TSN features in the following configuration
    2. The CPSWng Native Ethernet configuration of the CPSWng instance supports both MAC mode
       and Switch mode TSN features with Linux.
 
-.. ifconfig:: CONFIG_part_family in ('AM62X_family','AM62AX_family','AM64X_family','AM62PX_family','AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('AM62X_family','AM62AX_family','AM62DX_family','AM64X_family','AM62PX_family','AM62LX_family')
 
    The CPSW3g instance supports MAC mode and Switch mode TSN features with Linux.
 

source/linux/Foundational_Components/Kernel/_Users_Guide.rst

@@ -387,6 +387,8 @@ Compiling the Device Tree Binaries
     +-------------------------------------------+--------------------------------------+
     | AM62Ax SK                                 | k3-am62a7-sk.dts                     |
     +-------------------------------------------+--------------------------------------+
+    | AM62Dx EVM                                | k3-am62d2-evm.dts                    |
+    +-------------------------------------------+--------------------------------------+
     | AM62x LP SK                               | k3-am62-lp-sk.dts                    |
     +-------------------------------------------+--------------------------------------+
     | Beagle Play                               | k3-am625-beagleplay.dts              |

source/linux/Foundational_Components/U-Boot/UG-DFU.rst

@@ -244,6 +244,12 @@ platform that support USB Peripheral boot mode.
     - Connect USB Type C DRD Port (J15) on SK board to PC through USB cable
     - Power on the board
 
+.. ifconfig:: CONFIG_part_family in ('AM62DX_family')
+
+    - Set SYSBOOT switches to USB DFU boot mode (Refer to **Initialization** chapter of AM62D TRM for boot switch details)
+    - Connect USB Type C DRD Port (J25) on EVM board to PC through USB cable
+    - Power on the board
+
 .. ifconfig:: CONFIG_part_family in ('AM62LX_family')
 
     - Set SYSBOOT switches to USB DFU boot mode (Refer to **Initialization** chapter of AM62L TRM for boot switch details)
@@ -256,7 +262,7 @@ platform that support USB Peripheral boot mode.
     - Connect USB Type C DRD Port (J19) on SK board to PC through USB cable
     - Power on the board
 
-.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'J7_family', 'AM62X_family', 'AM62AX_family', 'AM62PX_family', 'AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'J7_family', 'AM62X_family', 'AM62AX_family', 'AM62DX_family', 'AM62PX_family', 'AM62LX_family')
 
     .. rubric:: On Linux host
 
@@ -320,7 +326,7 @@ platform that support USB Peripheral boot mode.
 
     Send boot images in this order: tiboot3.bin -> tispl.bin -> u-boot.img
 
-.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'AM62X_family', 'AM62AX_family', 'AM62PX_family', 'AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'AM62X_family', 'AM62AX_family', 'AM62DX_family', 'AM62PX_family', 'AM62LX_family')
 
     .. code-block:: text
 
@@ -331,7 +337,7 @@ platform that support USB Peripheral boot mode.
 
     .. note:: On Windows, if you face any issues while listing the available DFU Interfaces, try installing/updating the Generic USB DFU Drivers using `Zadig <https://zadig.akeo.ie/>`_.
 
-.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'J7_family', 'AM62X_family', 'AM62AX_family', 'AM62PX_family', 'AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'J7_family', 'AM62X_family', 'AM62AX_family', 'AM62DX_family', 'AM62PX_family', 'AM62LX_family')
 
     Move to directory containing the images and give the following commands
 
@@ -402,7 +408,7 @@ platform that support USB Peripheral boot mode.
 		host$ sudo dfu-util -R -a tispl.bin -D tispl.bin
 		host$ sudo dfu-util -R -a u-boot.img -D u-boot.img
 
-.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'AM62X_family', 'AM62AX_family', 'AM62PX_family')
+.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'AM62X_family', 'AM62AX_family', 'AM62DX_family', 'AM62PX_family')
 
     .. rubric:: On Linux host
 
@@ -458,7 +464,7 @@ platform that support USB Peripheral boot mode.
 
     .. note:: On Windows host, if `name` of the DFU Interface doesn't work, use `alt` number instead.
 
-.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'J7_family', 'AM62X_family', 'AM62AX_family', 'AM62PX_family', 'AM62LX_family')
+.. ifconfig:: CONFIG_part_family in ('AM64X_family', 'J7_family', 'AM62X_family', 'AM62AX_family', 'AM62DX_family', 'AM62PX_family', 'AM62LX_family')
 
     At this point, the board should boot to the U-Boot prompt.
 

source/linux/Foundational_Components/U-Boot/UG-General-Info.rst

@@ -552,6 +552,53 @@ Build U-Boot
          $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" am62ax_evm_a53_defconfig O=$UBOOT_DIR/out/a53
          $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" CC="$CC_64" BL31=$TFA_DIR/build/k3/lite/release/bl31.bin TEE=$OPTEE_DIR/out/arm-plat-k3/core/tee-pager_v2.bin O=$UBOOT_DIR/out/a53 BINMAN_INDIRS=$TI_LINUX_FW_DIR
 
+   .. ifconfig:: CONFIG_part_variant in ('AM62DX')
+
+      +-------------+----------------------------------+--------------------------------------------------------+--------------------------------------------------------+
+      |  Board      |            SD Boot               |                       USB DFU                          |                       USB MSC                          |
+      +=============+==================================+========================================================+========================================================+
+      |  AM62DX EVM |  | ``am62dx_evm_r5_defconfig``   |  | ``am62dx_evm_r5_defconfig am62x_r5_usbdfu.config``  |  | ``am62dx_evm_r5_defconfig am62x_r5_usbmsc.config``  |
+      |             |  | ``am62dx_evm_a53_defconfig``  |  | ``am62dx_evm_a53_defconfig``                        |  | ``am62dx_evm_a53_defconfig``                        |
+      +-------------+----------------------------------+--------------------------------------------------------+--------------------------------------------------------+
+
+      .. note::
+
+         Where to get the sources:
+
+         - ti-u-boot version: :ref:`u-boot-release-notes`
+         - ti-linux-firmware version: :ref:`ti-linux-fw-release-notes`
+         - TF-A version: :ref:`tf-a-release-notes`
+         - OP-TEE version: :ref:`optee-release-notes`
+
+      .. code-block:: console
+
+         $ export UBOOT_DIR=<path-to-ti-u-boot>
+         $ export TI_LINUX_FW_DIR=<path-to-ti-linux-firmware>
+         $ export TFA_DIR=<path-to-arm-trusted-firmware>
+         $ export OPTEE_DIR=<path-to-ti-optee-os>
+
+      .. note::
+
+         The instructions below assume all binaries are built manually. For instructions to build bl31.bin go to: :ref:`foundational-components-optee`.
+         For instructions to build tee-pager_v2.bin (bl32.bin) go to: :ref:`foundational-components-atf`. BINMAN_INDIRS can point to
+         :file:`<path-to-tisdk>/board-support/prebuilt-images` to use the pre-built binaries that come in the pre-built SDK (bl31.bin for BL31, bl32.bin for TEE).
+
+      .. code-block:: console
+
+         $ cd $UBOOT_DIR
+
+         R5
+         To build tiboot3.bin. Saved in $UBOOT_DIR/out/r5.
+         $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_32" am62dx_evm_r5_defconfig O=$UBOOT_DIR/out/r5
+         $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_32" O=$UBOOT_DIR/out/r5 BINMAN_INDIRS=$TI_LINUX_FW_DIR
+
+         A53
+         To build tispl.bin and u-boot.img. Saved in $UBOOT_DIR/out/a53. Requires bl31.bin, tee-pager_v2.bin.
+         $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" am62dx_evm_a53_defconfig O=$UBOOT_DIR/out/a53
+         $ make ARCH=arm CROSS_COMPILE="$CROSS_COMPILE_64" CC="$CC_64" BL31=$TFA_DIR/build/k3/lite/release/bl31.bin TEE=$OPTEE_DIR/out/arm-plat-k3/core/tee-pager_v2.bin O=$UBOOT_DIR/out/a53 BINMAN_INDIRS=$TI_LINUX_FW_DIR
+
+
+
    .. ifconfig:: CONFIG_part_variant in ('AM62PX')
 
       +-------------+----------------------------------+----------------------------------------------------------+--------------------------------------------------------+
@@ -659,13 +706,13 @@ Build U-Boot
       :file:`<path to folder>/ti-sysfw/` can be used. Please make sure
       to use the absolute path.
 
-.. ifconfig:: CONFIG_part_variant in ('J721E', 'J7200', 'AM62X', 'AM62AX', 'AM62PX', 'J721S2', 'J784S4','J742S2', 'J722S')
+.. ifconfig:: CONFIG_part_variant in ('J721E', 'J7200', 'AM62X', 'AM62AX', 'AM62DX', 'AM62PX', 'J721S2', 'J784S4','J742S2', 'J722S')
 
    .. note::
 
       It is also possible to pick up a custom DM binary by adding TI_DM argument pointing to the file. If not provided, it defaults to picking up the DM binary from BINMAN_INDIRS. This is only applicable to devices that utilize split firmware.
 
-.. ifconfig:: CONFIG_part_variant in ('AM65X', 'J721E', 'J7200', 'AM64X', 'AM62X', 'AM62AX', 'AM62LX', 'AM62PX', 'J721S2', 'J784S4','J742S2', 'J722S')
+.. ifconfig:: CONFIG_part_variant in ('AM65X', 'J721E', 'J7200', 'AM64X', 'AM62X', 'AM62AX', 'AM62DX', 'AM62LX', 'AM62PX', 'J721S2', 'J784S4','J742S2', 'J722S')
 
    .. rubric:: Target Images
       :name: target-images
@@ -821,6 +868,18 @@ Build U-Boot
          * tiboot3-am62ax-hs-evm.bin from <output directory>/r5
          * tispl.bin, u-boot.img from <output directory>/a53
 
+.. ifconfig:: CONFIG_part_variant in ('AM62DX')
+
+   * HS-FS
+
+     * :file:`tiboot3-am62dx-hs-fs-evm.bin` from :file:`<output directory>/r5`
+     * :file:`tispl.bin, u-boot.img` from :file:`<output directory>/a53`
+
+   * HS-SE
+
+     * :file:`tiboot3-am62dx-hs-evm.bin` from :file:`<output directory>/r5`
+     * :file:`tispl.bin, u-boot.img` from :file:`<output directory>/a53`
+
 .. ifconfig:: CONFIG_part_variant in ('AM62PX')
 
        * HS-FS
@@ -853,7 +912,7 @@ Build U-Boot
          * tispl.bin
          * u-boot.img
 
-.. ifconfig:: CONFIG_part_variant in ('AM65X', 'J721E', 'J7200', 'AM64X', 'AM62X', 'AM62AX', 'AM62PX', 'J721S2', 'J784S4','J742S2', 'J722S', 'AM62LX')
+.. ifconfig:: CONFIG_part_variant in ('AM65X', 'J721E', 'J7200', 'AM64X', 'AM62X', 'AM62AX', 'AM62DX', 'AM62PX', 'J721S2', 'J784S4','J742S2', 'J722S', 'AM62LX')
 
    .. warning::
 
@@ -2079,7 +2138,7 @@ The SRAM memory layout explains the memory used for Bootloader's operation.
             │                                      │
             └──────────────────────────────────────┘0x43c3ffff
 
-    .. ifconfig:: CONFIG_part_variant in ('AM62AX','AM62PX')
+    .. ifconfig:: CONFIG_part_variant in ('AM62AX','AM62PX','AM62DX')
 
         .. code-block:: console
 

source/linux/Foundational_Components/U-Boot/UG-UART.rst

@@ -67,7 +67,7 @@ is installed
       $ sb --ymodem $OUT_AXX/tispl.bin > $UART_BOOT_MAIN_UART < $UART_BOOT_MAIN_UART
       $ sb --ymodem $OUT_AXX/u-boot.img > $UART_BOOT_MAIN_UART < $UART_BOOT_MAIN_UART
 
-.. ifconfig:: CONFIG_part_variant in ('AM64X', 'AM62X', 'J722S', 'AM62PX')
+.. ifconfig:: CONFIG_part_variant in ('AM64X', 'AM62X', 'J722S', 'AM62PX', 'AM62DX')
 
    ROM supports booting from MAIN_UART0 via X-Modem protocol. R5 SPL, A53
    SPL and U-Boot use Y-MODEM Protocol for downloading next stages over

source/linux/How_to_Guides/Target/How_to_emmc_boot.rst

@@ -37,7 +37,7 @@ eMMC layout
       +----------------------------------+0x3A00   +-------------------------+
                    Boot0 (8 MB)                              UDA
 
-.. ifconfig:: CONFIG_part_variant in ('J721S2', 'AM62X', 'AM62PX', 'AM62AX', 'AM62LX')
+.. ifconfig:: CONFIG_part_variant in ('J721S2', 'AM62X', 'AM62PX', 'AM62AX', 'AM62DX', 'AM62LX')
 
    .. code-block:: text
 
@@ -54,7 +54,7 @@ eMMC layout
       +----------------------------------+0x3600   +-------------------------+
                    Boot0 (8 MB)                              UDA
 
-.. ifconfig:: CONFIG_part_variant not in ('AM64X', 'J7200', 'J721S2', 'AM62X', 'AM62PX', 'AM62AX', 'AM62LX')
+.. ifconfig:: CONFIG_part_variant not in ('AM64X', 'J7200', 'J721S2', 'AM62X', 'AM62PX', 'AM62AX', 'AM62DX', 'AM62LX')
 
    .. code-block:: text
 
@@ -145,7 +145,7 @@ In this example, eMMC device is ``dev 0``, to find which device is eMMC, refer t
       => fatload mmc 1 ${loadaddr} emmc/u-boot.img
       => mmc write ${loadaddr} 0x1800 0x2000
 
-.. ifconfig:: CONFIG_part_variant in ('J721S2', 'AM62X', 'J784S4','J742S2', 'J722S', 'AM62PX', 'AM62AX', 'AM62LX')
+.. ifconfig:: CONFIG_part_variant in ('J721S2', 'AM62X', 'J784S4','J742S2', 'J722S', 'AM62PX', 'AM62AX', 'AM62DX','AM62LX')
 
    .. code-block:: console
 
@@ -157,7 +157,7 @@ In this example, eMMC device is ``dev 0``, to find which device is eMMC, refer t
       => fatload mmc 1 ${loadaddr} emmc/u-boot.img
       => mmc write ${loadaddr} 0x1400 0x2000
 
-.. ifconfig:: CONFIG_part_variant not in ('AM64X', 'J7200', 'J721S2', 'AM62X', 'J784S4','J742S2', 'J722S', 'AM62PX', 'AM62AX', 'AM62LX')
+.. ifconfig:: CONFIG_part_variant not in ('AM64X', 'J7200', 'J721S2', 'AM62X', 'J784S4','J742S2', 'J722S', 'AM62PX', 'AM62AX', 'AM62DX', 'AM62LX')
 
    .. code-block:: console
 

source/linux/Overview/_Processor_SDK_Building_The_SDK.rst

@@ -228,7 +228,7 @@ Your newly built wic image will be generated in deploy-ti directory. Use :ref:`L
 
    .. note:: If trying to build tisdk-display-cluster image, add ``DISPLAY_CLUSTER_ENABLE="1"`` at the end of :file:`conf/local.conf` file before running bitbake.
 
-.. ifconfig:: CONFIG_part_variant in ('AM64X', 'AM65X', 'AM335X', 'AM437X')
+.. ifconfig:: CONFIG_part_variant in ('AM64X', 'AM62DX', 'AM65X', 'AM335X', 'AM437X')
 
    .. important::