Add information on setting up Touch Display 2 on Compute Modules #4072
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6by9
reviewed
Apr 16, 2025
documentation/asciidoc/computers/compute-module/cmio-display.adoc
Outdated
Show resolved
Hide resolved
documentation/asciidoc/computers/compute-module/cmio-display.adoc
Outdated
Show resolved
Hide resolved
lurch
reviewed
Apr 16, 2025
lurch
changed the title
lurch
reviewed
Apr 16, 2025
|
I have pushed changes requested. |
lurch
reviewed
Apr 22, 2025
lurch
reviewed
Apr 22, 2025
lurch
reviewed
Apr 22, 2025
lurch
reviewed
Apr 22, 2025
documentation/asciidoc/computers/compute-module/cmio-display.adoc
Outdated
Show resolved
Hide resolved
lurch
reviewed
Apr 22, 2025
lurch
reviewed
Apr 23, 2025
|
|
||
| === 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. |
There was a problem hiding this comment.
IMHO "All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connecting it to the DSI connector is fixed;" makes it sound like it's the circuitry between the Touch Display and the DSI connector which is fixed? Which is obviously also true for the CMs 😉
Perhaps "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;" ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was missing information on the dt runes needed to get TD2 up and running on CM devices.