From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [RFC PATCH 0/7] Convert to atomic, part 4.
Date: Fri, 19 Jun 2015 10:02:23 +0200 [thread overview]
Message-ID: <1434700950-16242-1-git-send-email-maarten.lankhorst@linux.intel.com> (raw)
The only thing missing after part 3 is restoring atomic readout and making
suspend/restore. With fixes for all identified causes of regressions from
atomic suspend being done in convert to atomic, part 3 it's time to worry
about getting atomic suspend/restore working again.
I do this in a few steps, first I re-introduce the old commit for hw state
readout, with fixes. After that I convert the atomic readout to a full initial
modeset, and finally I try to re-enable fastboot optimizations again by default,
in a less hacky way.
This is a RFC because of the following possible issues:
- mode->clock may not be read out correctly. It can differ slightly from the
actually set value, which forces a modeset anyway when it could be avoided.
- Not tested with DRRS support on DP, might be broken with fastboot?
Maarten Lankhorst (7):
drm/i915: Do not update pfit state when toggling crtc enabled.
drm/i915: Read hw state into an atomic state struct, try 2.
All changes from try2.
drm/i915: enable fastboot for everyone
drm/i915: Update power domains only on affected crtc's.
drm/i915: Always reset in intel_crtc_restore_mode
drm/i915: Make intel_display_suspend atomic, try 2.
drivers/gpu/drm/i915/i915_dma.c | 12 +-
drivers/gpu/drm/i915/i915_drv.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 7 +-
drivers/gpu/drm/i915/i915_params.c | 5 -
drivers/gpu/drm/i915/intel_atomic.c | 23 +-
drivers/gpu/drm/i915/intel_display.c | 1302 ++++++++++++++++++++--------------
drivers/gpu/drm/i915/intel_dp.c | 2 +-
drivers/gpu/drm/i915/intel_drv.h | 21 +-
drivers/gpu/drm/i915/intel_fbdev.c | 22 +-
drivers/gpu/drm/i915/intel_lvds.c | 2 +-
10 files changed, 786 insertions(+), 612 deletions(-)
--
2.1.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-06-19 8:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 8:02 Maarten Lankhorst [this message]
2015-06-19 8:02 ` [RFC PATCH 1/7] drm/i915: Do not update pfit state when toggling crtc enabled Maarten Lankhorst
2015-06-19 8:02 ` [RFC PATCH 2/7] drm/i915: Read hw state into an atomic state struct, try 2 Maarten Lankhorst
2015-06-19 9:38 ` Daniel Stone
2015-06-22 15:31 ` Daniel Vetter
2015-06-23 10:49 ` Maarten Lankhorst
2015-06-23 11:40 ` Daniel Vetter
2015-06-19 8:02 ` [RFC PATCH 3/7] All changes from try2 Maarten Lankhorst
2015-06-19 8:02 ` [RFC PATCH 4/7] drm/i915: enable fastboot for everyone Maarten Lankhorst
2015-06-22 15:21 ` Daniel Vetter
2015-06-23 10:38 ` Maarten Lankhorst
2015-06-23 11:50 ` Daniel Vetter
2015-06-19 8:02 ` [RFC PATCH 5/7] drm/i915: Update power domains only on affected crtc's Maarten Lankhorst
2015-06-19 8:02 ` [RFC PATCH 6/7] drm/i915: Always reset in intel_crtc_restore_mode Maarten Lankhorst
2015-06-22 15:25 ` Daniel Vetter
2015-06-19 8:02 ` [RFC PATCH 7/7] drm/i915: Make intel_display_suspend atomic, try 2 Maarten Lankhorst
2015-06-22 14:54 ` [RFC PATCH 0/7] Convert to atomic, part 4 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=1434700950-16242-1-git-send-email-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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