The Raspberry Pi kernel is not normally referred to as mainline.
Mainline normally references the kernel released by Linux Torvalds to https://git.kernel.org/pub/scm/linux/ke ... linux.git/ / https://github.com/torvalds/linux
To submit a driver to that kernel you need to follow the process documented at https://www.kernel.org/doc/html/latest/ ... tches.html. A panel driver would be submitted via dri-devel, and you'll need to submit device tree bindings for it too.
If only looking to merge it into the Raspberry Pi kernel (often referred to as a vendor kernel because it is tailored by the vendor for their hardware), then a Github Pull Request to https://github.com/raspberrypi/linux is the correct option. Patches still need to be separated as driver, defconfig changes, and dtoverlay changes in separate patches. All also require appropriate Signed-off-by: tags as a Certificate of Origin.
We do accept drivers and overlays for hardware shown to work on the Pi if they are being commercially produced as accessories or open source hardware hence vc4-kms-dsi-waveshare-panel (commercial) and vc4-kms-dsi-lt070me05000 (open source hardware design).
Having had a very quick look at your repo, the backlight handling isn't right as it should use the pwm-backlight module instead. A quick look implies that vc4-kms-dpi.dtsi gives the basic setup, although that is as additional fragments because it is optional in that file.
At 24bpp that is 1.016Gbit/s per lane, which exceeds vc4's capabilities of 1Gbit/s per lane.
Your timings reference 912MHz, but appear to be only setting up 20fps. Clarity is the key thing when submitting drivers, so all debug information and irrelevant comments should be removed.
Mainline normally references the kernel released by Linux Torvalds to https://git.kernel.org/pub/scm/linux/ke ... linux.git/ / https://github.com/torvalds/linux
To submit a driver to that kernel you need to follow the process documented at https://www.kernel.org/doc/html/latest/ ... tches.html. A panel driver would be submitted via dri-devel, and you'll need to submit device tree bindings for it too.
If only looking to merge it into the Raspberry Pi kernel (often referred to as a vendor kernel because it is tailored by the vendor for their hardware), then a Github Pull Request to https://github.com/raspberrypi/linux is the correct option. Patches still need to be separated as driver, defconfig changes, and dtoverlay changes in separate patches. All also require appropriate Signed-off-by: tags as a Certificate of Origin.
We do accept drivers and overlays for hardware shown to work on the Pi if they are being commercially produced as accessories or open source hardware hence vc4-kms-dsi-waveshare-panel (commercial) and vc4-kms-dsi-lt070me05000 (open source hardware design).
Having had a very quick look at your repo, the backlight handling isn't right as it should use the pwm-backlight module instead. A quick look implies that vc4-kms-dpi.dtsi gives the basic setup, although that is as additional fragments because it is optional in that file.
Code:
* VS035ZSM native timing: * 1440 x 1600 @ 60 Hz * HSYNC=40 HFP=80 HBP=80 → htotal=1640 * VSYNC=40 VFP=40 VBP=40 → vtotal=1720 * pixel clock = 1640 * 1720 * 60 / 1000 = 169,296 kHz *Your timings reference 912MHz, but appear to be only setting up 20fps. Clarity is the key thing when submitting drivers, so all debug information and irrelevant comments should be removed.
Statistics: Posted by 6by9 — Sat Feb 14, 2026 9:13 pm