From: Emil Velikov <emil.l.velikov@gmail.com>
To: Kausal Malladi <Kausal.Malladi@intel.com>,
matthew.d.roper@intel.com, jesse.barnes@intel.com,
damien.lespiau@intel.com, sonika.jindal@intel.com,
durgadoss.r@intel.com, vijay.a.purushothaman@intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
hverkuil@xs4all.nl, daniel@fooishbar.org
Cc: annie.j.matheson@intel.com, emil.l.velikov@gmail.com,
dhanya.p.r@intel.com, daniel.vetter@intel.com
Subject: Re: [PATCH 07/12] drm: Add structures to set/get a palette color property
Date: Tue, 7 Jul 2015 19:01:59 +0100 [thread overview]
Message-ID: <559C1417.9030004@gmail.com> (raw)
In-Reply-To: <1435894307-5722-8-git-send-email-Kausal.Malladi@intel.com>
Hi Kausal,
On 03/07/15 04:31, Kausal Malladi wrote:
> This patch adds new structures in DRM layer for Palette color correction.
> These structures will be used by user space agents to configure
> appropriate number of samples and Palette LUT for a platform.
>
> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
> Signed-off-by: Kausal Malladi <Kausal.Malladi@intel.com>
> ---
> include/uapi/drm/drm.h | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
> index d9562a2..04a8f2a 100644
> --- a/include/uapi/drm/drm.h
> +++ b/include/uapi/drm/drm.h
> @@ -863,6 +863,18 @@ struct drm_color_caps {
> struct drm_cge_caps cge_caps;
> };
>
> +struct drm_r32g32b32 {
> + __u32 r32;
> + __u32 g32;
> + __u32 b32;
> +};
> +
I don't think this will work on a 64bit kernel with 32 bit userspace...
although I'm low on caffeine I could be imagining.
> +struct drm_palette {
> + __u32 version;
> + __u32 palette_num_samples;
> + struct drm_r32g32b32 palette_lut[0];
If memory serves me right, I've mentioned earlier that using zero sized
arrays might not be so good considering portability and using non GCC
compilers.
I believe your consern was about that using a pointer is inefficient.
Can you provide some references/hints how is that so ?
Thanks
Emil
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-07 18:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 3:31 [PATCH 00/12] Color Manager Implementation Kausal Malladi
2015-07-03 3:31 ` [PATCH 01/12] drm/i915: Atomic commit path fix for CRTC properties Kausal Malladi
2015-07-03 3:31 ` [PATCH 02/12] drm: Create Color Management DRM properties Kausal Malladi
2015-07-07 23:23 ` Matt Roper
2015-07-08 4:27 ` Malladi, Kausal
2015-07-03 3:31 ` [PATCH 03/12] drm/i915: Attach color properties to CRTC Kausal Malladi
2015-07-07 23:23 ` Matt Roper
2015-07-08 4:29 ` Malladi, Kausal
2015-07-03 3:31 ` [PATCH 04/12] drm: Add structures for querying color capabilities Kausal Malladi
2015-07-03 3:31 ` [PATCH 05/12] drm/i915: Load color capabilities for CHV CRTC Kausal Malladi
2015-07-03 3:31 ` [PATCH 06/12] drm/i915: Add atomic set property interface for CRTC Kausal Malladi
2015-07-03 3:31 ` [PATCH 07/12] drm: Add structures to set/get a palette color property Kausal Malladi
2015-07-07 18:01 ` Emil Velikov [this message]
2015-07-03 3:31 ` [PATCH 08/12] drm: Export drm_property_replace_global_blob function Kausal Malladi
2015-07-03 3:31 ` [PATCH 09/12] drm/i915: Add pipe level Gamma correction for CHV/BSW Kausal Malladi
2015-07-07 23:23 ` Matt Roper
2015-07-11 10:00 ` Malladi, Kausal
2015-07-03 3:31 ` [PATCH 10/12] drm/i915: Add DeGamma " Kausal Malladi
2015-07-03 3:31 ` [PATCH 11/12] drm: Add structure for set/get a CTM color property Kausal Malladi
2015-07-03 3:31 ` [PATCH 12/12] drm/i915: Add CSC correction for CHV/BSW Kausal Malladi
[not found] <1435765702-3094-1-git-send-email-Kausal.Malladi@intel.com>
[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
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=559C1417.9030004@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=Kausal.Malladi@intel.com \
--cc=annie.j.matheson@intel.com \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@intel.com \
--cc=daniel@fooishbar.org \
--cc=dhanya.p.r@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=durgadoss.r@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=sonika.jindal@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