All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chandra Konduru <chandra.konduru@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v9] drm/i915/skl: Add support for SKL background color
Date: Tue, 24 Feb 2015 01:10:41 +0100	[thread overview]
Message-ID: <20150224001041.GJ24485@phenom.ffwll.local> (raw)
In-Reply-To: <1424477494-23472-1-git-send-email-chandra.konduru@intel.com>

On Fri, Feb 20, 2015 at 04:11:33PM -0800, Chandra Konduru wrote:
> @@ -11660,6 +11700,7 @@ static const struct drm_crtc_funcs intel_crtc_funcs = {
>  	.page_flip = intel_crtc_page_flip,
>  	.atomic_duplicate_state = intel_crtc_duplicate_state,
>  	.atomic_destroy_state = intel_crtc_destroy_state,
> +	.set_property = intel_crtc_set_property,

So in my internals mail about whether atomic blocks this I've missed that
atm we can't do any atomic crtc properties. And I really don't want to
slow down the atomic conversion by piling up more legacy cruft first, so I
think properties on the crtc like this one will get stalled a bit despite
what I've claimed.

I guess we need to discuss this in our mtg tomorrow.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-02-24  0:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  0:11 [PATCH v9] drm/i915/skl: Add support for SKL background color Chandra Konduru
2015-02-24  0:10 ` Daniel Vetter [this message]
2015-04-27 15:28 ` Ville Syrjälä
2015-04-27 20:33   ` Konduru, Chandra
2015-05-04  7:57     ` Daniel Vetter
2015-05-05 14:33       ` Ville Syrjälä
2015-05-06  8:57         ` 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=20150224001041.GJ24485@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chandra.konduru@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 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.