From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753380AbcEYIci (ORCPT ); Wed, 25 May 2016 04:32:38 -0400 Received: from webbox1416.server-home.net ([77.236.96.61]:45471 "EHLO webbox1416.server-home.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751799AbcEYIcg (ORCPT ); Wed, 25 May 2016 04:32:36 -0400 From: Alexander Stein To: Stefan Agner Cc: Meng Yi , dri-devel@lists.freedesktop.org, David Airlie , airlied@redhat.com, linux-kernel@vger.kernel.org, Mark Brown Subject: Re: fsl-dcu not works on latest "drm-next" Date: Wed, 25 May 2016 10:32:27 +0200 Message-ID: <1895743.ZKMIL6pEz5@ws-stein> User-Agent: KMail/4.14.10 (Linux/4.4.6-gentoo; KDE/4.14.16; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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