All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clayton Craft <clayton@craftyguy.net>
To: tomi.valkeinen@ti.com, aaro.koskinen@iki.fi, peter.ujfalusi@ti.com
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	laurent.pinchart@ideasonboard.com
Subject: RE: [BISECTED,REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900
Date: Thu, 20 Jul 2017 18:28:27 -0700	[thread overview]
Message-ID: <20170721012827.GI3@computer.craftyguy.net> (raw)
In-Reply-To: <ef561ff4-c96d-b59c-0df1-dfcac8163259@ti.com>

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

> Well, I tried that (attached), but it didn't work either. For some
> reason the error worker seems to stop after the disable. Possibly the
> irq flood keeps it from running, so maybe it should catch all the errors
> (I see underflows too).
> 
> Sorry, but I can't use more time on this today, and I'm leaving for
> vacation today. I hope Laurent can help during my absence.
> 
> We could try reverting the patch you mention, but I think it doesn't
> cause the problem.
> 
> Did you have CONFIG_DRM_OMAP_CONNECTOR_ANALOG_TV enabled earlier when
> things worked? If you didn't, and the dts did not contain display
> aliases, I think the omapdrm may have started without TV. So maybe the
> TV side is the culprit, somehow (I couldn't find anything when I looked
> at that side either).

Just curious if any progress has been made on this issue. It's still
happening with 4.13-rc1, and it doesn't look like any of the suspect
patches were reverted.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-07-21  1:28 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         ` Clayton Craft [this message]
2017-06-30  8:58       ` Aaro Koskinen
2017-06-30  9:02         ` Tomi Valkeinen
2017-06-30  9:02           ` Tomi Valkeinen
2017-07-04 15:09           ` Pavel Machek
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=20170721012827.GI3@computer.craftyguy.net \
    --to=clayton@craftyguy.net \
    --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.