arch/risc-v: Fix Kconfig style

- Remove spaces from Kconfig

- Add TABs

Signed-off-by: simbit18 <simbit18@gmail.com>

Author: simbit18

arch/risc-v/src/esp32p4/Kconfig

@@ -8,88 +8,90 @@ if ARCH_CHIP_ESP32P4
 source "arch/risc-v/src/common/espressif/Kconfig"
 
 config ESP32P4_SELECTS_REV_LESS_V3
-  bool "Select ESP32-P4 revisions <3.0 (No >=3.x Support)"
-  default n
-  ---help---
-    Select this option to support ESP32-P4 revisions 0.x and 1.x.
-    Revisions higher than 3.0 (included) and revisions less than 3.0
-    have huge hardware difference.
-    Revisions higher than 3.0 (included) is not compatible with 0.x and 1.x.
+	bool "Select ESP32-P4 revisions <3.0 (No >=3.x Support)"
+	default n
+	---help---
+		Select this option to support ESP32-P4 revisions 0.x and 1.x.
+		Revisions higher than 3.0 (included) and revisions less than 3.0
+		have huge hardware difference.
+		Revisions higher than 3.0 (included) is not compatible with 0.x and 1.x.
 
 choice ESP32P4_REV_MIN
-  prompt "Minimum Supported ESP32-P4 Revision"
-  default ESP32P4_REV_MIN_1
-  ---help---
-    Required minimum chip revision. ESP-IDF will check for it and
-    reject to boot if the chip revision fails the check.
-    This ensures the chip used will have some modifications (features, or bugfixes).
+	prompt "Minimum Supported ESP32-P4 Revision"
+	default ESP32P4_REV_MIN_1
+	---help---
+		Required minimum chip revision. ESP-IDF will check for it and
+		reject to boot if the chip revision fails the check.
+		This ensures the chip used will have some modifications (features, or bugfixes).
 
-    The complied binary will only support chips above this revision,
-    this will also help to reduce binary size.
+		The complied binary will only support chips above this revision,
+		this will also help to reduce binary size.
 
 config ESP32P4_REV_MIN_0
-  depends on ESP32P4_SELECTS_REV_LESS_V3
-  bool "Rev v0.0"
+	depends on ESP32P4_SELECTS_REV_LESS_V3
+	bool "Rev v0.0"
 
 config ESP32P4_REV_MIN_1
-  depends on ESP32P4_SELECTS_REV_LESS_V3
-  bool "Rev v0.1"
+	depends on ESP32P4_SELECTS_REV_LESS_V3
+	bool "Rev v0.1"
 
 config ESP32P4_REV_MIN_100
-  depends on ESP32P4_SELECTS_REV_LESS_V3
-  bool "Rev v1.0"
+	depends on ESP32P4_SELECTS_REV_LESS_V3
+	bool "Rev v1.0"
 
 config ESP32P4_REV_MIN_300
-  bool "Rev v3.0"
-  depends on !ESP32P4_SELECTS_REV_LESS_V3
+	bool "Rev v3.0"
+	depends on !ESP32P4_SELECTS_REV_LESS_V3
 
-endchoice
+endchoice # ESP32P4_REV_MIN
 
 config ESP32P4_REV_MIN_FULL
-  int
-  default 0 if ESP32P4_REV_MIN_0
-  default 1 if ESP32P4_REV_MIN_1
-  default 100 if ESP32P4_REV_MIN_100
-  default 300 if ESP32P4_REV_MIN_300
+	int
+	default 0 if ESP32P4_REV_MIN_0
+	default 1 if ESP32P4_REV_MIN_1
+	default 100 if ESP32P4_REV_MIN_100
+	default 300 if ESP32P4_REV_MIN_300
 
 config ESP_REV_MIN_FULL
-  int
-  default ESP32P4_REV_MIN_FULL
+	int
+	default ESP32P4_REV_MIN_FULL
 
 config ESP32P4_REV_MAX_FULL
-  int
-  default 399 if !ESP32P4_SELECTS_REV_LESS_V3
-  default 199 if ESP32P4_SELECTS_REV_LESS_V3
-  # keep in sync the "Maximum Supported Revision" description with this value
+	int
+	default 399 if !ESP32P4_SELECTS_REV_LESS_V3
+	default 199 if ESP32P4_SELECTS_REV_LESS_V3
+
+# keep in sync the "Maximum Supported Revision" description with this value
 
 config ESP_REV_MAX_FULL
-  int
-  default ESP32P4_REV_MAX_FULL
+	int
+	default ESP32P4_REV_MAX_FULL
 
 config ESP_EFUSE_BLOCK_REV_MIN_FULL
-  int "Minimum Supported ESP32-P4 eFuse Block Revision"
-  default 0
-  ---help---
-    Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
-    whether the current image can work correctly for this eFuse Block revision.
-    So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
-    If you want to update this value to run the image that not compatible with the current eFuse Block revision,
-    please contact to Espressif's business team for details:
-    https://www.espressif.com.cn/en/contact-us/sales-questions
+	int "Minimum Supported ESP32-P4 eFuse Block Revision"
+	default 0
+	---help---
+		Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+		whether the current image can work correctly for this eFuse Block revision.
+		So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+		If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+		please contact to Espressif's business team for details:
+		https://www.espressif.com.cn/en/contact-us/sales-questions
 
 config ESP_EFUSE_BLOCK_REV_MAX_FULL
-  int
-  default 199
-  comment "Maximum Supported ESP32-P4 eFuse Block Revision (eFuse Block Rev v0.99)"
-  # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL
+	int
+	default 199
+	comment "Maximum Supported ESP32-P4 eFuse Block Revision (eFuse Block Rev v0.99)"
+
+# The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL
 
 endif # ARCH_CHIP_ESP32P4
 
 config P4_REV3_MSPI_CRASH_AFTER_POWER_UP_WORKAROUND
-  bool
-  default y if ESP32P4_REV_MIN_300
+	bool
+	default y if ESP32P4_REV_MIN_300
 
 config P4_REV3_MSPI_WORKAROUND_SIZE
-  hex
-  default 0x100 if ESP32P4_REV_MIN_300
-  default 0
+	hex
+	default 0x100 if ESP32P4_REV_MIN_300
+	default 0