doc: nrf: update references to Zephyr documentation

Update some references with their new id. Note that most samples now
require the usage of the Zephyr Sphinx domain, enabled in this patch as
well.

Signed-off-by: Gerard Marull-Paretas <[email protected]>

Author: gmarull

applications/nrf5340_audio/doc/firmware_architecture.rst

@@ -263,7 +263,7 @@ Synchronization module flow
 The received audio data in the I2S-based firmware devices follows the following path:
 
 1. The LE Audio Controller Subsystem for nRF53 running on the network core receives the compressed audio data.
-#. The controller subsystem sends the audio data to the Zephyr Bluetooth LE host similarly to the :ref:`zephyr:bluetooth-hci-rpmsg-sample` sample.
+#. The controller subsystem sends the audio data to the Zephyr Bluetooth LE host similarly to the :ref:`zephyr:bluetooth-hci-ipc-sample` sample.
 #. The host sends the data to the stream control module.
 #. The data is sent to a FIFO buffer.
 #. The data is sent from the FIFO buffer to the :file:`audio_datapath.c` synchronization module.

doc/nrf/conf.py

@@ -48,6 +48,7 @@
     "zephyr.external_content",
     "zephyr.doxyrunner",
     "zephyr.link-roles",
+    "zephyr.domain",
     "sphinx_tabs.tabs",
     "software_maturity_table",
     "sphinx_togglebutton",

doc/nrf/device_guides/working_with_nrf/nrf52/developing.rst

@@ -78,7 +78,7 @@ Here is an example of how you can build for the :ref:`peripheral_lbs` sample:
     west build -b *build_target* -- -DCONFIG_BOOTLOADER_MCUBOOT=y -DCONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
 
 When you connect to the device after the build has completed and the firmware has been programmed to it, the SMP Service is enabled with the ``UUID 8D53DC1D-1DB7-4CD3-868B-8A527460AA84``.
-If you want to add SMP Service to advertising data, refer to the :ref:`zephyr:smp_svr_sample`.
+If you want to add SMP Service to advertising data, refer to the :zephyr:code-sample:`smp-svr`.
 
 .. fota_upgrades_over_ble_additional_information_end
 
@@ -180,11 +180,11 @@ To perform a FOTA update, complete the following steps:
 FOTA update sample
 ==================
 
-The :ref:`zephyr:smp_svr_sample` demonstrates how to set up your project to support FOTA updates.
+The :zephyr:code-sample:`smp-svr` demonstrates how to set up your project to support FOTA updates.
 
 The sample documentation is from the Zephyr project and is incompatible with the :ref:`ug_multi_image`.
 When working in the |NCS| environment, ignore the part of the sample documentation that describes the building and programming steps.
-In |NCS|, you can build and program the :ref:`zephyr:smp_svr_sample` as any other sample using the following commands:
+In |NCS|, you can build and program the :zephyr:code-sample:`smp-svr` as any other sample using the following commands:
 
 .. parsed-literal::
    :class: highlight

doc/nrf/device_guides/working_with_nrf/nrf53/nrf5340.rst

@@ -161,7 +161,7 @@ Bluetooth Low Energy
 
    * - Network core
      - Application core
-   * - :ref:`zephyr:bluetooth-hci-rpmsg-sample`
+   * - :ref:`zephyr:bluetooth-hci-ipc-sample`
      - | :ref:`Bluetooth Low Energy samples <ble_samples>`
        | :ref:`Bluetooth samples in Zephyr <zephyr:bluetooth-samples>`
    * - :ref:`ble_rpc_host` (supported for development)
@@ -177,7 +177,7 @@ Split Controller and Host
 
 When splitting the Bluetooth LE Controller and the Host, run the Bluetooth LE Controller on the network core and the host part of the Bluetooth LE stack and the application logic on the application core.
 
-For the network core, the |NCS| provides the :ref:`zephyr:bluetooth-hci-rpmsg-sample` sample.
+For the network core, the |NCS| provides the :ref:`zephyr:bluetooth-hci-ipc-sample` sample.
 This Zephyr sample is designed specifically to enable the Bluetooth LE Controller functionality on a remote MCU using the `RPMsg Messaging Protocol`_ as a transport for Bluetooth HCI.
 The sample implements the RPMsg transport using the `OpenAMP`_ library to communicate with a Bluetooth Host stack that runs on a separate core (in this case, the nRF5340 application core).
 
@@ -257,7 +257,7 @@ When using Thread or Zigbee in parallel with Bluetooth LE, run the low-level rad
    Bluetooth LE and IEEE 802.15.4 multiprotocol architecture in multicore SoC
 
 For the network core, the |NCS| provides the :ref:`multiprotocol-rpmsg-sample` sample.
-It is a combination of the :ref:`zephyr:bluetooth-hci-rpmsg-sample` sample (for Bluetooth LE) and the :ref:`zephyr:nrf-ieee802154-rpmsg-sample` sample (for IEEE 802.15.4).
+It is a combination of the :ref:`zephyr:bluetooth-hci-ipc-sample` sample (for Bluetooth LE) and the :ref:`zephyr:nrf-ieee802154-rpmsg-sample` sample (for IEEE 802.15.4).
 This means that it enables both the Bluetooth LE Controller and the nRF IEEE 802.15.4 radio driver and simultaneously exposes the functionality of both stacks to the application core using the `RPMsg Messaging Protocol`_.
 Separate RPMsg endpoints are used to obtain independent inter-core connections for each stack.
 
@@ -354,7 +354,7 @@ The combination of these options determines which (if any) sample is included in
      - Child image sample for the network core
      - Child image sample for the application core
    * - :kconfig:option:`CONFIG_BT_HCI_IPC`
-     - :ref:`zephyr:bluetooth-hci-rpmsg-sample`
+     - :ref:`zephyr:bluetooth-hci-ipc-sample`
      - ---
    * - :kconfig:option:`CONFIG_NRF_802154_SER_HOST`
      - :ref:`zephyr:nrf-ieee802154-rpmsg-sample`

doc/nrf/device_guides/working_with_nrf/nrf70/gs.rst

@@ -250,8 +250,8 @@ Testing the LEDs and buttons in the nRF7002 DK
 
 The following samples allow you to test if the buttons (or switches) and LEDs on the development kit are working properly with |NCS|:
 
-* :ref:`blinky-sample`
-* :ref:`button-sample`
+* :zephyr:code-sample:`blinky`
+* :zephyr:code-sample:`button`
 
 Build and flash the samples to make sure |NCS| is running correctly on your development kit.
 For the button and LED definitions, see the :file:`boards/arm/nrf7002dk_nrf5340/nrf5340_cpuapp_common.dts` file.

doc/nrf/libraries/bluetooth_services/services/dfu_smp.rst

@@ -11,7 +11,7 @@ This module implements a Simple Management Protocol (SMP) Service Client that ca
 SMP is a basic transfer encoding for use with the `mcumgr`_ management protocol.
 See `SMP over Bluetooth`_ for the service specification.
 
-The SMP Client module can be used to interact with Zephyr's :ref:`zephyr:smp_svr_sample`.
+The SMP Client module can be used to interact with Zephyr's :zephyr:code-sample:`smp-svr`.
 
 The SMP Client implements only the service.
 It does not provide any functionality to process or interpret SMP commands and responses.
@@ -49,12 +49,12 @@ Usage
 MTU negotiation
 ===============
 
-The current DFU SMP Server implementation in the :ref:`zephyr:smp_svr_sample` requires the whole command to be sent in one transfer.
+The current DFU SMP Server implementation in the :zephyr:code-sample:`smp-svr` requires the whole command to be sent in one transfer.
 For most operations, this requires a bigger MTU size than the default one.
 This requires MTU negotiation in the MTU exchange process (see :c:func:`bt_gatt_exchange_mtu`).
 Writing long characteristic values is not supported.
 
-This is a limitation of the :ref:`zephyr:smp_svr_sample`, not of the SMP Client.
+This is a limitation of the :zephyr:code-sample:`smp-svr`, not of the SMP Client.
 
 Sending a command
 =================

doc/nrf/releases_and_maturity/known_issues.rst

@@ -213,7 +213,7 @@ Only secure applications can use Bluetooth® LE
 .. rst-class:: v1-2-1 v1-2-0 v1-1-0
 
 :kconfig:option:`CONFIG_BT_SMP` alignment requirement
-  When running the :ref:`bluetooth_central_dfu_smp` sample, the :kconfig:option:`CONFIG_BT_SMP` configuration must be aligned between this sample and the Zephyr counterpart (:ref:`zephyr:smp_svr_sample`).
+  When running the :ref:`bluetooth_central_dfu_smp` sample, the :kconfig:option:`CONFIG_BT_SMP` configuration must be aligned between this sample and the Zephyr counterpart (:zephyr:code-sample:`smp-svr`).
   However, security is not enabled by default in the Zephyr sample.
 
 
@@ -1796,8 +1796,8 @@ NCSDK-21709: :ref:`peripheral_uart` sample does not work on nRF52810 and nRF5281
 
 .. rst-class:: v2-3-0 v2-2-0
 
-NCSDK-18112: :ref:`bluetooth_central_dfu_smp` sample cannot do discovery on the :ref:`smp_svr_sample`
-  The :ref:`bluetooth_central_dfu_smp` sample cannot perform the GATT discovery on a DK with the :ref:`smp_svr_sample`.
+NCSDK-18112: :ref:`bluetooth_central_dfu_smp` sample cannot do discovery on the :zephyr:code-sample:`smp-svr`
+  The :ref:`bluetooth_central_dfu_smp` sample cannot perform the GATT discovery on a DK with the :zephyr:code-sample:`smp-svr`.
 
   **Workaround:** Enable the legacy LLCP mechanism (:kconfig:option:`CONFIG_BT_LL_SW_LLCP_LEGACY`).
 
@@ -4109,22 +4109,22 @@ The time returned by clock_gettime() API becomes incorrect after one week of upt
 .. rst-class:: v1-4-2 v1-4-1 v1-4-0
 
 NCSDK-6330: USB Mass Storage Sample Application fails MSC Tests from USB3CV test tool
-  :ref:`zephyr:usb_mass` fails the USB3CV compliance Command Set Test from the MSC Tests suite.
+  :zephyr:code-sample:`usb-mass` fails the USB3CV compliance Command Set Test from the MSC Tests suite.
 
 .. rst-class:: v1-4-2 v1-4-1 v1-4-0
 
 NCSDK-6328: USB CDC ACM Composite Sample Application fails Chapter 9 Tests from USB3CV test tool
-  :ref:`zephyr:usb_cdc-acm_composite` fails the USB3CV compliance TD 9.1: Device Descriptor Test from the Chapter 9 Test suite.
+  :zephyr:code-sample:`usb-cdc-acm-composite` fails the USB3CV compliance TD 9.1: Device Descriptor Test from the Chapter 9 Test suite.
 
 .. rst-class:: v1-4-2 v1-4-1 v1-4-0
 
 NCSDK-6331: WebUSB sample application fails Chapter 9 Tests from USB3CV test tool
-  :ref:`zephyr:webusb-sample` fails the USB3CV compliance TD 9.21: LPM L1 Suspend Resume Test from the Chapter 9 Test suite.
+  :zephyr:code-sample:`webusb` fails the USB3CV compliance TD 9.21: LPM L1 Suspend Resume Test from the Chapter 9 Test suite.
 
 .. rst-class:: v1-3-2 v1-3-1 v1-3-0
 
 FOTA does not work
-  FOTA with the :ref:`zephyr:smp_svr_sample` does not work.
+  FOTA with the :zephyr:code-sample:`smp-svr` does not work.
 
   **Affected platforms:** nRF5340
 
@@ -4137,18 +4137,18 @@ NCSIDB-108: Thread context switch might lead to a kernel fault
 .. rst-class:: v1-0-0
 
 Counter Alarm sample does not work
-  The :ref:`zephyr:alarm_sample` does not work.
+  The :zephyr:code-sample:`alarm` does not work.
   A fix can be found in `Pull Request #16736 <https://github.com/zephyrproject-rtos/zephyr/pull/16736>`_.
 
 .. rst-class:: v1-3-0 v1-2-1 v1-2-0 v1-1-0 v1-0-0
 
 USB Mass Storage Sample Application compilation issues
-  :ref:`zephyr:usb_mass` does not compile.
+  :zephyr:code-sample:`usb-mass` does not compile.
 
 .. rst-class:: v1-7-1 v1-7-0 v1-4-2 v1-4-1 v1-4-0
 
 NCSDK-6832: SMP Server sample fails upon initialization
-  The :ref:`zephyr:smp_svr_sample` will fail upon initialization when using the :file:`bt-overlay.conf` Kconfig overlay file.
+  The :zephyr:code-sample:`smp-svr` will fail upon initialization when using the :file:`bt-overlay.conf` Kconfig overlay file.
   This happens because of a stack overflow.
 
   **Workaround:** Set :kconfig:option:`CONFIG_MAIN_STACK_SIZE` to ``2048``.

doc/nrf/releases_and_maturity/releases/release-notes-1.0.0.rst

@@ -312,8 +312,8 @@ DFU
 Zephyr
 ======
 
-* The :ref:`zephyr:alarm_sample` does not work. A fix can be found in `Pull Request #16736 <https://github.com/zephyrproject-rtos/zephyr/pull/16736>`_.
-* :ref:`zephyr:usb_mass` does not compile.
+* The :zephyr:code-sample:`alarm` does not work. A fix can be found in `Pull Request #16736 <https://github.com/zephyrproject-rtos/zephyr/pull/16736>`_.
+* :zephyr:code-sample:`usb-mass` does not compile.
 
 nrfxlib
 =======

doc/nrf/releases_and_maturity/releases/release-notes-1.1.0.rst

@@ -522,7 +522,7 @@ Bluetooth Low Energy
   If a directed high duty cycle advertiser times out, the application might have to wait a short time before starting a new connectable advertiser.
   Otherwise, starting the advertiser will fail.
 * Bluetooth Low Energy peripheral samples are unstable in some conditions (when pairing and bonding are performed and then disconnections/re-connections happen).
-* When running the :ref:`bluetooth_central_dfu_smp` sample, the :kconfig:option:`CONFIG_BT_SMP` configuration must be aligned between this sample and the Zephyr counterpart (:ref:`zephyr:smp_svr_sample`).
+* When running the :ref:`bluetooth_central_dfu_smp` sample, the :kconfig:option:`CONFIG_BT_SMP` configuration must be aligned between this sample and the Zephyr counterpart (:zephyr:code-sample:`smp-svr`).
   However, security is not enabled by default in the Zephyr sample.
 * The central samples (:ref:`central_uart`, :ref:`bluetooth_central_hids`) do not support any pairing methods with MITM protection.
 * On some operating systems, the nrf_desktop application is unable to reconnect to a host.

doc/nrf/releases_and_maturity/releases/release-notes-1.2.0.rst

@@ -555,7 +555,7 @@ Bluetooth Low Energy
   NFC requires this API to work correctly.
 * When the :ref:`peripheral_hids_mouse` sample is used with the Zephyr Bluetooth LE Controller, directed advertising does not time out and the regular advertising cannot be started.
 * The :ref:`bluetooth_central_hids` sample cannot connect to a peripheral that uses directed advertising.
-* When running the :ref:`bluetooth_central_dfu_smp` sample, the :kconfig:option:`CONFIG_BT_SMP` configuration must be aligned between this sample and the Zephyr counterpart (:ref:`zephyr:smp_svr_sample`).
+* When running the :ref:`bluetooth_central_dfu_smp` sample, the :kconfig:option:`CONFIG_BT_SMP` configuration must be aligned between this sample and the Zephyr counterpart (:zephyr:code-sample:`smp-svr`).
   However, security is not enabled by default in the Zephyr sample.
 * The central samples (:ref:`central_uart`, :ref:`bluetooth_central_hids`) do not support any pairing methods with MITM protection.
 * On some operating systems, the nrf_desktop application is unable to reconnect to a host.