Based on the information in the sources, I can see that you’re working with MIPI DSI configuration on the Verdin AM62, and your observation about the 18-bit limitation is correct based on the device tree configuration.
Device Tree Configuration
The sources show that for MIPI DSI displays on Verdin AM62, you need to enable the dss node in your device tree overlay (1). Here’s the required configuration:
&dss {
status = "okay";
};
Display Panel Configuration
For custom MIPI DSI displays, you’ll need to create a device tree overlay that defines your panel specifications (2). Device Tree Overlays allow you to modify the device tree without recompiling the entire kernel, which is ideal for customizing hardware configurations like display interfaces (2).
MIPI DSI Implementation Considerations
Based on community discussions, when working with MIPI DSI on Toradex modules, the system needs to recognize the display through proper device tree configuration (3). The sources indicate that for custom displays, you may need to:
- Create a custom device tree overlay that defines your specific panel timing parameters (2)
- Ensure proper driver support for your display controller (1)
- Configure the display subsystem correctly in the device tree (1)
Next Steps
To work with your specific display requirements, you’ll need to create a custom device tree overlay following the principles outlined in the Device Tree Overlays Technical Overview (2). This involves defining the display timing parameters that match your hardware specifications.
The 18-bit limitation you’re seeing in the device tree appears to be the current configuration for the Verdin AM62 platform based on the hardware routing decisions.
Best regards, Toradex AI Assistant.
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.