I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
The DisplayPort functionality you’re asking about is not within the scope of Toradex’s supported configurations. Based on the available Toradex documentation, the Apalis iMX8 provides display signals over HDMI and LVDS interfaces(1).
For the Apalis iMX8, the supported display outputs are(1):
HDMI1 with device-tree node reference hdmi and DRM connector name HDMI-A-1
LVDS1 with device-tree node reference ldb2 and DRM connector name LVDS-1
Type-Specific LVDS with device-tree node reference ldb1
The documentation notes that while the hardware can provide display port signals on the HDMI connector, these interfaces have not been brought up in Linux as of yet(1).
Since you’re working with a custom board and trying to implement DisplayPort functionality that isn’t officially supported in Toradex’s BSP, I’d recommend checking these potentially useful sources:
Would you like me to provide general guidance on this topic instead, or would you prefer to explore the officially supported HDMI and LVDS display options for your Apalis iMX8?
Best regards, Toradex AI Assistant.
Did you like my answer?
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
thank you for your question and welcome to our community!
Could you tell me what specific Toradex iMX8QM module you have and what family it is from? This information helps us to better investigate your topic.
Looking purely at the pinmuxing I believe that using DisplayPort should be possible. In that case you should just have the Displayport signals on the HDMI pins. The assumption here however from your shared logs, is that the error occurs prior to that.
cdns-mhdp-imx 56268000.hdmi: [drm:cdns_mhdp_mailbox_validate_receive [cdns_mhdp_drmcore]] Hmmm spurious mailbox data maybe, cleaning out…1:2:130 vs 1:2:2
[ 117.367633] cdns-mhdp-imx 56268000.hdmi: [drm:cdns_mhdp_get_edid_block [cdns_mhdp_drmcore]] ERROR get block[0] edid failed: -22
This could mean, that potentially something with the I2C signal is not entirely correct. edid is being read through I2C. As far as I am concerned we are using I2C0 for that: