doc: Remove note for missing tf-m/ns target support

All nRF91 and nRF5340 boards (except the DKs) should support TF-M/_ns now. Signed-off-by: Joakim Andersson <[email protected]>
zephyrproject-rtos · Oct 10, 2023 · f2f64c2 · f2f64c2
1 parent c5e84c8
commit f2f64c2
Show file tree

Hide file tree

Showing 7 changed files with 0 additions and 21 deletions.
diff --git a/boards/arm/nrf5340_audio_dk_nrf5340/doc/index.rst b/boards/arm/nrf5340_audio_dk_nrf5340/doc/index.rst
@@ -53,9 +53,6 @@ The nrf5340_audio_dk_nrf5340_cpuapp build target provides support for the applic
 core on the nRF5340 SoC. The nrf5340_audio_dk_nrf5340_cpunet build target provides
 support for the network core on the nRF5340 SoC.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 The `Nordic Semiconductor Infocenter`_ contains the processor's information and
 the datasheet.
 

diff --git a/boards/arm/nrf9160_innblue21/doc/index.rst b/boards/arm/nrf9160_innblue21/doc/index.rst
@@ -104,9 +104,6 @@ have to set the IDAU (SPU) configuration to allow Non-Secure access to all
 CPU resources utilized by the Non-Secure application firmware. SPU
 configuration shall take place before jumping to the Non-Secure application.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 Building a Secure only application
 ==================================
 

diff --git a/boards/arm/nrf9160_innblue22/doc/index.rst b/boards/arm/nrf9160_innblue22/doc/index.rst
@@ -104,9 +104,6 @@ have to set the IDAU (SPU) configuration to allow Non-Secure access to all
 CPU resources utilized by the Non-Secure application firmware. SPU
 configuration shall take place before jumping to the Non-Secure application.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 Building a Secure only application
 ==================================
 

diff --git a/boards/arm/raytac_mdbt53_db_40_nrf5340/doc/index.rst b/boards/arm/raytac_mdbt53_db_40_nrf5340/doc/index.rst
@@ -24,9 +24,6 @@ The raytac_mdbt53_db_40_nrf5340_cpuapp build target provides support for the app
 core on the nRF5340 SoC. The raytac_mdbt53_db_40_nrf5340_cpuapp build target provides
 support for the network core on the nRF5340 SoC.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 nRF5340 SoC provides support for the following devices:
 
 * :abbr:`ADC (Analog to Digital Converter)`

diff --git a/boards/arm/raytac_mdbt53v_db_40_nrf5340/doc/index.rst b/boards/arm/raytac_mdbt53v_db_40_nrf5340/doc/index.rst
@@ -24,9 +24,6 @@ The raytac_mdbt53v_db_40_nrf5340_cpuapp build target provides support for the ap
 core on the nRF5340 SoC. The raytac_mdbt53v_db_40_nrf5340_cpuapp build target provides
 support for the network core on the nRF5340 SoC.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 nRF5340 SoC provides support for the following devices:
 
 * :abbr:`ADC (Analog to Digital Converter)`

diff --git a/boards/arm/sparkfun_thing_plus_nrf9160/doc/index.rst b/boards/arm/sparkfun_thing_plus_nrf9160/doc/index.rst
@@ -91,9 +91,6 @@ Building an application
 In most cases you'll want to use the ``ns`` target with any of the Zephyr
 or Nordic based examples.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 Some of the examples do not use secure mode, so they do not required the ``ns`` suffix.
 A great example of this is the `hello_world` below.
 

diff --git a/boards/arm/thingy53_nrf5340/doc/index.rst b/boards/arm/thingy53_nrf5340/doc/index.rst
@@ -22,9 +22,6 @@ The nrf5340dk_nrf5340_cpuapp build target provides support for the application
 core on the nRF5340 SoC. The nrf5340dk_nrf5340_cpunet build target provides
 support for the network core on the nRF5340 SoC.
 
-.. note::
-   Trusted Firmware-M (TF-M) and building the ``ns`` target is not supported for this board.
-
 The `Nordic Semiconductor Infocenter`_ contains the processor's information and
 the datasheet.