From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
linux-fbdev-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: [PATCH 0/2] fbcon+i915 locking fixes
Date: Wed, 23 Jan 2013 17:25:07 +0100 [thread overview]
Message-ID: <1358958309-5342-1-git-send-email-daniel.vetter@ffwll.ch> (raw)
Hi Dave,
First patch is a resend of Alan's fbcon vs. fb notifier deadlock fix.
Without this lockdep is pretty much useless for debugging drm locking
issues, and it looks like quite a few bootup hangs could be blamed on this
one, too.
Since the fbdev maintainer seems to be awol, please merge this through
your drm tree. I've looked through the patch and the new locking seems to
be sane so feel free to smash a
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
onto it.
2nd patch is a locking bug in the i915 driver with the new kms locking.
Since the bug only happens in your drm-next tree, please apply the patch
there directly.
Thanks, Daniel
Alan Cox (1):
fb: Rework locking to fix lock ordering on takeover
Daniel Vetter (1):
drm/i915: fixup crtc locking in intel_release_load_detect_pipe
drivers/gpu/drm/i915/intel_display.c | 1 +
drivers/tty/vt/vt.c | 81 ++++++++++++++++++++++++++--------
drivers/video/console/fbcon.c | 30 ++++++++++++-
drivers/video/fbmem.c | 5 +--
drivers/video/fbsysfs.c | 3 ++
include/linux/console.h | 1 +
6 files changed, 98 insertions(+), 23 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-01-23 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 16:25 Daniel Vetter [this message]
2013-01-23 16:25 ` [PATCH 1/2] fb: Rework locking to fix lock ordering on takeover Daniel Vetter
2013-01-23 16:38 ` Takashi Iwai
2013-01-23 16:49 ` Daniel Vetter
2013-01-23 16:25 ` [PATCH 2/2] drm/i915: fixup per-crtc locking in intel_release_load_detect_pipe Daniel Vetter
2013-01-24 9:55 ` Daniel Vetter
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=1358958309-5342-1-git-send-email-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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