[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <HE1PR04MB1051BEA60168E078AEEDCA54EC5D0@HE1PR04MB1051.eurprd04.prod.outlook.com>
Date: Tue, 7 Jun 2016 02:16:00 +0000
From: Meng Yi <meng.yi@....com>
To: Stefan Agner <stefan@...er.ch>,
Alexander Stein <alexander.stein@...tec-electronic.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
David Airlie <airlied@...ux.ie>,
"airlied@...hat.com" <airlied@...hat.com>
Subject: RE: fsl-dcu not works on latest "drm-next"
Hi Stefan,
Sorry for reply late, I was on PTO. And another PTO on June 9~11, 2016.UTC+8
> >> static const struct regmap_config fsl_dcu_regmap_config = {
> >> .reg_bits = 32,
> >> .reg_stride = 4,
> >> .val_bits = 32,
> >> .cache_type = REGCACHE_RBTREE,
> >
> > This needs to be a flat cache. See
> > https://lists.freedesktop.org/archives/dri-devel/2016-January/099121.h
> > tml or https://lkml.org/lkml/2016/3/24/281
> > max_register also needs an appropriate value.
>
> Ok, since the complete set which switches to the atomic helper is not stable
> material (and also won't make it into 4.7 anymore), I created a seperate bugfix
> now:
> https://lists.freedesktop.org/archives/dri-devel/2016-June/109625.html
>
What is bug?
> What I don't quite get yet is the REGCACHE_FLAT influencing the endianness
> behavior?
>
> If it is, Meng, can you test again with v4.7-rc1 + the FLAT cache patch above?
>
I will test it, and send an e-mail to you by then.
Regards,
Meng
Powered by blists - more mailing lists