Update for review comments

JamesH65 · JamesH65 · commit e16b7097bdde · 2025-04-29T14:33:52.000+01:00
diff --git a/documentation/asciidoc/accessories/display/display_intro.adoc b/documentation/asciidoc/accessories/display/display_intro.adoc
@@ -162,4 +162,4 @@ dtoverlay=vc4-kms-dsi-7inch,sizex=400,invx,invy
 
 === Installation on Compute Module based devices.
 
-All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connecting it to the DSI connector is fixed; this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator can use any and all GPIOs and interfaces for whatever purposes they require. Autodetection is therefore not feasible, and hence is disabled on Compute Module devices. This means that the Device Tree fragments required to set up the display need to be loaded via some other mechanism, which can be either with a dtoverlay entry in config.txt as described above, via a custom base DT file, or if present, a HAT EEPROM.
+All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connected to the DSI connector on the Raspberry Pi board is fixed; this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator can use any and all GPIOs and interfaces for whatever purposes they require. Autodetection is therefore not feasible, and hence is disabled on Compute Module devices. This means that the Device Tree fragments required to set up the display need to be loaded via some other mechanism, which can be either with a dtoverlay entry in config.txt as described above, via a custom base DT file, or if present, a HAT EEPROM.
diff --git a/documentation/asciidoc/computers/compute-module/cmio-display.adoc b/documentation/asciidoc/computers/compute-module/cmio-display.adoc
@@ -1,16 +1,16 @@
-== Attach the official 7-inch display
+== Attaching the Touch Display LCD panel
 
 Update your system software and firmware to the latest version before starting.
 Compute Modules mostly use the same process, but sometimes physical differences force changes for a particular model.
 
-=== Connect a display to DISP1
+=== Connect a display to DISP1/DSI1
 
 NOTE: The Raspberry Pi Zero camera cable cannot be used as an alternative to the RPI-DISPLAY adapter. The two cables have distinct wiring.
 
-To connect a display to DISP1:
+To connect a display to DISP1/DSI1:
 
 . Disconnect the Compute Module from power.
-. Connect the display to the DISP1 port on the Compute Module IO board through the 22W to 15W display adapter.
+. Connect the display to the DISP1/DSI1 port on the Compute Module IO board through the 22W to 15W display adapter.
 . _(CM1, CM3, CM3+, and CM4S only)_: Connect the following GPIO pins with jumper cables:
   * `0` to `CD1_SDA`
   * `1` to `CD1_SCL`
@@ -24,11 +24,11 @@ dtoverlay=vc4-kms-dsi-7inch
 ----
 . Reboot your Compute Module with `sudo reboot`. Your device should detect and begin displaying output to your display.
 
-=== Connect a display to DISP0
+=== Connect a display to DISP0/DSI0
 
-To connect a display to DISP0:
+To connect a display to DISP0/DSI0:
 
-. Connect the display to the DISP0 port on the Compute Module IO board through the 22W to 15W display adapter.
+. Connect the display to the DISP0/DSI0 port on the Compute Module IO board through the 22W to 15W display adapter.
 . _(CM1, CM3, CM3+, and CM4S only)_: Connect the following GPIO pins with jumper cables:
   * `28` to `CD0_SDA`
   * `29` to `CD0_SCL`
@@ -66,14 +66,14 @@ ignore_lcd=1
 
 Touch Display 2 is a 720x1280 7" LCD display designed specifically for Raspberry Pi devices (see https://www.raspberrypi.com/products/touch-display-2/). It connects in much the same way as the original touch display, but the software setup on Compute Modules is slightly different as it uses a different display driver. See xref:../accessories/touch-display-2.adoc[Touch Display 2] for connection details.
 
-Edit the /boot/firmware/config.txt file and add the following to enable Touch Display 2 on DSI1.
+Edit the /boot/firmware/config.txt file and add the following to enable Touch Display 2 on DISP1/DSI1.
 
 [source,ini]
 ----
 dtoverlay=vc4-kms-dsi-ili9881-7inch
 ----
 
-To use DSI0 use the following:
+To use DISP0/DSI0 use the following:
 
 [source,ini]
 ----

Original file line number	Diff line number	Diff line change
`@@ -162,4 +162,4 @@ dtoverlay=vc4-kms-dsi-7inch,sizex=400,invx,invy`
`162`	`162`
`163`	`163`	`=== Installation on Compute Module based devices.`
`164`	`164`
`165`		-All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connecting it to the DSI connector is fixed; this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator can use any and all GPIOs and interfaces for whatever purposes they require. Autodetection is therefore not feasible, and hence is disabled on Compute Module devices. This means that the Device Tree fragments required to set up the display need to be loaded via some other mechanism, which can be either with a dtoverlay entry in config.txt as described above, via a custom base DT file, or if present, a HAT EEPROM.
	`165`	+All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connected to the DSI connector on the Raspberry Pi board is fixed; this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator can use any and all GPIOs and interfaces for whatever purposes they require. Autodetection is therefore not feasible, and hence is disabled on Compute Module devices. This means that the Device Tree fragments required to set up the display need to be loaded via some other mechanism, which can be either with a dtoverlay entry in config.txt as described above, via a custom base DT file, or if present, a HAT EEPROM.