MLK-20553-4 doc: imx: hab: Remove extra hab directory for a cleaner documentation structure

There is no need to have an extra hab directory under doc/imx/:

- doc/imx/hab/ahab/
- doc/imx/hab/habv4/

Remove extra hab directory for a cleaner documentation structure.

Signed-off-by: Breno Lima <breno.lima@nxp.com>
Reviewed-by: Ye Li <ye.li@nxp.com>

doc/imx/ahab/guides/mx8_mx8x_secure_boot.txt

@@ -168,7 +168,7 @@ The CSF contains all the commands that the AHAB executes during the secure
 boot. These commands instruct the AHAB on which memory areas of the image
 to authenticate, which keys to install, use and etc.
 
-CSF examples are available under doc/imx/hab/ahab/csf_examples/
+CSF examples are available under doc/imx/ahab/csf_examples/
 directory.
 
 This csf_boot_image.txt file example should be updated with the offset values
@@ -350,7 +350,7 @@ Keep in mind the offsets above to be used with CST/CSF
 2.2 Creating the CSF description file for OS container image
 -------------------------------------------------------------
 
-CSF examples are available under doc/imx/hab/ahab/csf_examples/
+CSF examples are available under doc/imx/ahab/csf_examples/
 directory.
 
 This csf_linux_img.txt file example should be updated with the offset values

doc/imx/ahab/guides/mx8_mx8x_spl_secure_boot.txt

@@ -168,7 +168,7 @@ during the secure boot procedure. These commands instruct the AHAB code on
 which memory areas of the image to authenticate, which keys to install, use
 and etc.
 
-CSF examples are available under doc/imx/hab/ahab/csf_examples/ directory.
+CSF examples are available under doc/imx/ahab/csf_examples/ directory.
 
 As explained in section above the mkimage log provides the container and
 signature block offsets used by the CSF description file:
@@ -351,7 +351,7 @@ The lifecycle value should now be 128 (0x80) OEM closed.
 
 The procedure for authenticating the OS container is similar as in Non-SPL
 targets, for a complete procedure please refer to mx8_mx8x_secure_boot.txt
-document available under doc/imx/hab/ahab/guides/ directory.
+document available under doc/imx/ahab/guides/ directory.
 
 References:
 [1] AN12212: "Software Solutions for Migration Guide from Aarch32 to

doc/imx/ahab/introduction_ahab.txt

@@ -10,7 +10,7 @@ secure boot concept. Due to the multi-core architecture the Security
 Controller (SECO) and System Control Unit (SCU) are heavily involved in
 the secure boot process.
 
-Step-by-step guides are available under doc/imx/hab/ahab/guides/ directory,
+Step-by-step guides are available under doc/imx/ahab/guides/ directory,
 users familiar with AHAB architecture and CST PKI tree generation should
 refer to this directory instead.
 
@@ -167,7 +167,7 @@ The sequence below explains the i.MX8 and i.MX8x boot flow:
      SCU by calling the sc_misc_seco_authenticate() API function. In current
      U-Boot implementation the additional image can be the Linux Kernel binary
      or the U-Boot proper and ATF. Details about current U-Boot implementation
-     can be found in AHAB guides included in doc/imx/hab/ahab/guides/ directory.
+     can be found in AHAB guides included in doc/imx/ahab/guides/ directory.
 
 2. Generating a PKI tree
 -------------------------
@@ -297,5 +297,5 @@ Table Hash.
   SRK_1_2_3_4_table.bin
 
 The SRK_1_2_3_4_table.bin and SRK_1_2_3_4_fuse.bin files can be used in further
-steps as explained in AHAB guides available under doc/imx/hab/ahab/guides/
+steps as explained in AHAB guides available under doc/imx/ahab/guides/
 directory.

doc/imx/habv4/guides/mx6_mx7_encrypted_boot.txt

@@ -98,7 +98,7 @@ secure boot. These commands instruct the HAB on which memory areas
 of the image to authenticate, which keys to install, use, etc...
 
 CSF examples for encrypted boot are available under
-doc/imx/hab/habv4/csf_examples/ directory.
+doc/imx/habv4/csf_examples/ directory.
 
 For both CSF, first part is same compared to the CSF used for
 the secure boot step.

doc/imx/habv4/guides/mx6_mx7_secure_boot.txt

@@ -75,7 +75,7 @@ The CSF contains all the commands that the ROM executes during the secure
 boot. These commands instruct the HAB on which memory areas of the image
 to authenticate, which keys to install, use and etc.
 
-CSF examples are available under doc/imx/hab/habv4/csf_examples/ directory.
+CSF examples are available under doc/imx/habv4/csf_examples/ directory.
 
 A build log containing the "Authenticate Data" parameters is available after
 the U-Boot build, the example below is a log for mx7dsabresd_defconfig target:

doc/imx/habv4/guides/mx8m_mx8mm_secure_boot.txt

@@ -225,7 +225,7 @@ The CSF contains all the commands that the ROM executes during the secure
 boot. These commands instruct the HAB code on which memory areas of the image
 to authenticate, which keys to install, use and etc.
 
-CSF examples are available under doc/imx/hab/habv4/csf_examples/ directory.
+CSF examples are available under doc/imx/habv4/csf_examples/ directory.
 
 As explained in sections above the SPL is first authenticated by the ROM code
 and the root of trust is extended to the FIT image, hence two CSF files are

doc/imx/habv4/introduction_habv4.txt

@@ -14,7 +14,7 @@ operations.
 This feature is supported in i.MX 50, i.MX 53, i.MX 6, i.MX 7 series and
  i.MX 8M, i.MX 8MM devices.
 
-Step-by-step guides are available under doc/imx/hab/habv4/guides/ directory,
+Step-by-step guides are available under doc/imx/habv4/guides/ directory,
 users familiar with HAB and CST PKI tree generation should refer to these
 documents instead.
 
@@ -252,7 +252,7 @@ Table Hash.
 	SRK4_sha256_2048_65537_v3_ca_crt.pem
 
 The SRK_1_2_3_4_table.bin and SRK_1_2_3_4_fuse.bin files can be used in further
-steps as explained in HAB guides available under doc/imx/hab/habv4/guides/
+steps as explained in HAB guides available under doc/imx/habv4/guides/
 directory.
 
 References: