linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP display subsystem - does it work?
Date: Thu, 19 Dec 2013 17:53:36 +0000	[thread overview]
Message-ID: <20131219175336.GD32243@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <52B1A922.6020901@ti.com>

On Wed, Dec 18, 2013 at 03:54:42PM +0200, Tomi Valkeinen wrote:
> On 2013-12-18 14:00, Russell King - ARM Linux wrote:
> 
> > So, here goes.  LDP3430:
> > 
> > OMAP DSS rev 2.0
> > omapdss DPI error: can't get VDDS_DSI regulator
> > omapfb omapfb: failed to connect default display
> > omapfb omapfb: failed to init overlay connections
> > omapfb omapfb: failed to setup omapfb
> > platform omapfb: Driver omapfb requests probe deferral
> > 
> > I don't see evidence of it being re-probed, but I do see this during boot
> > which implies that there's nothing there:
> > 
> > XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> >       after 0 requests (0 known processed) with 0 events remaining.
> 
> I don't have an LDP board at hand, and I wasn't able to find out anything
> from the logs.

Well, the X server dies because of some issue with tslib.  No idea
about that.  However, disabling touschreen stuff, the X server comes
up, but the LCD remains blank.

Since the LDP has openembedded stuff on it, it normally would boot
with a progress splash - that also is never displayed.  Maybe there's
something up with the backlight support?  This used to work with
mainline kernels I don't know how long ago.

      parent reply	other threads:[~2013-12-19 17:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 12:00 OMAP display subsystem - does it work? Russell King - ARM Linux
2013-12-18 13:54 ` Tomi Valkeinen
2013-12-18 15:29   ` Russell King - ARM Linux
2013-12-18 16:03     ` Tomi Valkeinen
2013-12-18 18:23   ` Tony Lindgren
2013-12-19  5:23     ` Tomi Valkeinen
2013-12-19 16:56       ` Tony Lindgren
2013-12-20  7:45         ` Tomi Valkeinen
2013-12-19 17:56     ` Russell King - ARM Linux
2013-12-19 18:22       ` Tony Lindgren
2013-12-20 11:27         ` Russell King - ARM Linux
2013-12-20 11:48           ` Russell King - ARM Linux
2013-12-20 13:43             ` Tomi Valkeinen
2013-12-20 16:04               ` Tony Lindgren
2013-12-20 16:55                 ` Tony Lindgren
2013-12-21  0:59                   ` Russell King - ARM Linux
2013-12-28 23:30                     ` Russell King - ARM Linux
2013-12-23  7:53                   ` Tomi Valkeinen
2013-12-27 18:11                     ` Tony Lindgren
2013-12-23  7:49                 ` Tomi Valkeinen
2013-12-20 16:10           ` Tony Lindgren
2013-12-19 17:53   ` Russell King - ARM Linux [this message]

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=20131219175336.GD32243@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).