OMAPDSS: omap5 SYNC_LOST error with DPI/LCD
vikasmpatil at gmail.com
Mon May 12 04:33:48 PDT 2014
Re-posting as previous posting was rejected due to length.
Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI
I have build the driver for it from
Is this the correct driver for it?
Also I am trying to use the generic-dpi-panel driver for this with OMAP5.
It seems I also need to add support for TDF19988 somewhere in omapdrm or
lcd/panel driver by calling drm_i2c_encoder_init to initialize it. Can I
use somecode from ticldc driver or driver itself? Could you please give
some inputs, how should I proceed further to adding support for TDF19988
for which the input is coming from DPI interface?
Thanks & Regards,
On Mon, May 12, 2014 at 2:11 PM, Vikas Patil <vikasmpatil at gmail.com> wrote:
> Hi Tomi,
> How could I confirm for OMAP5 DPI support apart form enabling
> CONFIG_OMAP2_DSS_DPI and CONFIG_PANEL_GENERIC_DPI? Enabling mentioned
> config builds components from Kernel\drivers\video\omap2\dss and
> kernel\drivers\video\omap2\displays only. Is there any support needs to be
> available under kernel\arch\arm\mach-omap2?
> On Fri, May 9, 2014 at 4:49 PM, Tomi Valkeinen <tomi.valkeinen at ti.com>wrote:
>> On 08/05/14 13:07, Vikas Patil wrote:
>> > Hi,
>> > I am working on to enable the second display output for customized OMAP5
>> > based platform and linux 3.4.25. First display which is HDMI/tv is
>> > working fine. Second display out is coming via DPI interface. To enable
>> > DPI interface I enabled CONFIG_OMAP2_DSS_DPI and
>> > CONFIG_PANEL_GENERIC_DPI and added that in omap_dss_device and
>> > omap_dss_board_info and removed the HDMI device and disabled
>> > CONFIG_OMAP5_DSS_HDMI. With his kernel seems to be booting correctly,
>> > however when I try to run kmscube app and it seems to be running,
>> > noticing following error and till now nothing on display.
>> Does the kernel have support for OMAP5 DPI? I remember there were some
>> bits that had to be added to make it work.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dri-devel