Display not working if omapdrm is builtin with 3.15rc

Display not working if omapdrm is builtin with 3.15rc

[Koen Kooi]

Hi,

I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.

So what's the magic to get an actual signal on the hdmi connector?

regards,

Koen

Re: Display not working if omapdrm is builtin with 3.15rc

[Javier Martinez Canillas]

Hello Koen,

On Fri, May 2, 2014 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Hi,
>
> I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.
>
> So what's the magic to get an actual signal on the hdmi connector?
>
> regards,
>
> Koen--

This is a known issue as far as I know. You need [0] to correctly set
the display PLL clock rates.

Best regards,
Javier

[0]: http://permalink.gmane.org/gmane.linux.ports.arm.kernel/295077

Re: Display not working if omapdrm is builtin with 3.15rc

[Koen Kooi]

Op 2 mei 2014, om 13:25 heeft Javier Martinez Canillas <javier@dowhile0.org> het volgende geschreven:

> Hello Koen,
> 
> On Fri, May 2, 2014 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Hi,
>> 
>> I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.
>> 
>> So what's the magic to get an actual signal on the hdmi connector?
>> 
>> regards,
>> 
>> Koen--
> 
> This is a known issue as far as I know. You need [0] to correctly set
> the display PLL clock rates.

OK, 1/2 is already in and I applied 2/2 manually. Still no picture on screen :(

root@beagleboard:~# dmesg | grep -i fb
      .init : 0xc07a9000 - 0xc07fb040   ( 329 kB)
[    3.830474] Freeing unused kernel memory: 328K (c07a9000 - c07fb000)
[   10.082489] omapdrm omapdrm.0: fb0: omapdrm frame buffer device

root@beagleboard:~# dmesg | grep -i drm
[    3.042266] [drm] Initialized drm 1.1.0 20060810
[    9.785095] omapdrm omapdrm.0: DMM not available, disable DMM support
[    9.792816] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    9.799865] [drm] No driver support for vblank timestamp query.
[   10.082489] omapdrm omapdrm.0: fb0: omapdrm frame buffer device
[   10.088775] omapdrm omapdrm.0: registered panic notifier
[   10.094421] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0

root@beagleboard:~# dmesg | grep -i dvi
[    6.943420] connector-dvi connector.10: failed to find video source
[    6.950256] platform connector.10: Driver connector-dvi requests probe deferral

Then I used this uSD card in a different board and I get the orange u-boot screen and later a GNOME desktop. So it seems I tested it with a broken board :/
Nevertheless, everything as builtin is still broken, but with modules it seems to work.

regards,

Koen

Re: Display not working if omapdrm is builtin with 3.15rc

[Tomi Valkeinen]

[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]

On 02/05/14 13:47, Koen Kooi wrote:
> Hi,
> 
> I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.
> 
> So what's the magic to get an actual signal on the hdmi connector?

Sigh, looks like my beagle xM died on me while testing this...

The reason for this is that the twl_gpio (which TFP410 uses) gets
initialized really late, so display things get deferred. Then, before
TFP410 has initialized, omapdrm starts. It finds VENC (tv-out) display
available, so it starts. After that TFP410 gets probed, but as DRM
doesn't support adding displays later, it is never actually added to
omapdrm.

Also, the VENC output doesn't even work by default if
CONFIG_DRM_OMAP_NUM_CRTCS is 1. It needs to be set to 2 to support the
second output (tv-out in this case). But my board died before I managed
to test this.

So, the probing is quite broken. And I have no good ideas how to fix it,
only bad ones...

A simple thing to do for testing is to either disable
CONFIG_OMAP2_DSS_VENC from the kernel, or remove the svideo-connector
from the board's .dts file. This results in tv-out not being available,
so when omapdrm starts and finds no displays, it'll defer its probe,
thus getting the DVI next time it probes.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Display not working if omapdrm is builtin with 3.15rc

[Tomi Valkeinen]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

On 02/05/14 14:25, Javier Martinez Canillas wrote:
> Hello Koen,
> 
> On Fri, May 2, 2014 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Hi,
>>
>> I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.
>>
>> So what's the magic to get an actual signal on the hdmi connector?
>>
>> regards,
>>
>> Koen--
> 
> This is a known issue as far as I know. You need [0] to correctly set
> the display PLL clock rates.
> 
> Best regards,
> Javier
> 
> [0]: http://permalink.gmane.org/gmane.linux.ports.arm.kernel/295077

Different board, different problem. The link talks about beaglebone,
Koen about beagleboard.

 Tomi




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Display not working if omapdrm is builtin with 3.15rc

[Koen Kooi]

Op 2 mei 2014, om 13:59 heeft Tomi Valkeinen <tomi.valkeinen@ti.com> het volgende geschreven:

> On 02/05/14 13:47, Koen Kooi wrote:
>> Hi,
>> 
>> I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.
>> 
>> So what's the magic to get an actual signal on the hdmi connector?
> 
> Sigh, looks like my beagle xM died on me while testing this...
> 
> The reason for this is that the twl_gpio (which TFP410 uses) gets
> initialized really late, so display things get deferred. Then, before
> TFP410 has initialized, omapdrm starts. It finds VENC (tv-out) display
> available, so it starts. After that TFP410 gets probed, but as DRM
> doesn't support adding displays later, it is never actually added to
> omapdrm.
> 
> Also, the VENC output doesn't even work by default if
> CONFIG_DRM_OMAP_NUM_CRTCS is 1. It needs to be set to 2 to support the
> second output (tv-out in this case). But my board died before I managed
> to test this.
> 
> So, the probing is quite broken. And I have no good ideas how to fix it,
> only bad ones...
> 
> A simple thing to do for testing is to either disable
> CONFIG_OMAP2_DSS_VENC from the kernel, or remove the svideo-connector
> from the board's .dts file. This results in tv-out not being available,
> so when omapdrm starts and finds no displays, it'll defer its probe,
> thus getting the DVI next time it probes.

I disabled CONFIG_OMAP2_DSS_VENC and DVI works as expected with everything builtin!

regards,

Koen