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?
Regards, Vikash
On Fri, May 9, 2014 at 4:49 PM, Tomi Valkeinen tomi.valkeinen@ti.comwrote:
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.
Tomi
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.
Tomi
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?
Regards, Vikash
On Fri, May 9, 2014 at 4:49 PM, Tomi Valkeinen <tomi.valkeinen@ti.com mailto:tomi.valkeinen@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. Tomi
Hi,
Re-posting as previous posting was rejected due to length.
Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI conversion. I have build the driver for it from https://gitorious.org/thierryreding/linux/source/e7792ce2da5ded80861db787ace.... 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, Vikash
On Mon, May 12, 2014 at 2:11 PM, Vikas Patil vikasmpatil@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?
Regards, Vikash
On Fri, May 9, 2014 at 4:49 PM, Tomi Valkeinen tomi.valkeinen@ti.comwrote:
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.
Tomi
On 12/05/14 14:33, Vikas Patil wrote:
Hi,
Re-posting as previous posting was rejected due to length.
Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI conversion. I have build the driver for it from https://gitorious.org/thierryreding/linux/source/e7792ce2da5ded80861db787ace.... Is this the correct driver for it?
That driver cannot be used with omapdrm, which uses omapdss. There's no TDF19988 driver for omapdss (at least in the mainline), so you need to write one.
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?
You need to write a driver for it. Something similar to drivers/video/fbdev/omap2/displays-new/encoder-tfp410.c, except tfp410 is quite simple one.
But I think you said you're based on some old customized kernel, so I don't know which kind of omapdss driver you have there, so the mainline tfp410 cannot probably be used as an example. Most likely the omapdss drivers for your kernel are located in drivers/video/omap2/displays/ directory.
Tomi
Hi Tomi,
Thank a lot for your inputs and patch info.
It seems I cannot apply those patches straight away as it is based on 3.6-rc4 and I am using 3.4.25, between these two, it seems significant code changes for DSS related code.
I am using 3.4.25 kernel from TI for OMAP5 evm, it has been modified as per our platform requirement which is having OMAP5 ES2.0 revision.
I am trying to use the panel driver for DPI interface(i.e. Kernel\drivers\video\omap2\displays\panel-generic-dpi.c). So DSS and panel driver path are as follows
Kernel\drivers\video\omap2\dss\dpi.c,dss.c,display.c,dss_features.c etc Kernel\drivers\video\omap2\displays\panel-generic-dpi.c
soc specific: Kernel\arch\arm\mach-omap2\omap5_es2\clkt_clksel.c, clkt_dpll.c,clock.c,cm44xx_54xx.c etc
omapdrm path: Kernel\drivers\staging\omapdrm
In case for working HDMI port, we are using: Kernel\drivers\video\omap2\dss\hdmi.c Kernel\drivers\video\omap2\dss\hdmi_panel.c
I think this would require considerable amount of understanding on dss architecture and effort to backport some of the things, write new driver fro TDF19988 and make DPI interface working for our platform for someone like me who has just started working on DSS/Display.
Regards, Vikash
On Mon, May 12, 2014 at 5:28 PM, Tomi Valkeinen tomi.valkeinen@ti.comwrote:
On 12/05/14 14:33, Vikas Patil wrote:
Hi,
Re-posting as previous posting was rejected due to length.
Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI conversion. I have build the driver for it from
https://gitorious.org/thierryreding/linux/source/e7792ce2da5ded80861db787ace... .
Is this the correct driver for it?
That driver cannot be used with omapdrm, which uses omapdss. There's no TDF19988 driver for omapdss (at least in the mainline), so you need to write one.
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?
You need to write a driver for it. Something similar to drivers/video/fbdev/omap2/displays-new/encoder-tfp410.c, except tfp410 is quite simple one.
But I think you said you're based on some old customized kernel, so I don't know which kind of omapdss driver you have there, so the mainline tfp410 cannot probably be used as an example. Most likely the omapdss drivers for your kernel are located in drivers/video/omap2/displays/ directory.
Tomi
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.
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).
Thanks for sparing your valuable time here.
Regards, Vikash
On Mon, May 12, 2014 at 6:01 PM, Vikas Patil vikasmpatil@gmail.com wrote:
Hi Tomi,
Thank a lot for your inputs and patch info.
It seems I cannot apply those patches straight away as it is based on 3.6-rc4 and I am using 3.4.25, between these two, it seems significant code changes for DSS related code.
I am using 3.4.25 kernel from TI for OMAP5 evm, it has been modified as per our platform requirement which is having OMAP5 ES2.0 revision.
I am trying to use the panel driver for DPI interface(i.e. Kernel\drivers\video\omap2\displays\panel-generic-dpi.c). So DSS and panel driver path are as follows
Kernel\drivers\video\omap2\dss\dpi.c,dss.c,display.c,dss_features.c etc Kernel\drivers\video\omap2\displays\panel-generic-dpi.c
soc specific: Kernel\arch\arm\mach-omap2\omap5_es2\clkt_clksel.c, clkt_dpll.c,clock.c,cm44xx_54xx.c etc
omapdrm path: Kernel\drivers\staging\omapdrm
In case for working HDMI port, we are using: Kernel\drivers\video\omap2\dss\hdmi.c Kernel\drivers\video\omap2\dss\hdmi_panel.c
I think this would require considerable amount of understanding on dss architecture and effort to backport some of the things, write new driver fro TDF19988 and make DPI interface working for our platform for someone like me who has just started working on DSS/Display.
Regards, Vikash
On Mon, May 12, 2014 at 5:28 PM, Tomi Valkeinen tomi.valkeinen@ti.comwrote:
On 12/05/14 14:33, Vikas Patil wrote:
Hi,
Re-posting as previous posting was rejected due to length.
Forgot to mention, DPI pins are connected to TDF19988 chip for HDMI conversion. I have build the driver for it from
https://gitorious.org/thierryreding/linux/source/e7792ce2da5ded80861db787ace... .
Is this the correct driver for it?
That driver cannot be used with omapdrm, which uses omapdss. There's no TDF19988 driver for omapdss (at least in the mainline), so you need to write one.
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?
You need to write a driver for it. Something similar to drivers/video/fbdev/omap2/displays-new/encoder-tfp410.c, except tfp410 is quite simple one.
But I think you said you're based on some old customized kernel, so I don't know which kind of omapdss driver you have there, so the mainline tfp410 cannot probably be used as an example. Most likely the omapdss drivers for your kernel are located in drivers/video/omap2/displays/ directory.
Tomi
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
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/9223b3ce9... on 3.12 linux) https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i2c/tda998x_dr... on 3.15.-rc5 linux)
Regards, Vikash
On Fri, May 16, 2014 at 2:23 PM, Tomi Valkeinen tomi.valkeinen@ti.comwrote:
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
dri-devel@lists.freedesktop.org
-
Tomi Valkeinen -
Vikas Patil