From: Daniel Vetter <daniel@ffwll.ch>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/atomic: pass old crtc state to atomic_begin/flush.
Date: Mon, 15 Jun 2015 09:10:15 +0200 [thread overview]
Message-ID: <20150615071015.GE8341@phenom.ffwll.local> (raw)
In-Reply-To: <1434100702-15754-1-git-send-email-maarten.lankhorst@linux.intel.com>
On Fri, Jun 12, 2015 at 11:18:22AM +0200, Maarten Lankhorst wrote:
> In intel it's useful to keep track of some state changes with old
> crtc state vs new state, for example to disable initial planes or
> when a modeset's prevented during fastboot.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Hm, thus far the approach has been that the various ->check callbacks diff
the state and set appropriate stuff like needs_modeset or planes_changed.
And with intel_crtc->atomic we've kinda started to build up similar
things for i915. What do you plan to use this for?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-06-15 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 9:18 [PATCH] drm/atomic: pass old crtc state to atomic_begin/flush Maarten Lankhorst
2015-06-15 7:10 ` Daniel Vetter [this message]
2015-06-15 7:30 ` Maarten Lankhorst
2015-06-15 9:13 ` Daniel Vetter
2015-06-15 9:18 ` Maarten Lankhorst
2015-06-15 13:53 ` Daniel Vetter
2015-06-16 8:27 ` Ville Syrjälä
2015-06-16 9:59 ` [Intel-gfx] " 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=20150615071015.GE8341@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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