Give that bit a go first and see if you can get it going.Mipi-dbi-spi does look like a prime candidate for the display as it includes the driver for the LCD controller st7789v.
Even manglement with a little intelligence should be able to manage this one Image may be NSFW.Creating an overlay is clearly not for the faint hearted and sadly way beyond my capabilities. My Worzle head is Management these days and before that it was a hardware not software head - we contract out all our development work these days, otherwise I would jump onto this and get it done.
Clik here to view.

Instructions for building the kernel are at https://www.raspberrypi.com/documentati ... l#building. If you can follow those instructions and get a custom kernel running, then you've got a reasonable chance.
Once built and installed once, use "make menuconfig" to start the menu based kernel configuration. Use "/" to search, enter "CSTXXX", and press return. You should get given the one option for "TOUCHSCREEN_HYNITORN_CSTXXX". Press 1 to follow that option, then space to toggle it to "M" (module). "Escape" a couple of times should take you back to the top menu. Right arrow to select "Exit", and press return. Select "Yes" to save your configuration. Now run the steps after "make bcmXXX_defconfig" to rebuild the kernel with that module.
For the overlay start with https://github.com/raspberrypi/linux/bl ... verlay.dts which is a comparable touch screen controller. For an initial hack literally edit that file from arch/arm/boot/dts/overlays/goodix-overlay.dts. Ideally you'd create a new overlay and add it to the Makefile.
aBugsWorstNightmare has already linked to the binding at https://github.com/raspberrypi/linux/bl ... stxxx.yaml. That pretty much matches up with the Goodix overlay, other than needing to change the compatible string and add
Code:
touchscreen-size-x = <640>; touchscreen-size-y = <480>;
Rebuild and install the kernel. Edit /boot/firmware/config.txt and add "dtoverlay=goodix", or the new name if you'd created a new overlay. It does have a couple of overrides, so amend it if your panel connects the interrupt or reset to a different GPIO. Reboot, and then use evtest to see if your touchscreen is registered. If not then check the kernel logs ("dmesg") to see if there are any errors logged.
If you get stuck, then we're here to help.
Statistics: Posted by 6by9 — Tue Jul 23, 2024 3:40 pm