Hi Tomi,

Thanks. Currently I am trying to understand and create a driver for TDF19988 for omapdss using the 3.8.13 (Latest OMAP5 GLDSK Kernel).

Yes, I agree omapdss has changed a lot from 3.4 to 3.8 to 3.12 to 3.15 linux kernels and following refrences which I was thinking to use for this not helping much to create a one quickly. Though it should be possible to write a new driver for 3.8 kernel or Do you know anything which will limit creating a new driver for 3.8? What do you think I should take care while creating a new driver for 3.8 or some point to keep in mind?

Other than this, are there any other references I can look at?
https://git.ti.com/wilink8-wlan/wilink8-wlan-ti-linux-kernel/trees/9223b3ce953c2af6af38ce57108f03f6c63ff91e/drivers/video/omap2/displays-new (based on 3.12 linux)
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i2c/tda998x_drv.c (based on 3.15.-rc5 linux)

Regards,

Vikash

On Fri, May 16, 2014 at 2:23 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:

On 13/05/14 09:26, Vikas Patil wrote:
> Hi Tomi,
>
>>That driver cannot be used with omapdrm, which uses omapdss. There's no
> TDF19988 driver for omapdss (at least in the mainline),
> Just to better understand, could you please explain why I can't use it
> with omadrm and omapdss? Which scenario this driver will be useful? I
> think I still didn't understand how all this sit together.

The display SW architecture used by the TDF19988 driver is totally
different than what omapdss/omapdrm uses. There is no common display
framework for linux yet.

> Do you think following driver can be used as a reference to start?
> http://www.spinics.net/lists/linux-omap/msg104598.html (Sil9022 DPI to
> HDMI Encoder).

Probably not, as your kernel is much older than the one that driver has
been written on. The omapdss driver has changed quite a bit.

Tomi