feat(android): AM62X/AM62PX: update for Release 11.00.00

- Update build instructions for Android 16i.
- Update Release version.

Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>

Author: glaroque

source/android/Foundational_Components_Bootloaders.rst

@@ -31,7 +31,7 @@ Fetch the code using ``repo``:
 .. code-block:: console
 
    $ mkdir ${YOUR_PATH}/ti-bootloader-aosp/ && cd $_
-   $ repo init -u https://git.ti.com/git/android/manifest.git -b android15-release -m releases/RLS_10_01_01_Bootloader.xml
+   $ repo init -u https://git.ti.com/git/android/manifest.git -b android16-release -m releases/RLS_11_00_00_Bootloader.xml
    $ repo sync
 
 For more information about ``repo``, visit `Android's official
@@ -110,7 +110,7 @@ Build Instructions
 
 #. From :file:`out/am62x-sk/release`, copy the :file:`tiboot3.bin`, :file:`tispl.bin`
    and :file:`u-boot.img` generated to
-   :file:`${YOUR_PATH}/ti-aosp-15/vendor/ti/am62x/bootloader`.
+   :file:`${YOUR_PATH}/ti-aosp-16/vendor/ti/am62x/bootloader`.
 
    If not copied, the prebuilt bootloader binaries already present
    in :file:`vendor/ti/am62x/bootloader` will get used by :file:`flashall.sh` flashing script.
@@ -134,7 +134,7 @@ Build Instructions
 Release Instructions
 ********************
 
-In addition to building and copying manually to :file:`${YOUR_PATH}/ti-aosp-15`,
+In addition to building and copying manually to :file:`${YOUR_PATH}/ti-aosp-16`,
 it's also possible to automatically build **all supported variants** and copy them to Android.
 
 Assuming Android has already been downloaded following
@@ -143,7 +143,7 @@ Assuming Android has already been downloaded following
 .. code-block:: console
 
    $ cd ${YOUR_PATH}/ti-bootloader-aosp/
-   $ ./build/release_android.sh --aosp=${YOUR_PATH}/ti-aosp-15 --commit
+   $ ./build/release_android.sh --aosp=${YOUR_PATH}/ti-aosp-16 --commit
    # [...] lots of build logs later
 
 After that, rebuild Android by following :ref:`android-build-aosp` to use the new bootloaders.

source/android/Foundational_Components_Kernel.rst

@@ -7,7 +7,7 @@ Android is built around a Linux kernel. By default, Android's
 
 .. code-block:: text
 
-   ${YOUR_PATH}/ti-aosp-15/device/ti/am62x-kernel/kernel/6.6
+   ${YOUR_PATH}/ti-aosp-16/device/ti/am62x-kernel/kernel/6.12
 
 This guide describes how to rebuild and customize a Linux kernel for
 Android.
@@ -23,7 +23,7 @@ Fetch the code using ``repo``:
 .. code-block:: console
 
    $ mkdir ${YOUR_PATH}/ti-kernel-aosp/ && cd $_
-   $ repo init -u https://git.ti.com/git/android/manifest.git -b android15-release -m releases/RLS_10_01_01_Kernel.xml
+   $ repo init -u https://git.ti.com/git/android/manifest.git -b android16-release -m releases/RLS_11_00_00_Kernel.xml
    $ repo sync
 
 .. tip::
@@ -32,7 +32,7 @@ Fetch the code using ``repo``:
 
    .. code-block:: console
 
-      $ repo init -u https://git.ti.com/git/android/manifest.git -b android15-release -m releases/RLS_10_01_01_Kernel.xml --depth=1
+      $ repo init -u https://git.ti.com/git/android/manifest.git -b android16-release -m releases/RLS_11_00_00_Kernel.xml --depth=1
 
 .. _android-build-kernel:
 
@@ -45,7 +45,7 @@ tree which has been fully build and is located in:
 
 .. code-block:: text
 
-   ${YOUR_PATH}/ti-aosp-15/
+   ${YOUR_PATH}/ti-aosp-16/
 
 Building everything from scratch
 ================================
@@ -57,9 +57,8 @@ Building everything from scratch
 .. code-block:: console
 
    $ cd ${YOUR_PATH}/ti-kernel-aosp/
-   $ export TARGET_KERNEL_USE="6.6"
-   $ export DIST_DIR=${YOUR_PATH}/ti-aosp-15/device/ti/am62x-kernel/kernel/${TARGET_KERNEL_USE}
-   $ tools/bazel run //common:ti_dist -- --dist_dir=$DIST_DIR
+   $ export DIST_DIR=${YOUR_PATH}/ti-aosp-16/device/ti/am62x-kernel/kernel/6.12
+   $ ./tools/bazel run --config=ti //private/devices/ti/am6x:ti_dist -- --destdir=$DIST_DIR
 
 Re-running this command will rebuild incrementally.
 
@@ -82,9 +81,9 @@ The usual (``make menuconfig``) is done via ``bazel`` command :
 .. code-block:: console
 
    $ cd ${YOUR_PATH}/ti-kernel-aosp/
-   $ tools/bazel run //common:ti_config -- menuconfig
+   $ tools/bazel run --config=ti //private/devices/ti/am6x:ti_config -- menuconfig
 
-This will automatically update the :file:`arch/arm64/configs/ti_gki.fragment`.
+This will automatically update the :file:`private/devices/ti/am6x/ti.fragment`.
 
 .. note::
 
@@ -111,9 +110,9 @@ In order to flash a new kernel, several images should be flashed:
    < Wait for fastbootd reboot >
 
    $ cd <PATH/TO/IMAGES>
-   $ fastboot flash boot boot.img
-   $ fastboot flash vendor_boot vendor_boot.img
-   $ fastboot flash vendor_dlkm vendor_dlkm.img
+   $ fastboot flash boot boot.img --disable-verity
+   $ fastboot flash vendor_boot vendor_boot.img --disable-verity
+   $ fastboot flash vendor_dlkm vendor_dlkm.img --disable-verity
    $ fastboot reboot
 
 The board should boot with the new kernel.
@@ -130,28 +129,35 @@ To enable new modules:
 
    #. Run ``menuconfig`` as documented previously, Select ``=m`` for the driver.
 
-   #. Edit :file:`${YOUR_PATH}/ti-kernel-aosp/BUILD.bazel` to add your new module.
-      Look for the following section:
+   #. Edit :file:`${YOUR_PATH}/ti-kernel-aosp/private/ti/device/am6x/BUILD.bazel` to add your new module.
+      Look for the following sections:
 
       .. code-block:: bazel
 
-         _TI_MODULE_OUTS = [
+         TI_IN_TREE_MODULES = [
              # keep sorted
-             "crypto/af_alg.ko",
-             "crypto/algif_hash.ko",
+             "crypto/crc64_iso3309_generic.ko",
+             "drivers/char/hw_random/optee-rng.ko",
+             "drivers/clk/keystone/sci-clk.ko",
+             ...
+         ]
 
-   #. In the ``_TI_MODULE_OUTS`` array, add the path to your new kernel module.
+         TI_VENDOR_DLKM_MODULES = [
+             # keep sorted
+             "am65-cpts.ko",
+             "cc33xx.ko",
+             "cdns-usb-common.ko",
+             ...
+         ]
 
-   #. Rebuild the kernel as documented in :ref:`android-build-kernel`.
+   #. Add your new kernel module to the appropriate array:
 
-   #. If the driver module needs to be loaded early (in the ramdisk), edit
-      :file:`${YOUR_PATH}/ti-aosp-15/device/ti/am62x/BoardConfig-common.mk`
-      and add the path to your module:
+      - **TI_IN_TREE_MODULES**: For in-tree kernel modules. Use the full path from kernel root (e.g., ``"drivers/your_driver/your_module.ko"``)
+      - **TI_VENDOR_DLKM_MODULES**: For vendor-specific dynamically loadable kernel modules. Use only the module filename (e.g., ``"your_module.ko"``)
 
-      .. code-block:: make
+      Keep the list sorted alphabetically.
 
-         BOARD_VENDOR_RAMDISK_KERNEL_MODULES += \
-                 device/ti/am62x-kernel/kernel/$(TARGET_KERNEL_USE)/your_module.ko
+   #. Rebuild the kernel as documented in :ref:`android-build-kernel`.
 
    #. Finally, rebuild the Android images.
 
@@ -170,87 +176,77 @@ As listed in :ref:`android-dtbo`, we can configure an overlay to be applied
 from U-Boot by setting the ``adtbo_idx`` variable.
 
 To view how the ``adtbo_idx`` maps with the dtbo file, we can inspect the :file:`BUILD.bazel`
-from the `kernel source code <https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/BUILD.bazel?h=ti-android-linux-6.6.y#n953>`__.
-Looking at the ``kernel_images()`` macro, we can see:
+from the `kernel source code <https://git.ti.com/cgit/android/kernel-ti-device/tree/BUILD.bazel?h=ti-android-linux-6.12.y>`__.
+Looking at the ``TI_DTBOS`` array, we can see:
 
 .. code-block:: bazel
 
-   kernel_images(
-    name = "ti_images",
-    build_dtbo = True,
-    build_initramfs = True,
-    dtbo_srcs = [
-        ":ti/k3-am62x-sk-hdmi-audio.dtbo",
-        ":ti/k3-am62x-sk-csi2-ov5640.dtbo",
-        ":ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo",
-        ":ti/k3-am625-sk-microtips-mf101hie-panel.dtbo",
-        ":ti/k3-am62x-sk-lpm-wkup-sources.dtbo",
-        ":ti/k3-am62-lp-sk-microtips-mf101hie-panel.dtbo",
-        ":ti/k3-am625-beagleplay-csi2-ov5640.dtbo",
-        ":ti/k3-am625-beagleplay-csi2-tevi-ov5640.dtbo",
-        ":ti/k3-am625-beagleplay-lincolntech-lcd185-panel.dtbo",
-        ":ti/k3-am62p5-sk-mcan.dtbo",
-        ":ti/k3-am62p5-sk-microtips-mf101hie-panel.dtbo",
-        ":ti/k3-am625-sk-m2-cc3301.dtbo",
-        ":ti/k3-am62p5-sk-m2-cc3301.dtbo",
-        ":ti/k3-am625-sk-wl1837.dtbo",
-
-The ``dtbo_srcs`` array order dicates the index. For example:
+   TI_DTBOS = [
+       "k3-am62x-sk-hdmi-audio.dtbo",
+       "k3-am62x-sk-csi2-ov5640.dtbo",
+       "k3-am62x-sk-csi2-tevi-ov5640.dtbo",
+       "k3-am625-sk-microtips-mf101hie-panel.dtbo",
+       "k3-am62x-sk-lpm-wkup-sources.dtbo",
+       "k3-am62-lp-sk-microtips-mf101hie-panel.dtbo",
+       "k3-am625-beagleplay-csi2-ov5640.dtbo",
+       "k3-am625-beagleplay-csi2-tevi-ov5640.dtbo",
+       "k3-am625-beagleplay-lincolntech-lcd185-panel.dtbo",
+       "k3-am62p5-sk-mcan.dtbo",
+       "k3-am62p5-sk-microtips-mf101hie-panel.dtbo",
+       "k3-am625-sk-m2-cc3351.dtbo",
+       "k3-am62p5-sk-m2-cc3351.dtbo",
+       "k3-am625-sk-wl1837.dtbo",
+       "k3-am62p5-sk-dsi-rpi-7inch-panel.dtbo",
+       "k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo",
+       "k3-j722s-evm-csi2-quad-tevi-ov5640.dtbo",
+       "k3-j722s-evm-dsi-rpi-7inch-panel.dtbo",
+       "k3-j722s-evm-fpdlink-fusion.dtbo",
+   ]
+
+The ``TI_DTBOS`` array order dictates the index. For example:
 
 .. list-table::
    :header-rows: 1
 
    * - filename
      - index
 
-   * - :file:`ti/k3-am62x-sk-hdmi-audio.dtbo`
+   * - :file:`k3-am62x-sk-hdmi-audio.dtbo`
      - 0
 
-   * - :file:`ti/k3-am62x-sk-csi2-ov5640.dtbo`
+   * - :file:`k3-am62x-sk-csi2-ov5640.dtbo`
      - 1
 
+   * - :file:`k3-am62x-sk-csi2-tevi-ov5640.dtbo`
+     - 2
 
-Adding more :file:`.dtbo` files to the :file:`dtbo.img`
-=======================================================
+   * - :file:`k3-am625-sk-microtips-mf101hie-panel.dtbo`
+     - 3
 
-In this section, we will see how to add more :file:`.dtbo` files to the :file:`dtbo.img`.
-Let's see how to add :file:`ti/k3-am62p5-sk-dsi-rpi-7inch-panel.dtbo` for example:
+   * - :file:`k3-am62x-sk-lpm-wkup-sources.dtbo`
+     - 4
 
-   #. Edit :file:`${YOUR_PATH}/ti-kernel-aosp/BUILD.bazel`.
-      Look for the following section:
 
-      .. code-block:: bazel
-
-         kernel_build(
-             name = "ti",
-             outs = [
-                 "Image",
-                 "System.map",
-                 "k3-am62-lp-sk.dtb",
-                 "k3-am62-lp-sk-microtips-mf101hie-panel.dtbo",
-
-   #. In the ``kernel_build()`` section, add ``k3-am62p5-sk-dsi-rpi-7inch-panel.dtbo`` to the ``outs`` array.
+Adding more :file:`.dtbo` files to the :file:`dtbo.img`
+=======================================================
 
-   #. Still in ``kernel_build()``, look for the ``make_goals`` array and add ``ti/k3-am62p5-sk-dsi-rpi-7inch-panel.dtbo``.
+In this section, we will see how to add more :file:`.dtbo` files to the :file:`dtbo.img`.
 
-   #. Now look for the following section:
+   #. Edit :file:`${YOUR_PATH}/ti-kernel-aosp/private/ti/device/am6x/BUILD.bazel`.
+      Look for the ``TI_DTBOS`` array and add your new dtbo file:
 
       .. code-block:: bazel
 
-         kernel_images(
-             name = "ti_images",
-             build_dtbo = True,
-             build_initramfs = True,
-             dtbo_srcs = [
-                 ":ti/k3-am62x-sk-hdmi-audio.dtbo",
-                 ":ti/k3-am62x-sk-csi2-ov5640.dtbo",
-                 ":ti/k3-am62x-sk-csi2-tevi-ov5640.dtbo",
-
-   #. In the ``kernel_images()``, add ``:ti/k3-am62p5-sk-dsi-rpi-7inch-panel.dtbo`` at the end of the array.
+         TI_DTBOS = [
+             "k3-am62x-sk-hdmi-audio.dtbo",
+             "k3-am62x-sk-csi2-ov5640.dtbo",
+             ...
+             "your-new-overlay.dtbo",  # Add your new dtbo here
+         ]
 
       .. important::
 
-         Make sure to add the it at the **end** of the array. The order in ``dtbo_srcs`` will determine
+         Make sure to add it at the **end** of the array. The order in ``TI_DTBOS`` will determine
          the ``adtbo_idx`` to be used.
 
    #. Rebuild the kernel as documented in :ref:`android-build-kernel`.

source/android/Foundational_Components_OTA.rst

@@ -22,7 +22,7 @@ OTA via ``adb sideload``
 
       .. code-block:: console
 
-         $ cd ${YOUR_PATH}/ti-aosp-15
+         $ cd ${YOUR_PATH}/ti-aosp-16
          $ source build/envsetup.sh
          $ lunch <BUILD_TARGET>
          $ export DIST_DIR=./dist_output

source/android/Overview_Building_the_SDK.rst

@@ -32,15 +32,15 @@ Create a folder for downloading all sources
 
 .. code-block:: console
 
-   $ mkdir ~/10_01_00 && cd $_
+   $ mkdir ~/11_00_00 && cd $_
    $ export YOUR_PATH=$PWD
 
 Fetch the code using ``repo``:
 
 .. code-block:: console
 
-   $ mkdir ${YOUR_PATH}/ti-aosp-15 && cd $_
-   $ repo init -u https://git.ti.com/git/android/manifest.git -b android15-release -m releases/RLS_10_01_01.xml
+   $ mkdir ${YOUR_PATH}/ti-aosp-16 && cd $_
+   $ repo init -u https://git.ti.com/git/android/manifest.git -b android16-release -m releases/RLS_11_00_00.xml
    $ repo sync
 
 .. tip::
@@ -63,7 +63,7 @@ Build Instructions
 
 .. code-block:: console
 
-   $ cd ${YOUR_PATH}/ti-aosp-15
+   $ cd ${YOUR_PATH}/ti-aosp-16
    $ source build/envsetup.sh
    $ lunch <BUILD_TARGET>
    $ m
@@ -77,26 +77,26 @@ Where ``<BUILD_TARGET>`` is listed in the table below :
     ============================= ============================
     Android Build type            Build target
     ============================= ============================
-    AM62X-SK Tablet userdebug       ``am62x-ap4a-userdebug``
-    AM62X-SK Tablet user            ``am62x-ap4a-user``
-    AM62X-SK Car userdebug          ``am62x_car-ap4a-userdebug``
-    AM62X-SK Car user               ``am62x_car-ap4a-user``
+    AM62X-SK Tablet userdebug       ``am62x-bp2a-userdebug``
+    AM62X-SK Tablet user            ``am62x-bp2a-user``
+    AM62X-SK Car userdebug          ``am62x_car-bp2a-userdebug``
+    AM62X-SK Car user               ``am62x_car-bp2a-user``
     ============================= ============================
 
-    The recommended ``<BUILD_TARGET>`` to use is ``am62x-ap4a-userdebug``.
+    The recommended ``<BUILD_TARGET>`` is ``am62x-bp2a-userdebug``.
 
 .. ifconfig:: CONFIG_part_variant in ('AM62PX')
 
     ============================= ============================
     Android Build type            Build target
     ============================= ============================
-    AM62PX-SK Tablet userdebug       ``am62p-ap4a-userdebug``
-    AM62PX-SK Tablet user            ``am62p-ap4a-user``
-    AM62PX-SK Car userdebug          ``am62p_car-ap4a-userdebug``
-    AM62PX-SK Car user               ``am62p_car-ap4a-user``
+    AM62PX-SK Tablet userdebug       ``am62p-bp2a-userdebug``
+    AM62PX-SK Tablet user            ``am62p-bp2a-user``
+    AM62PX-SK Car userdebug          ``am62p_car-bp2a-userdebug``
+    AM62PX-SK Car user               ``am62p_car-bp2a-user``
     ============================= ============================
 
-    The recommended ``<BUILD_TARGET>`` to use is ``am62p-ap4a-userdebug``.
+    The recommended ``<BUILD_TARGET>`` is ``am62p-bp2a-userdebug``.
 
 It's possible to customize the standard build (``m``), by passing build flags.
 For example, the following enables ADB on user builds:
@@ -121,7 +121,7 @@ The following build flags are available. **Default** values are **highlighted**.
      - Boot from SD card instead of eMMC
 
 After building is complete, the necessary images will be available in
-:file:`${YOUR_PATH}/ti-aosp-15/out/target/product/am62*/`.
+:file:`${YOUR_PATH}/ti-aosp-16/out/target/product/am62*/`.
 
 To proceed to flash Android, see :ref:`android-flashing`.
 
@@ -138,6 +138,4 @@ To proceed to flash Android, see :ref:`android-flashing`.
 .. ifconfig:: CONFIG_part_variant in ('AM62X')
 
     The android images generated for the AM62X-SK EVM are compatible with the Beagle Play board.
-    For flashing the Beagle Play, see the `dedicated application note`_.
-
-    .. _dedicated application note: ../devices/AM62X/android/Application_Notes_BeaglePlay.html
+    For flashing the Beagle Play, see the :ref:`beagleplay-app-note`.