style: normalize Android RST indentation

Signed-off-by: Julio <juliosuas@gmail.com>

Author: juliosuas

source/android/Application_Notes_Android_Secure_Build.rst

@@ -12,7 +12,7 @@ The process is an example, feel free to adapt following your needs.
 
    This process is only supported with Android user images
 
-Fetching Bootloader, Kernel, and Android
+Fetching boot loader, Kernel, and Android
 ----------------------------------------
 
 - Bootloaders:
@@ -131,22 +131,22 @@ Build and copy secure images to Android:
 
 .. note::
 
-    **RPMB corruptions**:
+   **RPMB corruptions**:
 
-    If we do several flashes with different builds, we may be faced with RPMB corruptions.
-    Indeed some metadata are stored in the RPMB and by default if there is a mismatch OP-TEE fails to load Trusted Applications.
-    Thus the OP-TEE keymaster service fails and the device doesn't boot.
-    To avoid this situation we can add the flag ``CFG_REE_FS_ALLOW_RESET=y`` in `build_optee.sh`:
+   If we do several flashes with different builds, we may be faced with RPMB corruptions.
+   Indeed some metadata are stored in the RPMB and by default if there is a mismatch OP-TEE fails to load Trusted Applications.
+   Thus the OP-TEE keymaster service fails and the device doesn't boot.
+   To avoid this situation we can add the flag ``CFG_REE_FS_ALLOW_RESET=y`` in `build_optee.sh`:
 
-        Allow secure storage in the REE FS to be entirely deleted without causing anti-rollback errors.
-        This is used to reset the secure storage to a clean, empty state.
+      Allow secure storage in the REE FS to be entirely deleted without causing anti-rollback errors.
+      This is used to reset the secure storage to a clean, empty state.
 
-    **Testing Case**:
+   **Testing Case**:
 
-    If you want to test and be sure to reuse RPMB partition you can set ``CFG_RPMB_TESTKEY=y`` in `build_optee.sh`:
+   If you want to test and be sure to reuse RPMB partition you can set ``CFG_RPMB_TESTKEY=y`` in `build_optee.sh`:
 
-        OP-TEE can either embed a built-in RPMB key or derive it from platform specific secrets.
-        The former case might be useful during development while the later is recommended for production devices.
+      OP-TEE can either embed a built-in RPMB key or derive it from platform specific secrets.
+      The former case might be useful during development while the later is recommended for production devices.
 
 Copy ``avb.key`` in Android:
 

source/android/Application_Notes_Camera.rst

@@ -23,9 +23,9 @@ The following hardware is required to use the CSI-2 camera:
 
 - ALINX ov5640 sensor module (AN5641)
 
-  .. image:: /images/alinx_ov5640.jpg
-    :width: 300
-    :alt: alinx_ov5640
+   .. image:: /images/alinx_ov5640.jpg
+      :width: 300
+      :alt: alinx_ov5640
 
 .. ifconfig:: CONFIG_part_variant in ('AM62X')
 

source/android/Application_Notes_Sample_Maps_App.rst

@@ -29,15 +29,15 @@ Launching the app
 
 .. ifconfig:: CONFIG_part_variant in ('AM62X')
 
-      * Boot the EVM with binaries built using ``am62x_car-bp2a-userdebug`` lunch target
+   * Boot the EVM with binaries built using ``am62x_car-bp2a-userdebug`` lunch target
 
 .. ifconfig:: CONFIG_part_variant in ('AM62PX')
 
-      * Boot the EVM with binaries built using ``am62p_car-bp2a-userdebug`` lunch target
+   * Boot the EVM with binaries built using ``am62p_car-bp2a-userdebug`` lunch target
 
 .. ifconfig:: CONFIG_part_variant in ('AM67A')
 
-      * Boot the EVM with binaries built using ``am67a_car-bp2a-userdebug`` lunch target
+   * Boot the EVM with binaries built using ``am67a_car-bp2a-userdebug`` lunch target
 
 * The SnappMaps application should be visible by default on the home screen
 

source/android/Overview_Building_the_SDK.rst

@@ -81,49 +81,49 @@ Where ``<BUILD_TARGET>`` is listed in the table below :
 
 .. ifconfig:: CONFIG_part_variant in ('AM62X')
 
-    ============================= ============================
-    Android Build type            Build target
-    ============================= ============================
-    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``
-    ============================= ============================
+   ============================= ============================
+   Android Build type            Build target
+   ============================= ============================
+   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>`` is ``am62x-bp2a-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-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``
-    ============================= ============================
+   ============================= ============================
+   Android Build type            Build target
+   ============================= ============================
+   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>`` is ``am62p-bp2a-userdebug``.
+   The recommended ``<BUILD_TARGET>`` is ``am62p-bp2a-userdebug``.
 
 .. ifconfig:: CONFIG_part_variant in ('AM67A')
 
-    ============================= ============================
-    Android Build type            Build target
-    ============================= ============================
-    AM67A-EVM Tablet userdebug       ``am67a-bp2a-userdebug``
-    AM67A-EVM Tablet user            ``am67a-bp2a-user``
-    AM67A-EVM Car userdebug          ``am67a_car-bp2a-userdebug``
-    AM67A-EVM Car user               ``am67a_car-bp2a-user``
-    ============================= ============================
+   ============================= ============================
+   Android Build type            Build target
+   ============================= ============================
+   AM67A-EVM Tablet userdebug       ``am67a-bp2a-userdebug``
+   AM67A-EVM Tablet user            ``am67a-bp2a-user``
+   AM67A-EVM Car userdebug          ``am67a_car-bp2a-userdebug``
+   AM67A-EVM Car user               ``am67a_car-bp2a-user``
+   ============================= ============================
 
-    The recommended ``<BUILD_TARGET>`` is ``am67a-bp2a-userdebug``.
+   The recommended ``<BUILD_TARGET>`` is ``am67a-bp2a-userdebug``.
 
 It's possible to customize the standard build (``m``), by passing build flags.
 For example, the following enables ADB on user builds:
 
 .. code-block:: console
 
-  $ TARGET_ADB_USER_ENABLE=true m
+   $ TARGET_ADB_USER_ENABLE=true m
 
 The following build flags are available. **Default** values are **highlighted**.
 
@@ -160,5 +160,5 @@ 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 :ref:`beagleplay-app-note`.
+   The android images generated for the AM62X-SK EVM are compatible with the Beagle Play board.
+   For flashing the Beagle Play, see the :ref:`beagleplay-app-note`.

source/android/Overview_Flashing.rst

@@ -39,8 +39,8 @@ Make sure to install the udev rules as documented:
 
 .. tip::
 
-    If Snagboot cannot be installed, it's possible to boot the initial bootloaders from an SD card.
-    Follow :ref:`android-bootloader-sdcard` if you encounter issues with Snagboot.
+   If Snagboot cannot be installed, it's possible to boot the initial bootloaders from an SD card.
+   Follow :ref:`android-bootloader-sdcard` if you encounter issues with Snagboot.
 
 
 eMMC flashing
@@ -153,7 +153,7 @@ Once the build is complete, follow the steps below to flash the images to eMMC.
 
        .. ifconfig:: CONFIG_part_variant in ('AM62PX')
 
-         .. code-block:: console
+          .. code-block:: console
 
              # If you are using binaries built locally
              $ cd out/target/product/am62p
@@ -167,7 +167,7 @@ Once the build is complete, follow the steps below to flash the images to eMMC.
 
        .. ifconfig:: CONFIG_part_variant in ('AM67A')
 
-         .. code-block:: console
+          .. code-block:: console
 
              # If you are using binaries built locally
              $ cd out/target/product/am67a
@@ -369,25 +369,25 @@ Once the build is complete, follow the steps below to flash the images to eMMC.
 
 .. tip::
 
-    If you get ``mcopy`` command not found error on Linux PC, install the ``mtools`` package:
+   If you get ``mcopy`` command not found error on Linux PC, install the ``mtools`` package:
 
-    .. code-block:: console
+   .. code-block:: console
 
       $ apt-get install mtools
 
 .. warning::
 
-    It's possible that the in-memory partition layout is still from an older system.
+   It's possible that the in-memory partition layout is still from an older system.
 
-    In that case, we can observe flashing errors similar to::
+   In that case, we can observe flashing errors similar to::
 
       writing 'tiboot3'...
       FAILED (remote: invalid partition or device)
 
-    When that happens:
+   When that happens:
 
-    1. Reboot into the newly flashed bootloader with ``$ fastboot reboot bootloader``
-    2. Restart the flashing from :ref:`U-Boot environment <step_5_flashing_instructions>`.
+   1. Reboot into the newly flashed boot loader with ``$ fastboot reboot bootloader``
+   2. Restart the flashing from :ref:`U-Boot environment <step_5_flashing_instructions>`.
 
 
 5. Once the flashing is complete, power off the board
@@ -438,4 +438,3 @@ Once the build is complete, follow the steps below to flash the images to eMMC.
 
 
 7. Board should boot the Android images now.
-

source/boards/beagle/BeagleY-AI/android/Application_Notes_BeagleY_AI.rst

@@ -43,14 +43,14 @@ Building the image
 To build the image you need to build the image for the am67a-evm.
 The kernel includes the appropriate device tree and the proper bootloaders are deployed.
 
-   .. code-block:: console
+.. code-block:: console
 
-      $ source build/envsetup.sh
-      $ lunch am67a-bp2a-user/userdebug
-      $ m TARGET_SDCARD_BOOT=true
-      $ sudo flashall --board am67a-beagley-ai --sdcard=/dev/sdX
+   $ source build/envsetup.sh
+   $ lunch am67a-bp2a-user/userdebug
+   $ m TARGET_SDCARD_BOOT=true
+   $ sudo flashall --board am67a-beagley-ai --sdcard=/dev/sdX
 
-   TARGET_SDCARD_BOOT=true is required since the beagley-ai does not have an eMMC.
+TARGET_SDCARD_BOOT=true is required since the beagley-ai does not have an eMMC.
 
 **************************
 Initial flashing procedure
@@ -125,8 +125,8 @@ Flashing Android requires to use the sdcard.
 
    .. code-block:: console
 
-     Finished. Total time: 112.819s
-     -------------------------------
-     flashing done, you can issue the 'fastboot reboot' command
+      Finished. Total time: 112.819s
+      -------------------------------
+      flashing done, you can issue the 'fastboot reboot' command
 
    At which point the board is flash and can reboot. It will boot to Android.