From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Stefan Agner <stefan@agner.ch>
Cc: Meng Yi <meng.yi@nxp.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
airlied@redhat.com, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: fsl-dcu not works on latest "drm-next"
Date: Wed, 25 May 2016 10:32:27 +0200 [thread overview]
Message-ID: <1895743.ZKMIL6pEz5@ws-stein> (raw)
In-Reply-To: <b80923e8e32e9605c150a5de761db88a@agner.ch>
On Tuesday 24 May 2016 23:20:02, Stefan Agner wrote:
> On 2016-05-24 19:14, Meng Yi wrote:
> > I found that its regmap endianness issue, so I want to replace the
> > "regmap".
> Hm, replace with what? Note that we need some kind of endianness
> convertion since the IP is big endian on LS1021a and little endian on
> Vybrid (vf610).
Yep, regmap is required and was broken meanwhile but should be fixed now. See
linked lkml post.
> Is it maybe just an issue with regmap/the big-endian property in the
> device tree? Maybe this thread is interesting for you:
> https://lkml.org/lkml/2016/3/23/233
AFAICT device tree should not been changed here. The "big-endian" property was
there fromt he beginning.
> > 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
> >
> > And not works now. some log below:
Which commit actually broke your kernel? And where to fetch it from? Is your
problem really caused by regmap?
Best regards,
Alexander
next prev parent reply other threads:[~2016-05-25 8:32 UTC|newest]
Thread overview: 34+ 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
2016-05-04 3:40 ` Meng Yi
2016-05-25 2:14 ` Meng Yi
2016-05-25 6:20 ` Stefan Agner
2016-05-25 6:20 ` Stefan Agner
2016-05-25 8:32 ` Alexander Stein [this message]
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-26 9:11 ` Alexander Stein
2016-05-25 9:18 ` Mark Brown
2016-05-25 9:18 ` Mark Brown
2016-05-25 9:59 ` Meng Yi
2016-05-25 10:41 ` Mark Brown
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 5:54 ` Stefan Agner
2016-05-27 12:20 ` Mark Brown
2016-05-27 12:20 ` Mark Brown
2016-05-27 17:36 ` Stefan Agner
2016-05-27 17:36 ` Stefan Agner
2016-05-27 19:50 ` Mark Brown
2016-06-03 22:52 ` Stefan Agner
2016-06-03 22:52 ` Stefan Agner
2016-06-07 2:16 ` Meng Yi
2016-06-07 2:46 ` Stefan Agner
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=1895743.ZKMIL6pEz5@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meng.yi@nxp.com \
--cc=stefan@agner.ch \
/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.