From: Mark Brown <broonie@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
linux-kernel@vger.kernel.org, Meng Yi <meng.yi@nxp.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
airlied@redhat.com
Subject: Re: fsl-dcu not works on latest "drm-next"
Date: Fri, 27 May 2016 20:50:48 +0100 [thread overview]
Message-ID: <20160527195048.GA29837@sirena.org.uk> (raw)
In-Reply-To: <40626c17a4e8960d20bfa07c59892bfa@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Fri, May 27, 2016 at 10:36:21AM -0700, Stefan Agner wrote:
> On 2016-05-27 05:20, Mark Brown wrote:
> > That's another way of addressing it of course, but unless the register
> > map actually is sparse it's probably still sensible to send the
> > conversion to flat cache as a fix.
> The regcache is used for suspend, but the suspend implementation in its
> current form is not in not working. Hence I felt it is not worth fixing
> part of something which is broken as a whole anyway.
> So far I was under the impression the "only" issue using REGCACHE_RBTREE
> is that it triggers a warning when enabling lockdep.
The warning is warning about a real issue that might crop up - it's not
just cosmetic, it's doing allocations inside a spinlock which could
break badly. Even if it doesn't help this issue I'd recommend getting a
fix in if you can to avoid it blowing up on people (unless the more
complete set of changes can go in as a bugfix of course in which case
it's moot).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-27 19:51 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 ` 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 [this message]
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=20160527195048.GA29837@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alexander.stein@systec-electronic.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®