public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: annie.j.matheson@intel.com, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, vijay.a.purushothaman@intel.com,
	jesse.barnes@intel.com, daniel.vetter@intel.com,
	dhanya.p.r@intel.com
Subject: Re: [PATCH 04/12] drm: Add structures for querying color capabilities
Date: Fri, 3 Jul 2015 11:28:41 +0100	[thread overview]
Message-ID: <20150703102841.GC15101@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20150703064131.GE23343@phenom.ffwll.local>

On Fri, Jul 03, 2015 at 08:41:31AM +0200, Daniel Vetter wrote:
> > Yeah. My first idea for the gamma stuff was that we'd simply have the
> > blob property for the data, and then a separate enum property which
> > decides how we interpret the blob contents. The default for the enum
> > would be the 8bpc/256 entries thing always, but the other values could
> > be potentially hardware specific. Obviously this would limit the use of
> > the fancier modes to the atomic API since you'd need to configure both
> > the blob and enum at the same time. But I don't see why we shouldn't
> > be allowed to rely on atomic from now on.
> 
> Yeah, enum+blob is what I like too. We can do one gamma table format enum
> in drm core. And drivers can then create it with just the enum values they
> actually support, similar to how we have rotation/mirror defines for
> everything, but the driver doesn't necessarily support it all. And the
> enum would fully encode everything there is to know about a layout, i.e.
> including excat precision and stuff like the 1025th/513th additional entry
> we have in some intel gamma tables.

I'm assuming you're still talking about 3 separate properties though?
pre-csc lut, csc, post-csc lut?

-- 
Damien

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-07-03 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1435765702-3094-1-git-send-email-Kausal.Malladi@intel.com>
     [not found] ` <1435765702-3094-10-git-send-email-Kausal.Malladi@intel.com>
2015-07-02 16:00   ` [PATCH 09/12] drm/i915: Add pipe level Gamma correction for CHV/BSW Damien Lespiau
2015-07-03  8:03     ` Jani Nikula
2015-07-03  8:29       ` [Intel-gfx] " Malladi, Kausal
2015-07-03  8:58         ` Jani Nikula
     [not found] ` <1435765702-3094-5-git-send-email-Kausal.Malladi@intel.com>
2015-07-02 16:20   ` [PATCH 04/12] drm: Add structures for querying color capabilities Damien Lespiau
2015-07-02 16:45     ` Damien Lespiau
2015-07-02 17:04       ` [Intel-gfx] " Ville Syrjälä
2015-07-03  6:41         ` Daniel Vetter
2015-07-03 10:28           ` Damien Lespiau [this message]
2015-07-03 12:36             ` Ville Syrjälä
     [not found] ` <1435765702-3094-8-git-send-email-Kausal.Malladi@intel.com>
2015-07-02 16:30   ` [PATCH 07/12] drm: Add structures to set/get a palette color property Damien Lespiau
     [not found] ` <1435765702-3094-9-git-send-email-Kausal.Malladi@intel.com>
2015-07-02 16:32   ` [PATCH 08/12] drm: Export drm_property_replace_global_blob function Damien Lespiau
     [not found] ` <1435765702-3094-4-git-send-email-Kausal.Malladi@intel.com>
2015-07-02 16:25   ` [PATCH 03/12] drm/i915: Attach color properties to CRTC Damien Lespiau
2015-07-02 16:35   ` Damien Lespiau
2015-07-03  3:31 [PATCH 00/12] Color Manager Implementation Kausal Malladi
2015-07-03  3:31 ` [PATCH 04/12] drm: Add structures for querying color capabilities Kausal Malladi

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=20150703102841.GC15101@strange.ger.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=annie.j.matheson@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dhanya.p.r@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jesse.barnes@intel.com \
    --cc=vijay.a.purushothaman@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