From: Daniel Vetter <daniel@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Rob Bradford <robert.bradford@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Liviu Dudau <liviu.dudau@arm.com>,
Stefan Schake <stschake@gmail.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Vincent Abriou <vincent.abriou@st.com>,
amd-gfx@lists.freedesktop.org,
Uma Shankar <uma.shankar@intel.com>,
James Wang <james.qian.wang@arm.com>,
"Kumar, Kiran S" <kiran.s.kumar@intel.com>,
Mali DP Maintainers <malidp@foss.arm.com>,
Daniel Stone <daniels@collabora.com>, Leo Li <sunpeng.li@amd.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Boris Brezillon <bbrezillon@kernel.org>,
Philippe Cornu <philippe.cornu@st.com>,
Yannick Fertre <yannick.fertre@st.com>,
Kausal Malladi <kausalmalladi@gmail.com>
Subject: Re: [PATCH] drm/gamma: Clarify gamma lut uapi
Date: Tue, 2 Apr 2019 09:59:39 +0200 [thread overview]
Message-ID: <20190402075939.GD2665@phenom.ffwll.local> (raw)
In-Reply-To: <20190329092027.3430-1-daniel.vetter@ffwll.ch>
On Fri, Mar 29, 2019 at 10:20:27AM +0100, Daniel Vetter wrote:
> Interpreting it as a 0.16 fixed point means we can't accurately
> represent 1.0. Which is one of the values we really should be able to
> represent.
>
> Since most (all?) luts have lower precision this will only affect
> rounding of 0xffff.
>
> Cc: Uma Shankar <uma.shankar@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Shashank Sharma <shashank.sharma@intel.com>
> Cc: "Kumar, Kiran S" <kiran.s.kumar@intel.com>
> Cc: Kausal Malladi <kausalmalladi@gmail.com>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Rob Bradford <robert.bradford@intel.com>
> Cc: Daniel Stone <daniels@collabora.com>
> Cc: Stefan Schake <stschake@gmail.com>
> Cc: Eric Anholt <eric@anholt.net>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Leo Li <sunpeng.li@amd.com>
> Cc: amd-gfx@lists.freedesktop.org
> Cc: James (Qian) Wang <james.qian.wang@arm.com>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
> Cc: Mali DP Maintainers <malidp@foss.arm.com>
> Cc: CK Hu <ck.hu@mediatek.com>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Cc: Yannick Fertre <yannick.fertre@st.com>
> Cc: Philippe Cornu <philippe.cornu@st.com>
> Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org>
> Cc: Vincent Abriou <vincent.abriou@st.com>
> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Cc: Boris Brezillon <bbrezillon@kernel.org>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Applied, thanks for all the reviews.
-Daniel
> ---
> include/uapi/drm/drm_mode.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h
> index 09d72966899a..83cd1636b9be 100644
> --- a/include/uapi/drm/drm_mode.h
> +++ b/include/uapi/drm/drm_mode.h
> @@ -621,7 +621,8 @@ struct drm_color_ctm {
>
> struct drm_color_lut {
> /*
> - * Data is U0.16 fixed point format.
> + * Values are mapped linearly to 0.0 - 1.0 range, with 0x0 == 0.0 and
> + * 0xffff == 1.0.
> */
> __u16 red;
> __u16 green;
> --
> 2.20.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-04-02 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 9:20 [PATCH] drm/gamma: Clarify gamma lut uapi Daniel Vetter
2019-03-29 14:26 ` Liviu Dudau
2019-03-29 14:29 ` Lionel Landwerlin
2019-03-29 14:36 ` Ville Syrjälä
[not found] ` <20190329092027.3430-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2019-03-29 15:23 ` Matt Roper
2019-03-29 17:31 ` Maarten Lankhorst
2019-03-29 15:47 ` Philippe CORNU
2019-04-02 7:59 ` Daniel Vetter [this message]
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=20190402075939.GD2665@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bbrezillon@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=kausalmalladi@gmail.com \
--cc=kiran.s.kumar@intel.com \
--cc=liviu.dudau@arm.com \
--cc=malidp@foss.arm.com \
--cc=philippe.cornu@st.com \
--cc=robert.bradford@intel.com \
--cc=stschake@gmail.com \
--cc=sunpeng.li@amd.com \
--cc=tomi.valkeinen@ti.com \
--cc=uma.shankar@intel.com \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.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