Bhupiister singh

I am not using that distro at the moment as its not fulfilling my purpose at the moment so still evaluating. Milk v has a small core for running arduino application and then Linux and arduino can talk, this lets real time task run on small core, which is what i want. That distro is using small core for Image signal processing, which i do not want.

I was able to make 4 inch and 2 inch lcd work I reported the solution on github too where i was trying to solve it with someone Github link to solution For 2inch LCD module, i simply followed this link 2 inc LCD This patch in the above link was important duo-kernel-fb_st7789v.patch I was also able to make ST7796s 4inch LCD work, I kept the above patch but the init sequence for this display was different, below is the full code fb_st7796s.c /linux_5.10/drivers/staging/fbtft/fb_st7796s.c Make entry in the Makefile obj-$(CONFIG_FB_TFT_ST7796S) += fb_st7796s.o Entry in the kconfig config FB_TFT_ST7796S tristate "FB driver for the ST7789V LCD Controller" depends on FB_TFT help This enables generic framebuffer support for the Sitronix ST7796S display controller. The controller is intended for small color displays with a resolution of up to 320x240 pixels. Say Y if you have such a display that utilizes this controller. Keep modifications made by above patch for this file /linux_5.10/drivers/staging/fbtft/fbtft-core.c DTS that works for me I am having issue of the color inversion where RGB is BRG 4 inch preview 2 inch preview

My intention is not to put the whole desktop on the display. Just a user application. I am trying to build a thermostat and might use LVGL for it. I tried a similar project on 256MB and still had plenty of RAM left.

Making it work with panel-mipi-dbi is completely new to me. I hope ill be able to make sense out of it.

@robertoj My objective is MilkV Duo S with Waveshare ili9486 LCD, and it will be much better if I can use ST7796, as this is a 4-inch display. I need to make at least a 4-inch display work for my project. It can be any readily available display.

@robertoj What about your experience with ST7796? I have one with red pcb. Even this one is not working for me. Tried different dtb and .c files. Did this work for you ever?

Hi @robertoj and @WDR_s I am having a similar screen ILI9486 from waveshare that i am trying to make it work with Milk-v duo S board. https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(B) I was able to drive ST7789v and see content on screen with below code dts file &spi3 { status = "okay"; /delete-node/ spidev@0; st7789v: st7789v@0 { compatible = "sitronix,st7789v"; reg = <0>; spi-max-frequency = <48000000>; spi-cpol; spi-cpha; rotate = <0>; fps = <60>; rgb; buswidth = <8>; dc = <&porta 18 GPIO_ACTIVE_HIGH>; reset = <&porta 28 GPIO_ACTIVE_HIGH>; debug = <0x0>; status = "okay"; }; }; But trying to make ILi9486 work is next to impossible for me. I tried the dts file modification that worked for @WDR_s before he implemented touch. But this also does not work for me. And just for information dc-gpios and reset-gpios does not work for me and i have to name it dc and reset or else device /dev/fb0 is not created. &spi3 { status = "okay"; #address-cells = <1>; #size-cells = <0>; /delete-node/ spidev@0; ili9486: ili9486@0 { /* IMPORTANT: fb_tft binds MUCH more reliably to this */ compatible = "ilitek,ili9341"; reg = <0>; status = "okay"; /* SPI MODE 0 (correct for Waveshare ILI9486) */ spi-max-frequency = <24000000>; /* Use SAME pins that worked for ST7789V */ dc = <&porta 18 GPIO_ACTIVE_HIGH>; reset = <&porta 28 GPIO_ACTIVE_HIGH>; rotate = <0>; bgr = <0>; fps = <30>; regwidth = <16>; buswidth = <8>; txbuflen = <65536>; debug = <3>; /* Long, safe init sequence */ init = <0x10000b0 0x00 0x1000011 0x20000ff 0x10000C0 0x0D 0x0D 0x10000C1 0x43 0x10000C5 0x00 0x48 0x80 0x10000C7 0x00 0x1000036 0x28 0x100003A 0x55 0x10000B1 0xB0 0x11 0x10000F0 0x01 0x10000F6 0x00 0x01 0x32 0x1000026 0x01 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F 0x10000B6 0x02 0x02 0x3B 0x1000011 0x20000ff 0x1000029>; }; }; This is very critical for me and i would really appreciate if you could make things work for me. Is the kernel 5.10 a issue here? as my SPI pins work for other display but not just for this display.