MIPI LCD 10.1

[Valma]

I could see that i don't have the driver mb709_mipi in my debian distribution, i suppose that it should be in /lib/modules/3.10.102-2-pine64-longsleep/kernel/drivers/ and in a folder, i thought that it would be in drivers/video/sunxi/disp2/disp but i can't see this folders because don't exist.

I've searched in https://github.com/linux-sunxi/linux-sunxi but i didn't find the driver...

Where can i find the driver?because i modified the dtb file with the correct values obtaining it of screen's datasheet. I think that i only need the driver for linux to work the screen.

Afterward, it's possible that mb709_mipi won't work for my screen, but i have looking for a driver that i could modify to adapt and i can see this one in the sources:
drivers/video/omap/lcd_mipid.c

what do you think?

Thank you for your support.

Just doing a bit of searching and it appears that the LCD displaying "aging mode" is simply the LCD performing a basic diagnostic check on itself.  I believe that you have given the LCD power, but other than that there is no communication happening between the pine and the LCD. 

Have you made any more progress with this?  I think that it will not be a trivial task to add support for additional displays for the dsi port. If my understanding is correct LCD drivers need to be added before video driver compilation?  Someone correct me if I am wrong.

Yes, i saw time ago that aging mode is a test of screen, and i can configure the screen to work in that mode connected to pine64. 

At this moment the problem is the drivers and the wake-up command. I think that the conexion are well but debian and the screen have problem to detect each other. I tried to develop drivers but the problem is that i can't debug and i only have traces as a debug system and that is a pain for taking advances.

I think that the solution is nearest than it seems but the problem is that i don't have resources to debug. I was looking ways to debug but i remember that pine64 doesn't have the connector jtag or something like that...

From my point of view, the solution will be in the driver now, and I can analyze the other screen drivers and it seems not to be so complicated because in the screen specifications says that the only thing that is necesary is to send the wake-up command, afterthat i suppose that the communication will be activated and it will work.