Trying new MIPI-DSI code for the touch panel
#1
Hi,

  I'm trying to compile a 4.19 kernel with new code for the MIPI-DSI connection by Jagan Teki, but am unsure regarding display panel selection.

Can anyone say if the pine64 7" screen is one of or similar to any of:

 Bananapi S070WV20-CT16 MIPI-DSI
 Ilitek ILI9322 320x240 QVGA panels    
 Ilitek ILI9881C-based panels
 Innolux P079ZCA panel (NEW)      
 JDI LT070ME05000 WUXGA DSI panel  
 Samsung LD9040 RGB/SPI panel 
 LG4573 RGB/SPI panel
 Orise Technology otm8009a 480x800 dsi 2dl panel
 Panasonic VVX10F034N00 1920x1200 video mode panel
 Raspberry Pi 7-inch touchscreen panel
 Raydium RM68200 720x1280 DSI video mode panel 
 Samsung S6E3HA2 DSI video mode panel
 Samsung S6E63J0X03 DSI command mode panel
 Samsung S6E8AA0 DSI video mode panel
 Seiko 43WVF1G panel
 Sharp LQ101R1SX01 panel
 Sharp LS043T1LE01 qHD video mode panel
 Sitronix ST7789V panel

Many thanks for help!
  Reply
#2
(10-16-2018, 05:46 AM)Learnincurve Wrote: Hi,

  I'm trying to compile a 4.19 kernel with new code for the MIPI-DSI connection by Jagan Teki, but am unsure regarding display panel selection.

Can anyone say if the pine64 7" screen is one of or similar to any of:

 Bananapi S070WV20-CT16 MIPI-DSI
 Ilitek ILI9322 320x240 QVGA panels    
 Ilitek ILI9881C-based panels
 Innolux P079ZCA panel (NEW)      
 JDI LT070ME05000 WUXGA DSI panel  
 Samsung LD9040 RGB/SPI panel 
 LG4573 RGB/SPI panel
 Orise Technology otm8009a 480x800 dsi 2dl panel
 Panasonic VVX10F034N00 1920x1200 video mode panel
 Raspberry Pi 7-inch touchscreen panel
 Raydium RM68200 720x1280 DSI video mode panel 
 Samsung S6E3HA2 DSI video mode panel
 Samsung S6E63J0X03 DSI command mode panel
 Samsung S6E8AA0 DSI video mode panel
 Seiko 43WVF1G panel
 Sharp LQ101R1SX01 panel
 Sharp LS043T1LE01 qHD video mode panel
 Sitronix ST7789V panel

Many thanks for help!

Here is the 7" LCD panel datasheet published on PINE64 wiki page: http://files.pine64.org/doc/datasheet/pi..._panel.pdf

Jagan will receive this same panel soon and you can follow up with him.
  Reply
#3
Thank you TLLIM.

  Glad Jagan is in the loop with the screen!

BR.

--Marius--
  Reply
#4
Jagan has published code at https://github.com/amarula/linux-amarula...IP-A64-DSI including support for the feiyang panel, so we should be good to go with a mainline kernel supporting desktop features with the LCD screen. The rest of the mainlining effort also seems to be progressing nicely now, with only a few holes still remaining.-

I tried compiling an Armbian image against Jagan's kernel, but couldn't get the board to boot. Probably due to my very limited (mis)understanding of the arm boot process and the way uboot, system and the device tree interact. the board powered up and got warm, but didn't connect to the network and didn't expand the fs image to fill the SD card. I copy of the image is available at https://drive.google.com/open?id=1ZMiXZU...Q3ViHPetDH

in case anyone wants to play with it.

BR.

--Marius--
  Reply
#5
(11-12-2018, 03:40 AM)Learnincurve Wrote: Jagan has published code at https://github.com/amarula/linux-amarula...IP-A64-DSI including support for the feiyang panel, so we should be good to go with a mainline kernel supporting desktop features with the LCD screen. The rest of the mainlining effort also seems to be progressing nicely now, with only a few holes still remaining.-

I tried compiling an Armbian image against Jagan's kernel, but couldn't get the board to boot. Probably due to my very limited (mis)understanding of the arm boot process and the way uboot, system and the device tree interact. the board powered up and got warm, but didn't connect to the network and didn't expand the fs image to fill the SD card.  I copy of the image is available at https://drive.google.com/open?id=1ZMiXZU...Q3ViHPetDH

in case anyone wants to play with it.

BR.

--Marius--

You can contact jagan at sunxi IRC, my guess due to PLL clock setting.
  Reply
#6
Looks like it might be a build issue. The image is missing a device tree (.dtb) file.

I will try to address the problem before bothering Jagan.
  Reply
#7
(11-14-2018, 02:26 AM)Learnincurve Wrote: Looks like it might be a build issue. The image is missing a device tree (.dtb) file.

I will try to address the problem before bothering Jagan.

Do you resolve the problem with LCD? I would like to join to this topic and go farther with others display which can be connected to Pine64. Do FEYIANG FY07024DI26A30-D is an official default LCD for Pine64 (available on link https://store.pine64.org/?product=7-lcd-touch-screen-panel).
Regards
Voloviq
  Reply
#8
Do FEIYANG is a default official LCD for Pine64 available at (https://store.pine64.org/?product=7-lcd-...reen-panel)
  Reply
#9
The panel driver for Feiyang seems to work well with the work Jagan Teki did for kernel 4.19 and upwards.
We (the Volumio team, volumio.org) have been testing with a few of the 5.x kernels which integrated his work.
We always experience the same issue when trying to rotate the screen orientation counter clockwise, using a setting in /etc/X11/xorg.conf. It causes a kernel driver to crash when a timeout occurs while waiting for vblank, with all sorts of followup issues.

Did anyone run into these vblank time out issues, if so, in which configuration? Or with other panels?

Cheers - Gé
  Reply
#10
(09-07-2019, 04:06 PM)gkkpch Wrote: The panel driver for Feiyang seems to work well with the work Jagan Teki did for kernel 4.19 and upwards.
We (the Volumio team, volumio.org) have been testing with a few of the 5.x kernels which integrated his work.
We always experience the same issue when trying to rotate the screen orientation counter clockwise, using a setting in /etc/X11/xorg.conf. It causes a kernel driver to crash when a timeout occurs while waiting for vblank, with all sorts of followup issues.

Did anyone run into these vblank time out issues, if so, in which configuration? Or with other panels?

Cheers - Gé

I don't know specifically the answer to your question, but this document seems to imply that you could do the rotation in the device tree instead of in your xorg.conf. I don't know exactly how you do that, but I think it must be an option within the panel definition.

https://git.kernel.org/pub/scm/linux/ker...?h=v5.2.14
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)