From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Tony Lindgren <tony@atomide.com>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Subject: Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900
Date: Thu, 15 Jun 2017 10:28:31 +0300 [thread overview]
Message-ID: <faadb535-666e-1ac9-35c5-58916d3c92aa@ti.com> (raw)
In-Reply-To: <20170614221133.k7gmbzzjsbmbjgbc@darkstar.musicnaut.iki.fi>
On 2017-06-15 01:11, Aaro Koskinen wrote:
> Hi,
>
> When booting v4.12-rc5 on Nokia N900, omapdrm fails to probe and there
> is no display.
>
> Bisected to:
>
> a09d2bc1503508c17ef3a71c6b1905e3660f3029 is the first bad commit
> commit a09d2bc1503508c17ef3a71c6b1905e3660f3029
> Author: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Date: Tue May 3 22:08:01 2016 +0300
>
> drm/omap: Use omapdss_stack_is_ready() to check that the display stack is up
>
> Instead of 'guessing' based on aliases of the status of the DSS drivers,
> use the new interface to check that all needed drivers are loaded.
> In this way we can be sure that all needed drivers are loaded so it is
> safe to continue the probing of omapdrm.
> This method will allow the omapdrm to be probed 'headless', without
> outputs.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> Reverting the commit seems to fix the issue.
When you revert this patch do you see a warning saying:
"could not connect display: blah" ? if so what is 'blah'?
n900 have two displays afaik, LCD and TVout. omapdss_stack_is_ready() is
to ensure that we have all the drivers loaded for both displays, while
by reverting it it is enough if one of them is loaded at the time we do
the check and omapdrm would continue to probe, but the missing display
(even if it is going to be probed a bit later) will not work.
- Péter
next prev parent reply other threads:[~2017-06-15 7:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 22:11 Aaro Koskinen
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 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-07-04 15:09 ` Pavel Machek
2017-07-31 12:59 ` Tomi Valkeinen
2017-06-30 12:36 ` Daniel Vetter
2017-07-31 13:21 ` Tomi Valkeinen
2017-08-02 10:12 ` Daniel Vetter
2017-08-02 11:54 ` Tomi Valkeinen
2017-08-02 12:08 ` Daniel Vetter
2017-06-15 7:28 ` Peter Ujfalusi [this message]
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=faadb535-666e-1ac9-35c5-58916d3c92aa@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®