fixup! nrf_security: Make PSA SSF client independent

nrfconnect · Oct 1, 2024 · 827893f · 827893f
1 parent 0ccf135
commit 827893f
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/subsys/nrf_security/CMakeLists.txt b/subsys/nrf_security/CMakeLists.txt
@@ -37,7 +37,7 @@ if(CONFIG_BUILD_WITH_TFM)
   include(${NRF_SECURITY_ROOT}/cmake/config_to_tf-m.cmake)
 endif()
 
-if(CONFIG_BUILD_WITH_TFM OR (CONFIG_NRF_PSA_SSF_CRYPTO_CLIENT AND CONFIG_NRF_SECURITY))
+if(CONFIG_BUILD_WITH_TFM OR (CONFIG_PSA_SSF_CRYPTO_CLIENT AND CONFIG_NRF_SECURITY))
   # We enable either TF-M or the SSF client PSA crypto interface but we are
   # not in the secure image build
 

diff --git a/subsys/nrf_security/Kconfig b/subsys/nrf_security/Kconfig
@@ -30,7 +30,7 @@ config NORDIC_SECURITY_BACKEND
 	  Note that this will enable nrf_oberon by default. Multiple backends is
 	  not supported.
 
-config NRF_PSA_SSF_CRYPTO_CLIENT
+config PSA_SSF_CRYPTO_CLIENT
 	bool
 	prompt "PSA crypto provided through SSF"
 	default y

diff --git a/subsys/nrf_security/src/CMakeLists.txt b/subsys/nrf_security/src/CMakeLists.txt
@@ -111,7 +111,7 @@ add_library(${mbedcrypto_target}
     ${src_crypto}
 )
 
-if(CONFIG_NRF_PSA_SSF_CRYPTO_CLIENT)
+if(CONFIG_PSA_SSF_CRYPTO_CLIENT)
   add_subdirectory(ssf_secdom)
 endif()