All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Tony Lindgren <tony@atomide.com>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900
Date: Tue, 4 Jul 2017 17:09:02 +0200	[thread overview]
Message-ID: <20170704150902.GB10703@localhost> (raw)
In-Reply-To: <5bc9976e-228c-5cba-c2ae-bfc5135f17a0@ti.com>

Hi!

> >>>> Are you sure it doesn't probe? It fails the omapdss_stack_is_ready()
> >>>> check?
> >>>
> >>> It appears the reason was that I didn't have
> >>> CONFIG_DRM_OMAP_CONNECTOR_ANALOG_TV enabled.
> >>>
> >>> I think that's wrong. I don't own an analog TV, so why should I enable
> >>> such option to get device's built-in display working?
> >>
> >> Indeed. Unfortunately I don't have a solution for that.
> >>
> >> DRM doesn't support adding devices after probe. So at omapdrm probe time
> >> we have to decide which displays to use. In the dts file, n900 defines
> >> the lcd and analog tv. omapdrm sees those, and, of course, must wait
> >> until their respective drivers have probed. If you don't have the
> >> display driver enabled, it's never loaded and omapdrm never probes as it
> >> keeps waiting for those.
> > 
> > Could you at least print some kind of message early in the boot ("omapdrm
> > is waiting for drivers for display x and y")?
> 
> That could be quite spammy. omapdrm will defer probe if the displays are
> not present, and the deferred probing machinery will then cause a new
> omapdrm probe later. That can happen a lot of times before the drivers
> are there.

Well doing printk just once should not be a problem...?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2017-07-04 15:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 22:11 [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900 Aaro Koskinen
2017-06-15  6:51 ` Tomi Valkeinen
2017-06-15  6:51   ` Tomi Valkeinen
2017-06-18 21:31   ` Aaro Koskinen
2017-06-29 18:50   ` Aaro Koskinen
2017-06-29 19:12     ` Aaro Koskinen
2017-06-30  5:52     ` Tony Lindgren
2017-06-30  6:41     ` Tomi Valkeinen
2017-06-30  6:41       ` Tomi Valkeinen
2017-06-30  8:47       ` Tomi Valkeinen
2017-06-30  8:47         ` Tomi Valkeinen
2017-06-30  9:37         ` Aaro Koskinen
2017-07-21  1:28         ` [BISECTED,REGRESSION] " Clayton Craft
2017-06-30  8:58       ` [BISECTED, REGRESSION] " Aaro Koskinen
2017-06-30  9:02         ` Tomi Valkeinen
2017-06-30  9:02           ` Tomi Valkeinen
2017-07-04 15:09           ` Pavel Machek [this message]
2017-07-31 12:59             ` Tomi Valkeinen
2017-07-31 12:59               ` Tomi Valkeinen
2017-06-30 12:36       ` Daniel Vetter
2017-06-30 12:36         ` Daniel Vetter
2017-07-31 13:21         ` Tomi Valkeinen
2017-07-31 13:21           ` Tomi Valkeinen
2017-08-02 10:12           ` Daniel Vetter
2017-08-02 10:12             ` Daniel Vetter
2017-08-02 11:54             ` Tomi Valkeinen
2017-08-02 11:54               ` Tomi Valkeinen
2017-08-02 12:08               ` Daniel Vetter
2017-08-02 12:08                 ` Daniel Vetter
2017-06-15  7:28 ` Peter Ujfalusi
2017-06-15  7:28   ` Peter Ujfalusi
2017-06-18 21:44   ` Aaro Koskinen

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=20170704150902.GB10703@localhost \
    --to=pavel@ucw.cz \
    --cc=aaro.koskinen@iki.fi \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=tony@atomide.com \
    /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.