OMAPDSS: omap5 SYNC_LOST error with DPI/LCD
tomi.valkeinen at ti.com
Mon May 12 04:26:25 PDT 2014
Well, there's at least a bit in the dss that needs to be configured for
DPI to be routed correctly. Commit
de09e4555592986219132b518c3f7834a28823cd in the mainline does that.
Then, if using DSI PLL, the clock routing needs to be fixed for OMAP5,
mainline commit f8ad984ce0372f43006f5c700310c2d6f301085d does that.
I'm not sure if there are any other OMAP5 DPI specific things, those are
the ones I remember.
On 12/05/14 11:41, Vikas Patil 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
> <mailto: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
> > 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
> > 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 --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the dri-devel