From: Stefan Agner <stefan@agner.ch>
To: Meng Yi <meng.yi@nxp.com>
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
airlied@redhat.com
Subject: RE: fsl-dcu not works on latest "drm-next"
Date: Mon, 06 Jun 2016 19:46:38 -0700 [thread overview]
Message-ID: <10773f1a55f10edeb22f56a4e2b42b97@agner.ch> (raw)
In-Reply-To: <HE1PR04MB1051BEA60168E078AEEDCA54EC5D0@HE1PR04MB1051.eurprd04.prod.outlook.com>
On 2016-06-06 19:16, Meng Yi wrote:
> 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?
>
The bug is that we should not use REGCACHE_RBTREE for MMIO registers...
--
Stefan
next prev parent reply other threads:[~2016-06-07 2:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR04MB105158F9CB2CEC73E6B5F5E9EC7A0@HE1PR04MB1051.eurprd04.prod.outlook.com>
2016-05-25 2:14 ` fsl-dcu not works on latest "drm-next" 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 [this message]
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=10773f1a55f10edeb22f56a4e2b42b97@agner.ch \
--to=stefan@agner.ch \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alexander.stein@systec-electronic.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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