diff --git a/components/spi_flash/Kconfig b/components/spi_flash/Kconfig
index 4cc4964a94..1d5a44c335 100644
--- a/components/spi_flash/Kconfig
+++ b/components/spi_flash/Kconfig
@@ -108,14 +108,6 @@ menu "Main Flash configuration"
                 Also refer to `Concurrency Constraints for Flash on SPI1` > `Flash Auto Suspend Feature`
                 before enabling this option.
 
-        config SPI_FLASH_SUSPEND_TSUS_VAL_US
-            int "SPI flash tSUS value (refer to chapter AC CHARACTERISTICS)"
-            default 50
-            range 20 100
-            help
-                This config is used for setting Tsus parameter. Tsus means CS# high to next command after
-                suspend. You can refer to the chapter of AC CHARACTERISTICS of flash datasheet.
-
         config SPI_FLASH_FORCE_ENABLE_XMC_C_SUSPEND
             bool "Enable XMC-C series flash chip suspend feature anyway"
             default n
diff --git a/docs/en/migration-guides/release-5.x/5.2/storage.rst b/docs/en/migration-guides/release-5.x/5.2/storage.rst
index 31bda41700..3547fa5604 100644
--- a/docs/en/migration-guides/release-5.x/5.2/storage.rst
+++ b/docs/en/migration-guides/release-5.x/5.2/storage.rst
@@ -9,3 +9,8 @@ NVS Encryption
 - For SoCs with the HMAC peripheral (``SOC_HMAC_SUPPORTED``), turning on :doc:`../../../security/flash-encryption` will no longer automatically turn on :doc:`../../../api-reference/storage/nvs_encryption`.
 - You will need to explicitly turn on NVS encryption and select the required scheme (flash encryption-based or HMAC peripheral-based). You can select the HMAC peripheral-based scheme (:ref:`CONFIG_NVS_SEC_KEY_PROTECTION_SCHEME`), even if flash encryption is not enabled.
 - SoCs without the HMAC peripheral will still automatically turn on NVS encryption when flash encryption is enabled.
+
+SPI Flash Driver
+^^^^^^^^^^^^^^^^
+
+XMC-C series flash suspend support has been removed. According to feedback from the flash manufacturer, in some situations the XMC-C flash would require a 1ms interval between resume and next command. This is too long for a software request. Based on the above reason, in order to use suspend safely, we decide to remove flash suspend support from XMC-C series. But you can still force enable it via `CONFIG_SPI_FLASH_FORCE_ENABLE_XMC_C_SUSPEND`. If you have any questions, please contact espressif business support.
diff --git a/docs/zh_CN/migration-guides/release-5.x/5.2/storage.rst b/docs/zh_CN/migration-guides/release-5.x/5.2/storage.rst
index 0173765c92..a4f10b2a84 100644
--- a/docs/zh_CN/migration-guides/release-5.x/5.2/storage.rst
+++ b/docs/zh_CN/migration-guides/release-5.x/5.2/storage.rst
@@ -9,3 +9,8 @@ NVS 加密
 - 在集成 HMAC 外设 (``SOC_HMAC_SUPPORTED``) 的 SoC 上，启用 :doc:`../../../security/flash-encryption` 时将不再自动启用 :doc:`../../../api-reference/storage/nvs_encryption`。
 - 因此需显式启用 NVS 加密，并按照需要选择基于 flash 加密或基于 HMAC 外设的方案。即使未启用 flash 加密，也可选择基于 HMAC 外设的方案 (:ref:`CONFIG_NVS_SEC_KEY_PROTECTION_SCHEME`)。
 - 启用 flash 加密后，未集成 HMAC 外设的 SoC 仍会自动启用 NVS 加密。
+
+SPI flash 驱动
+^^^^^^^^^^^^^^^^^^^^^^
+
+XMC-C 系列闪存 suspend 功能的支持已被移除。根据闪存制造商的反馈，在某些情况下，XMC-C 闪存需要在 resume 和下一条命令之间间隔 1 毫秒。这对于软件请求来说时间太长。基于上述原因，为了安全使用 suspend 功能，我们决定取消对 XMC-C 系列闪存挂起的支持。但是你依旧可以通过打开 `CONFIG_SPI_FLASH_FORCE_ENABLE_XMC_C_SUSPEND` 来强行使能这个功能。如果您有任何疑问，请联系 espressif 商务支持。