From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: Display not working if omapdrm is builtin with 3.15rc
Date: Fri, 2 May 2014 14:59:08 +0300 [thread overview]
Message-ID: <5363888C.5090303@ti.com> (raw)
In-Reply-To: <3A6485D2-7FEA-4C7E-9541-B814DFEE17A2@dominion.thruhere.net>
[-- 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 --]
next prev parent reply other threads:[~2014-05-02 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 10:47 Display not working if omapdrm is builtin with 3.15rc Koen Kooi
2014-05-02 11:25 ` Javier Martinez Canillas
2014-05-02 11:55 ` Koen Kooi
2014-05-02 12:00 ` Tomi Valkeinen
2014-05-02 11:59 ` Tomi Valkeinen [this message]
2014-05-02 12:33 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5363888C.5090303@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.