From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
Kausal Malladi <Kausal.Malladi@intel.com>
Cc: annie.j.matheson@intel.com, dhanya.p.r@intel.com,
dri-devel@lists.freedesktop.org, vijay.a.purushothaman@intel.com,
jesse.barnes@intel.com, daniel.vetter@intel.com,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 04/10] drm: Add Gamma correction structure
Date: Sat, 06 Jun 2015 17:21:41 +0530 [thread overview]
Message-ID: <5572DECD.3040500@intel.com> (raw)
In-Reply-To: <20150606010049.GG1099@intel.com>
Regards
Shashank
On 6/6/2015 6:30 AM, Matt Roper wrote:
> On Thu, Jun 04, 2015 at 07:12:35PM +0530, Kausal Malladi wrote:
>> From: Kausal Malladi <Kausal.Malladi@intel.com>
>>
>> This patch adds a new structure in DRM layer for Gamma color correction.
>> This structure will be used by all user space agents to configure
>> appropriate Gamma precision and Gamma level.
>>
>> struct drm_intel_gamma {
>> __u32 gamma_level;
>> (The gamma_level variable indicates if the Gamma correction is to be
>> applied on Pipe/plane)
>
> I'm not sure I understand the need for this one...you're getting the
> set_property call against a specific DRM object, so I don't think there
> should be any confusion at that point about what the values apply to?
>
Actually that is for the get_property path. If you have a look at the
design document, there is a provision to query the current applied gamma
which can be pipe/plane level. Hence keeping this.
>
>> __u32 gamma_precision;
>> (The Gamma precision indicates the Gamma mode to be applied)
>>
>> Supported precisions are -
>> #define I915_GAMMA_PRECISION_UNKNOWN 0
>> #define I915_GAMMA_PRECISION_CURRENT 0xFFFFFFFF
>> #define I915_GAMMA_PRECISION_LEGACY (1 << 0)
>> #define I915_GAMMA_PRECISION_10BIT (1 << 1)
>> #define I915_GAMMA_PRECISION_12BIT (1 << 2)
>> #define I915_GAMMA_PRECISION_14BIT (1 << 3)
>> #define I915_GAMMA_PRECISION_16BIT (1 << 4)
>
> I feel like the precision would work better as a separate enum property
> rather than being part of your blob; I think it would be cleaner if your
> blob only held the actual values if possible.
>
Again, this would be required for the get_property path. If we create a
separate property for this, the design might be very complex.
This is the current implementation:
1. Pack the correction values and configurations in blob()
2. call a create_blob() and get the blob_id
3. do a set_porperty() with the blob_id
4. set_property will find this blob, with the blob_id and apply
corrections.
Adding a separate property for gamma_level will add one more state here,
which will make it further complex. Do you agree ?
>>
>> __u32 num_samples;
>> (The num_samples indicates the number of Gamma correction
>> coefficients)
>> __u32 reserved;
>> __u16 values[0];
>> (An array of size 0, to accommodate the "num_samples" number of
>> R16G16B16 pixels, dynamically)
>> };
>>
>> v2: Addressing Daniel Stone's comment, added a variable sized array to
>> carry Gamma correction values as blob property.
>>
>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>> Signed-off-by: Kausal Malladi <Kausal.Malladi@intel.com>
>> ---
>> include/drm/drm_crtc.h | 3 +++
>> include/uapi/drm/drm.h | 10 ++++++++++
>> 2 files changed, 13 insertions(+)
>>
>> diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h
>> index 2a75d7d..bc44f27 100644
>> --- a/include/drm/drm_crtc.h
>> +++ b/include/drm/drm_crtc.h
>> @@ -483,6 +483,9 @@ struct drm_crtc {
>> * acquire context.
>> */
>> struct drm_modeset_acquire_ctx *acquire_ctx;
>> +
>> + /* Color Management Blob IDs */
>> + u32 gamma_blob_id;
>> };
>>
>> /**
>> diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
>> index 3801584..fc2661c 100644
>> --- a/include/uapi/drm/drm.h
>> +++ b/include/uapi/drm/drm.h
>> @@ -829,6 +829,16 @@ struct drm_event_vblank {
>> __u32 reserved;
>> };
>>
>> +/* Color Management structure for Gamma */
>> +struct drm_gamma {
>> + __u32 flags;
>
> The flags aren't described in your commit message...what are they used
> for? I guess it will become more clear as I read farther through your
> patch series.
>
>
> Matt
We are currently using this to define gamma/degamma as such, but yes I
agree that we have added this for future / undefined last minute usages,
and can be removed.
>
>
>> + __u32 gamma_level;
>> + __u32 gamma_precision;
>> + __u32 num_samples;
>> + __u32 reserved;
>> + __u16 values[0];
>> +};
>> +
>> /* typedef area */
>> #ifndef __KERNEL__
>> typedef struct drm_clip_rect drm_clip_rect_t;
>> --
>> 2.4.2
>>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-06 11:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1433425361-17864-1-git-send-email-Kausal.Malladi@intel.com>
2015-06-05 4:01 ` [PATCH v2 00/10] Color Manager Implementation Jindal, Sonika
2015-06-05 9:28 ` Malladi, Kausal
[not found] ` <1433425361-17864-5-git-send-email-Kausal.Malladi@intel.com>
2015-06-05 12:00 ` [PATCH v2 04/10] drm: Add Gamma correction structure Jindal, Sonika
2015-06-05 12:25 ` Malladi, Kausal
2015-06-12 17:17 ` Emil Velikov
2015-06-14 9:02 ` Sharma, Shashank
2015-06-18 15:00 ` Emil Velikov
2015-06-06 1:00 ` Matt Roper
2015-06-06 11:51 ` Sharma, Shashank [this message]
2015-06-09 0:48 ` Matt Roper
2015-06-09 11:06 ` Damien Lespiau
[not found] ` <1433425361-17864-6-git-send-email-Kausal.Malladi@intel.com>
2015-06-06 1:00 ` [PATCH v2 05/10] drm: Add a new function for updating color blob Matt Roper
2015-06-06 11:54 ` Sharma, Shashank
2015-06-09 0:53 ` Matt Roper
[not found] ` <1433425361-17864-7-git-send-email-Kausal.Malladi@intel.com>
2015-06-06 1:01 ` [PATCH v2 06/10] drm: Avoid atomic commit path for CRTC property (Gamma) Matt Roper
2015-06-06 12:04 ` Sharma, Shashank
2015-06-09 0:58 ` Matt Roper
2015-06-19 22:50 ` [Intel-gfx] " Matt Roper
2015-06-24 15:40 ` Malladi, Kausal
2015-06-24 21:37 ` Matheson, Annie J
[not found] ` <1433425361-17864-8-git-send-email-Kausal.Malladi@intel.com>
2015-06-06 5:33 ` [PATCH v2 07/10] drm/i915: Add pipe level Gamma correction for CHV/BSW Jindal, Sonika
2015-06-06 12:09 ` Sharma, Shashank
2015-06-09 11:23 ` Damien Lespiau
2015-06-09 11:51 ` Damien Lespiau
2015-06-09 14:15 ` Damien Lespiau
2015-06-09 10:11 ` [PATCH v2 00/10] Color Manager Implementation Damien Lespiau
2015-06-11 7:57 ` Malladi, Kausal
2015-06-11 9:04 ` Jani Nikula
[not found] ` <1433425361-17864-2-git-send-email-Kausal.Malladi@intel.com>
2015-06-06 1:00 ` [PATCH v2 01/10] drm/i915: Initialize Color Manager Matt Roper
2015-06-06 11:42 ` Sharma, Shashank
2015-06-09 10:34 ` Damien Lespiau
2015-06-09 14:26 ` Damien Lespiau
[not found] ` <1433425361-17864-3-git-send-email-Kausal.Malladi@intel.com>
2015-06-09 10:54 ` [PATCH v2 02/10] drm/i915: Attach color properties to CRTC Damien Lespiau
[not found] ` <1433425361-17864-9-git-send-email-Kausal.Malladi@intel.com>
2015-06-09 11:53 ` [PATCH v2 08/10] drm: Add CSC correction structure Damien Lespiau
2015-06-09 14:58 ` Damien Lespiau
[not found] ` <1433425361-17864-11-git-send-email-Kausal.Malladi@intel.com>
2015-06-09 11:55 ` [PATCH v2 10/10] drm/i915: Add CSC support for CHV/BSW Damien Lespiau
2015-06-09 12:50 ` [PATCH v2 00/10] Color Manager Implementation Damien Lespiau
2015-06-15 6:53 ` [Intel-gfx] " Daniel Vetter
2015-06-15 20:30 ` Matheson, Annie J
2015-06-16 3:12 ` Sharma, Shashank
2015-06-16 22:10 ` Matheson, Annie J
2015-07-13 8:29 ` Hans Verkuil
2015-07-13 9:18 ` Daniel Vetter
2015-07-13 9:43 ` [Intel-gfx] " Hans Verkuil
2015-07-13 9:54 ` Daniel Vetter
2015-07-13 10:11 ` Hans Verkuil
2015-07-13 14:07 ` [Intel-gfx] " Daniel Vetter
2015-07-14 8:17 ` Hans Verkuil
2015-07-14 9:11 ` Daniel Vetter
2015-07-14 9:35 ` Hans Verkuil
2015-07-14 10:16 ` [Intel-gfx] " Daniel Vetter
2015-07-15 12:35 ` Hans Verkuil
2015-07-15 13:28 ` [Intel-gfx] " Hans Verkuil
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=5572DECD.3040500@intel.com \
--to=shashank.sharma@intel.com \
--cc=Kausal.Malladi@intel.com \
--cc=annie.j.matheson@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dhanya.p.r@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=matthew.d.roper@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