From: Stefan Agner <stefan@agner.ch>
To: Meng Yi <meng.yi@nxp.com>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org
Subject: Re: fsl-dcu not works on latest "drm-next"
Date: Tue, 03 May 2016 09:08:02 -0700 [thread overview]
Message-ID: <7a4253f2639d1c7fe5e97dbfd8573f7b@agner.ch> (raw)
In-Reply-To: <HE1PR04MB105158F9CB2CEC73E6B5F5E9EC7A0@HE1PR04MB1051.eurprd04.prod.outlook.com>
Hi Meng,
Please use plain text mails on mailing lists.
On 2016-05-03 02:26, Meng Yi wrote:
> Hi,
>
> I just tested the latest drm-next branch on Freescale/NXP ls1021a-twr, and got some log below. And fsl-dcu not works.
>
> Since "drm-next" merged some branch , use git bisect had some problem ,
>
> so I manually checked out that "fsl-dcu" works at d761701c55a99598477f3cb25c03d939a7711e74
Hm, that commit seems rather unrelated... is that what git bisect told
you?
I guess my last pull request could be related to that, so maybe you can
check those two commits manually:
077d67374e ("drm: rcar-du: Fix compilation warning")
vs.
0449eefe2d ("drm/fsl-dcu: increment version and date")
>
> And not works now. some log below:
>
> [drm] Initialized drm 1.1.0 20060810
>
> panel supply power not found, using dummy regulator
>
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>
> [drm] No driver support for vblank timestamp query.
>
> ------------[ cut here ]------------
>
> WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_atomic_helper.c:1106 drm_atomic_helper_wait_for_vblanks+0xff/0x124
>
> [CRTC:24] vblank wait timed out
It seems that interrupt do not work properly. Could it be that work
elsewhere caused that issue?
--
Stefan
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-03 16:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 9:26 fsl-dcu not works on latest "drm-next" Meng Yi
2016-05-03 16:08 ` Stefan Agner [this message]
2016-05-04 3:40 ` Meng Yi
2016-05-25 2:14 ` Meng Yi
2016-05-25 6:20 ` Stefan Agner
2016-05-25 8:32 ` Alexander Stein
2016-05-25 8:58 ` Meng Yi
2016-05-25 9:57 ` Alexander Stein
2016-05-25 10:25 ` Meng Yi
2016-05-25 12:16 ` Alexander Stein
2016-05-26 8:18 ` Meng Yi
2016-05-26 9:11 ` Alexander Stein
2016-05-25 9:18 ` Mark Brown
2016-05-25 9:59 ` Meng Yi
2016-05-25 10:41 ` Mark Brown
2016-05-26 8:23 ` Meng Yi
2016-05-26 9:11 ` Alexander Stein
2016-05-27 5:54 ` Stefan Agner
2016-05-27 12:20 ` Mark Brown
2016-05-27 17:36 ` Stefan Agner
2016-05-27 19:50 ` Mark Brown
2016-06-03 22:52 ` Stefan Agner
2016-06-07 2:16 ` Meng Yi
2016-06-07 2:46 ` Stefan Agner
2016-06-07 3:47 ` Meng Yi
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=7a4253f2639d1c7fe5e97dbfd8573f7b@agner.ch \
--to=stefan@agner.ch \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=meng.yi@nxp.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