doc: display: consolidate MIPI docs in Display section

Move MIPI-DBI and MIPI-DSI docs from top-level Peripherals section to
under Display section.

Signed-off-by: Benjamin Cabé <[email protected]>

Author: kartben

MAINTAINERS.yml

@@ -1919,7 +1919,6 @@ Documentation Infrastructure:
   status: odd fixes
   files:
     - drivers/mipi_dsi/
-    - doc/hardware/peripherals/mipi_dsi.rst
     - include/zephyr/drivers/mipi_dsi.h
     - include/zephyr/drivers/mipi_dsi/
     - tests/drivers/mipi_dsi/

doc/_scripts/redirects.py

@@ -168,6 +168,8 @@
     ('guides/west/zephyr-cmds', 'develop/west/zephyr-cmds'),
     ('guides/zephyr_cmake_package', 'build/zephyr_cmake_package'),
     ('hardware/peripherals/eeprom', 'hardware/peripherals/eeprom/index'),
+    ('hardware/peripherals/mipi_dbi', 'hardware/peripherals/display/index'),
+    ('hardware/peripherals/mipi_dsi', 'hardware/peripherals/display/index'),
     ('hardware/peripherals/sensor', 'hardware/peripherals/sensor/index'),
     ('kernel/libc/index', 'develop/languages/c/index'),
     ('reference/api/api_lifecycle', 'develop/api/api_lifecycle'),

doc/hardware/peripherals/display/index.rst

@@ -1,11 +1,44 @@
-.. comment
-   not documenting
-   .. doxygengroup:: display_interfaces
-
 .. _display_api:
 
-Display Interface
-#################
+Display
+#######
+
+The Display subsystem in Zephyr provides a unified way to interact with a wide range of display
+devices. The Display API is transport-agnostic: it describes what you want the display to do,
+without exposing how the data moves over the wire.
+
+MIPI Display Bus Interface (DBI)
+********************************
+
+The **MIPI DBI** specification defines several parallel and serial buses for connecting a host to a
+display controller. In Zephyr, DBI support provides bus-level primitives for command writes, reads,
+pixel transfers, reset, and related operations that a driver uses internally to implement the
+generic API.
+
+Applications do not use DBI functions directly. Instead, they call the generic Display API (e.g., to
+write pixels), and the display driver handles the DBI protocol under the hood.
+
+MIPI-DBI defines 3 interface types:
+
+* Type A: Motorola 6800 parallel bus
+* Type B: Intel 8080 parallel bus
+* Type C: SPI Type serial bit bus with 3 options:
+
+  #. 9 write clocks per byte, final bit is command/data selection bit
+  #. Same as above, but 16 write clocks per byte
+  #. 8 write clocks per byte. Command/data selected via GPIO pin
+
+Currently, the API does not support Type C controllers with 16 write clocks (option 2).
+
+MIPI Display Serial Interface (DSI)
+***********************************
+
+The **MIPI DSI** standard is a high-speed differential serial bus designed for modern color TFT
+panels. Zephyr's DSI support provides the primitives needed by drivers to implement the generic
+Display API on top of a DSI link.
+
+As with DBI, applications never call DSI functions directly. They remain portable by using the
+generic Display API, while the driver handles the DSI transactions internally.
 
 API Reference
 *************
@@ -15,6 +48,20 @@ Generic Display Interface
 
 .. doxygengroup:: display_interface
 
+.. _mipi_dbi_api:
+
+MIPI Display Bus Interface (DBI)
+================================
+
+.. doxygengroup:: mipi_dbi_interface
+
+.. _mipi_dsi_api:
+
+MIPI Display Serial Interface (DSI)
+===================================
+
+.. doxygengroup:: mipi_dsi_interface
+
 Grove LCD Display
 =================
 

doc/hardware/peripherals/index.rst

@@ -40,8 +40,6 @@ Peripherals
    ipm.rst
    led.rst
    mdio.rst
-   mipi_dbi.rst
-   mipi_dsi.rst
    mspi.rst
    mbox.rst
    pcie.rst