From: Lyude Paul <lyude@redhat.com>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@linux.ie>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>
Subject: [PATCH v3 0/3] drm/i915: MST and wakeref leak fixes
Date: Tue, 29 Jan 2019 14:09:58 -0500 [thread overview]
Message-ID: <20190129191001.442-1-lyude@redhat.com> (raw)
While trying to fix a problem with suspend/resume that I introduced in
the atomic VCPI helpers for MST, I also ran into some issues with i915
varying from "not that bad" to "oh wow that's very bad". Here are the
fixes for those issues.
This series was originally just one patch,
"drm/i915: Don't send MST hotplugs during resume"
Lyude Paul (3):
drm/i915: Block fbdev HPD processing during suspend
drm/i915: Don't send MST hotplugs during resume
drm/i915: Don't send hotplug in intel_dp_check_mst_status()
drivers/gpu/drm/i915/intel_dp.c | 13 ++++++------
drivers/gpu/drm/i915/intel_drv.h | 10 +++++++++
drivers/gpu/drm/i915/intel_fbdev.c | 33 +++++++++++++++++++++++++++++-
3 files changed, 49 insertions(+), 7 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-29 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 19:09 Lyude Paul [this message]
2019-01-29 19:09 ` [PATCH v3 1/3] drm/i915: Block fbdev HPD processing during suspend Lyude Paul
2019-01-29 19:20 ` Chris Wilson
2019-01-29 19:10 ` [PATCH v3 2/3] drm/i915: Don't send MST hotplugs during resume Lyude Paul
2019-02-06 19:32 ` Ville Syrjälä
2019-01-29 19:10 ` [PATCH v3 3/3] drm/i915: Don't send hotplug in intel_dp_check_mst_status() Lyude Paul
2019-02-06 19:33 ` [Intel-gfx] " Ville Syrjälä
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=20190129191001.442-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.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