From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: intel-gfx@lists.freedesktop.org
Subject: [RFC] async CRTC enable/disable hack
Date: Fri, 13 Dec 2013 11:26:51 -0800 [thread overview]
Message-ID: <1386962813-2058-1-git-send-email-jbarnes@virtuousgeek.org> (raw)
Obviously still need a lot of work (and I didn't quite get the patch
split correctly, I meant commit the first bits earlier).
I think the approach may be sound though, and is actually not too hard
to get right with all the cross checking we have in place. Things to
fix:
- modeset cross check - we don't want to sync after a mode set just to
check, maybe we could put this off until the actual enable happens
- split flushing of disable and enable to actually make full mode sets
fast
Anyway this is just a sketch of something we might do, definitely not
intended for upstream anytime soon.
Thanks,
Jesse
next reply other threads:[~2013-12-13 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 19:26 Jesse Barnes [this message]
2013-12-13 19:26 ` [PATCH 1/2] drm/i915: wrap crtc enable/disable Jesse Barnes
2013-12-13 19:26 ` [PATCH 2/2] drm/i915: make crtc enable/disable asynchronous Jesse Barnes
2013-12-13 20:52 ` [RFC] async CRTC enable/disable hack 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=1386962813-2058-1-git-send-email-jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.