dtoverlay=vc4-kms-dsi-generic is only going to configure DSI to generate pixel data. It won't configure a bridge of any form, and certainly not by sending commands over the DSI interface.
If you want to configure via DSI, then you need to write a panel or bridge driver, and create a suitable overlay to load it.
There are a few niggles that we're trying to get to the bottom of with Pi5's DSI interfaces, which generally are around the horizontal front porch being too short for the hardware.
There's also a patch for 4 lane operation that should be merged imminently - https://github.com/raspberrypi/linux/pull/6157
The power of Google has given me https://www.semiee.com/file/Chipone/Chipone-ICN6202.pdf and https://github.com/Tina-Linux/LCD_Panel_Driver/.
The driver in that repo is a serious mess with commented out lumps, it doesn't fit into the kernel DRM subsystem, and is referencing jd9365 (a totally different display controller) as well as ICN6202. It may not be of much help, but the repo includes docs as well.
A normal bridge driver would be panel agnostic, and just be configured based on the display timings given to it by the panel definition. That's what you'll find the in-tree icn6211 driver does.
If you want to configure via DSI, then you need to write a panel or bridge driver, and create a suitable overlay to load it.
There are a few niggles that we're trying to get to the bottom of with Pi5's DSI interfaces, which generally are around the horizontal front porch being too short for the hardware.
There's also a patch for 4 lane operation that should be merged imminently - https://github.com/raspberrypi/linux/pull/6157
The power of Google has given me https://www.semiee.com/file/Chipone/Chipone-ICN6202.pdf and https://github.com/Tina-Linux/LCD_Panel_Driver/.
The driver in that repo is a serious mess with commented out lumps, it doesn't fit into the kernel DRM subsystem, and is referencing jd9365 (a totally different display controller) as well as ICN6202. It may not be of much help, but the repo includes docs as well.
A normal bridge driver would be panel agnostic, and just be configured based on the display timings given to it by the panel definition. That's what you'll find the in-tree icn6211 driver does.
Statistics: Posted by 6by9 — Tue Jul 09, 2024 11:20 am