From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Adam Ford <aford173@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OMAP DRM regression on N900
Date: Wed, 21 Aug 2019 21:51:27 +0300 [thread overview]
Message-ID: <20190821185127.GD26759@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAHCN7xLEiH6PttR6707dSVvi4N4qZM9UyXj4b-TUqOJSboi71g@mail.gmail.com>
Hi Adam,
On Wed, Aug 21, 2019 at 01:45:28PM -0500, Adam Ford wrote:
> On Wed, Aug 21, 2019 at 1:37 PM Laurent Pinchart wrote:
> > On Sun, Aug 18, 2019 at 05:08:38PM +0300, Aaro Koskinen wrote:
> > > Hi,
> > >
> > > I haven't got display working on N900 since v5.1. Bisected to:
> > >
> > > d17eb4537a7eb16da9eafbfd5717e12b45b77251 is the first bad commit
> > > commit d17eb4537a7eb16da9eafbfd5717e12b45b77251
> > > Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > Date: Wed Sep 12 19:41:31 2018 +0300
> > >
> > > drm/omap: Factor out common init/cleanup code for output devices
> >
> > Sorry :-(
> >
> > I'll send a tentative fix, I'd appreciate if you could test it.
>
> Can you point me to this patch? I was in the process of
> troubleshooting both a DM37, OMAP35 and AM35 board who all have blank
> screens. I'd like to try this patch too.
https://lists.freedesktop.org/archives/dri-devel/2019-August/232222.html
I forgot to CC linux-omap, I'll bounce the patch to do so now.
> > > looks like with this commit I get only the TV out:
> > >
> > > $ ls -l /sys/class/drm/
> > > total 0
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:15 card0 -> ../../devices/platform/omapdrm.0/drm/card0
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:15 card0-SVIDEO-1 -> ../../devices/platform/omapdrm.0/drm/card0/card0-SVIDEO-1
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:15 renderD128 -> ../../devices/platform/omapdrm.0/drm/renderD128
> > > -r--r--r-- 1 root root 4096 Aug 18 16:15 version
> > >
> > > with the previous commit both outputs are there:
> > >
> > > $ ls -l /sys/class/drm/
> > > total 0
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:28 card0 -> ../../devices/platform/omapdrm.0/drm/card0
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:28 card0-LVDS-1 -> ../../devices/platform/omapdrm.0/drm/card0/card0-LVDS-1
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:28 card0-SVIDEO-1 -> ../../devices/platform/omapdrm.0/drm/card0/card0-SVIDEO-1
> > > lrwxrwxrwx 1 root root 0 Aug 18 16:28 renderD128 -> ../../devices/platform/omapdrm.0/drm/renderD128
> > > -r--r--r-- 1 root root 4096 Aug 18 16:28 version
> > >
> > > Used .config below.
> >
> > [snip]
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2019-08-21 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 14:08 OMAP DRM regression on N900 Aaro Koskinen
2019-08-21 18:31 ` Laurent Pinchart
2019-08-21 18:45 ` Adam Ford
2019-08-21 18:51 ` Laurent Pinchart [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=20190821185127.GD26759@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=aaro.koskinen@iki.fi \
--cc=aford173@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tomi.valkeinen@ti.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