Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Uma Shankar <uma.shankar@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: ville.syrjala@intel.com, jonas@kwiboo.se, hansverk@cisco.com,
	maarten.lankhorst@intel.com
Subject: [v4 0/3] Add Colorspace connector property interface
Date: Tue, 27 Nov 2018 22:10:40 +0530	[thread overview]
Message-ID: <1543336843-22193-1-git-send-email-uma.shankar@intel.com> (raw)

This patch series creates a new connector property to program
colorspace to sink devices. Modern sink devices support more
than 1 type of colorspace like 601, 709, BT2020 etc. This helps
to switch based on content type which is to be displayed. The
decision lies with compositors as to in which scenarios, a
particular colorspace will be picked.

This will be helpful mostly to switch to higher gamut colorspaces
like BT2020 when the media content is encoded as BT2020. Thereby
giving a good visual experience to users.

The expectation from userspace is that it should parse the EDID
and get supported colorspaces. Use this property and switch to the
one supported. Kernel will not give the supported colorspaces since
this is panel dependent and our current property infrastructure is
not supporting it.

Have tested this using xrandr by using below command:
xrandr --output HDMI2 --set "Colorspace" "BT2020_rgb"

v2: Addressed Ville and Maarten's review comments. Merged the 2nd
and 3rd patch into one common logical patch.

v3: Removed Adobe references from enum definitions as per
Ville, Hans Verkuil and Jonas Karlman suggestions. Changed
default to an unset state where driver will assign the colorspace
when not chosen by user, suggested by Ville and Maarten. Addressed
other misc review comments from Maarten. Split the changes to
have separate colorspace property for DP and HDMI.

v4: Addressed Chris and Ville's review comments, and created a
common colorspace property for DP and HDMI, filtered the list
based on the colorspaces supported by the respective protocol
standard. Handled the default case more efficiently.

Uma Shankar (3):
  drm: Add HDMI colorspace property
  drm: Add DP colorspace property
  drm/i915: Attach colorspace property and enable modeset

 drivers/gpu/drm/drm_atomic_uapi.c      |  4 ++
 drivers/gpu/drm/drm_connector.c        | 92 ++++++++++++++++++++++++++++++++++
 drivers/gpu/drm/i915/intel_atomic.c    |  1 +
 drivers/gpu/drm/i915/intel_connector.c |  8 +++
 drivers/gpu/drm/i915/intel_drv.h       |  1 +
 drivers/gpu/drm/i915/intel_hdmi.c      | 18 +++++++
 include/drm/drm_connector.h            | 14 ++++++
 include/uapi/drm/drm_mode.h            | 33 ++++++++++++
 8 files changed, 171 insertions(+)

-- 
1.9.1

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

             reply	other threads:[~2018-11-27 16:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 16:40 Uma Shankar [this message]
2018-11-27 16:40 ` [v4 1/3] drm: Add HDMI colorspace property Uma Shankar
2018-11-28  1:01   ` kbuild test robot
2018-11-28 16:11   ` Sharma, Shashank
2018-11-29 14:44     ` Shankar, Uma
2018-11-27 16:40 ` [v4 2/3] drm: Add DP " Uma Shankar
2018-11-28 11:41   ` Brian Starkey
2018-11-28 13:59     ` Shankar, Uma
2018-11-28 16:13   ` Sharma, Shashank
2018-11-27 16:40 ` [v4 3/3] drm/i915: Attach colorspace property and enable modeset Uma Shankar
2018-11-28 20:49   ` kbuild test robot
2018-11-27 16:42 ` ✗ Fi.CI.CHECKPATCH: warning for Add Colorspace connector property interface (rev4) Patchwork
2018-11-27 16:45 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-27 17:05 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-27 20:58 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-11-28 11:56 ` [v4 0/3] Add Colorspace connector property interface Brian Starkey
2018-11-28 14:29   ` Shankar, Uma
2018-11-28 14:47     ` Brian Starkey
2018-11-29 14:40       ` Shankar, Uma

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=1543336843-22193-1-git-send-email-uma.shankar@intel.com \
    --to=uma.shankar@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hansverk@cisco.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jonas@kwiboo.se \
    --cc=maarten.lankhorst@intel.com \
    --cc=ville.syrjala@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