From: Thierry Reding <thierry.reding@gmail.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
uma.shankar@intel.com
Subject: Re: Design review request: DRM color manager
Date: Thu, 15 May 2014 09:05:59 +0200 [thread overview]
Message-ID: <20140515070558.GA5952@ulmo> (raw)
In-Reply-To: <53744F1E.6060107@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 815 bytes --]
On Thu, May 15, 2014 at 10:52:38AM +0530, Sharma, Shashank wrote:
[...]
> Please note that the color correction methods changes per platform and
> what's valid for one Intel platform may not be valid for other. So the
> atomic modeset should have a clear idea of what is supported on which
> platforms.
I don't think this will be an issue at all. The DRM driver should only
expose what's supported on the particular device that it drives. And
similarily userspace drivers should enumerate properties to find out
which ones are available. Atomic modeset is only the mechanism to make
sure it's all applied in one go. But that mechanism is completely
generic and can be applied to any properties, therefore no specific
knowledge about the available properties will be required in atomic
modesetting itself.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-05-15 7:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 6:31 Design review request: DRM color manager Sharma, Shashank
2014-04-22 4:11 ` Sharma, Shashank
2014-04-22 9:37 ` David Herrmann
2014-04-22 10:21 ` Sharma, Shashank
2014-04-22 11:39 ` David Herrmann
2014-04-22 12:07 ` Sharma, Shashank
2014-04-22 13:47 ` Daniel Vetter
2014-04-22 15:01 ` Sharma, Shashank
[not found] ` <FF3DDC77922A8A4BB08A3BC48A1EA8CB0169DE73@BGSMSX101.gar.corp.intel.com>
2014-05-07 14:22 ` Sharma, Shashank
2014-05-12 4:38 ` Sharma, Shashank
2014-05-12 8:51 ` Daniel Vetter
2014-05-12 10:26 ` Sharma, Shashank
2014-05-12 11:50 ` David Herrmann
2014-05-12 12:05 ` Sharma, Shashank
2014-05-12 15:28 ` Daniel Vetter
2014-05-12 16:00 ` [Intel-gfx] " David Herrmann
2014-05-13 3:48 ` Sharma, Shashank
2014-05-14 15:54 ` Thierry Reding
2014-05-15 5:22 ` Sharma, Shashank
2014-05-15 7:05 ` Thierry Reding [this message]
2014-05-15 7:39 ` Sharma, Shashank
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=20140515070558.GA5952@ulmo \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shashank.sharma@intel.com \
--cc=uma.shankar@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