There is no automatic dtoverlay loading on CMs for displays, as there are too many things that can be changed to make it feasible.
For a simple install that uses BSC0 on GPIOs 0&1 (normally /dev/i2c-0 in Linux), and DSI0, then adding "dtoverlay=vc4-kms-dsi-7inch,dsi0" to config.txt should configure KMS to drive the DSI display.
NB It will also claim GPIOs 28&29 for /dev/i2c-10 as that is the standard way camera and display I2C is handled. There are ways around that, but I don't believe it's possible with the standard overlays.
For clarification, the issue with DSI0 is when stopping and restarting the interface. If your use case never allows the screensaver to kick in and disable the display, then you should be OK with it.
For a simple install that uses BSC0 on GPIOs 0&1 (normally /dev/i2c-0 in Linux), and DSI0, then adding "dtoverlay=vc4-kms-dsi-7inch,dsi0" to config.txt should configure KMS to drive the DSI display.
NB It will also claim GPIOs 28&29 for /dev/i2c-10 as that is the standard way camera and display I2C is handled. There are ways around that, but I don't believe it's possible with the standard overlays.
For clarification, the issue with DSI0 is when stopping and restarting the interface. If your use case never allows the screensaver to kick in and disable the display, then you should be OK with it.
Statistics: Posted by 6by9 — Thu Feb 29, 2024 12:08 pm