Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Uma Shankar <uma.shankar@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ville.syrjala@intel.com, ajax@redhat.com, maarten.lankhorst@intel.com
Subject: Re: [v2 0/2] Add Colorspace connector property interface
Date: Sat, 3 Nov 2018 11:08:05 +0530	[thread overview]
Message-ID: <62c2a902-47c1-29fe-417f-8aa0b7f3d6b0@intel.com> (raw)
In-Reply-To: <1540987546-3142-1-git-send-email-uma.shankar@intel.com>

Hello Uma,

My comments inline.


On 10/31/2018 5:35 PM, Uma Shankar wrote:
> 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 curremt property infrastructure is
> not supporting it.
I am not very sure about this part, consider a situation where, I have 
connected a HDMI 2.0 monitor which supports BT2020 gamut, to a GEN9 
device, running an user-space which can also support BT2020 playback / 
HDR playback. Now, both monitor and user-space supports BT2020 playback, 
but the HW doesn't, and this will create a problem during playback. So I 
gess we need to expose a kernel Cap or property to showcase if the HW 
can support BT2020/DCI-P3 gamut space or not.

- Shashank
> 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.
>
> Uma Shankar (2):
>    drm: Add colorspace property
>    drm/i915: Attach colorspace property and enable modeset
>
>   drivers/gpu/drm/drm_atomic_uapi.c   |  4 ++++
>   drivers/gpu/drm/drm_connector.c     | 44 +++++++++++++++++++++++++++++++++++++
>   drivers/gpu/drm/i915/intel_atomic.c |  1 +
>   drivers/gpu/drm/i915/intel_hdmi.c   |  5 +++++
>   include/drm/drm_connector.h         |  7 ++++++
>   include/drm/drm_mode_config.h       |  6 +++++
>   include/uapi/drm/drm_mode.h         | 24 ++++++++++++++++++++
>   7 files changed, 91 insertions(+)
>

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

      parent reply	other threads:[~2018-11-03  5:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 12:05 [v2 0/2] Add Colorspace connector property interface Uma Shankar
2018-10-31 12:05 ` [v2 1/2] drm: Add colorspace property Uma Shankar
2018-11-02  9:19   ` [Intel-gfx] " Maarten Lankhorst
2018-11-02 11:29     ` Ville Syrjälä
2018-11-02 14:13       ` Shankar, Uma
2018-11-02 14:29         ` Jonas Karlman
2018-11-05  9:35           ` [Intel-gfx] " Hans Verkuil
2018-11-03  5:56   ` Sharma, Shashank
2018-10-31 12:05 ` [v2 2/2] drm/i915: Attach colorspace property and enable modeset Uma Shankar
2018-11-02  9:23   ` Maarten Lankhorst
2018-11-02 14:18     ` Shankar, Uma
2018-11-02 15:41       ` [Intel-gfx] " Ville Syrjälä
2018-11-02 15:44         ` Maarten Lankhorst
2018-11-02 15:49           ` Ville Syrjälä
2018-11-03  6:21   ` Sharma, Shashank
2018-10-31 12:45 ` ✗ Fi.CI.CHECKPATCH: warning for Add Colorspace connector property interface (rev2) Patchwork
2018-10-31 12:48 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-10-31 12:59 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-03  5:38 ` Sharma, Shashank [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=62c2a902-47c1-29fe-417f-8aa0b7f3d6b0@intel.com \
    --to=shashank.sharma@intel.com \
    --cc=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@intel.com \
    --cc=uma.shankar@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