All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Uma Shankar <uma.shankar@intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: dcastagna@chromium.org, emil.l.velikov@gmail.com,
	seanpaul@chromium.org, ville.syrjala@intel.com,
	maarten.lankhorst@intel.com
Subject: Re: [v7 0/9] Add HDR Metadata Parsing and handling in DRM layer
Date: Mon, 8 Apr 2019 15:01:26 +0530	[thread overview]
Message-ID: <177f83d1-de86-e357-1a28-e90b873df70f@intel.com> (raw)
In-Reply-To: <1554236430-7466-1-git-send-email-uma.shankar@intel.com>

Hello Uma,

V7 looks good to me, please feel free to use for the whole series:

Reviewed-by: Shashank Sharma <shashank.sharma@intel.com>

Regards

Shashank

On 4/3/2019 1:50 AM, Uma Shankar wrote:
> This patch series enables HDR support in drm. It basically defines
> HDR metadata structures, property to pass content (after blending)
> metadata from user space compositors to driver.
>
> Dynamic Range and Mastering infoframe creation and sending.
>
> ToDo:
> 1. We need to get the color framework in place for all planes
>     which support HDR content in hardware. This is already in progres
>     and patches are out for review in mailing list.
> 2. UserSpace/Compositors: Blending policies and metadata blob
>     creation and passing to driver. Work is already in progress
>     by Intel's middleware teams on wayland and the patches for
>     the same are in review.
>
> Please review and share your feedbacks/suggestions.
>
> Note: The intention for these patches is to get a design feedback on
> the uapi changes, generic property design and infoframe handling.
> This cannot get merged as of now without the userspace support in place.
>
> A POC has already been developed by Ville based on wayland. Please refer
> below link to see the component interactions and usage:
> https://lists.freedesktop.org/archives/wayland-devel/2017-December/036403.html
>
> v2: Updated Ville's POC changes to the patch series.Incorporated cleanups
> and fixes from Ville. Rebase on latest drm-tip.
>
> v3: Fixed a warning causing builds to break on CI. No major change.
>
> v4: Addressed Shashank's review comments.
>
> v5: Rebase on top of Ville's infoframe refactoring changes. Fixed non modeset
> case for HDR metadata update. Dropped a redundant patch.
>
> v6: Addressed Shashank's review comments and added RB's received.
>
> v7: Squashed 2 patches, dropped 1 change and addressed Brian Starkey's and
> Shashank's review comments.
>
> Note: Media driver and VAAPI changes for HDR are already out, with compositors
> changes also expected to land soon. Weston changes already floated and reviews
> started in community and is in active development along with GL efforts.
>
> Uma Shankar (7):
>    drm: Add HDR source metadata property
>    drm: Parse HDR metadata info from EDID
>    drm: Enable HDR infoframe support
>    drm/i915: Attach HDR metadata property to connector
>    drm/i915: Write HDR infoframe and send to panel
>    drm/i915:Enabled Modeset when HDR Infoframe changes
>    drm/i915: Set Infoframe for non modeset case for HDR
>
> Ville Syrjälä (2):
>    drm/i915: Add HLG EOTF
>    drm/i915: Enable infoframes on GLK+ for HDR
>
>   drivers/gpu/drm/drm_atomic.c        |   2 +
>   drivers/gpu/drm/drm_atomic_uapi.c   |  13 +++
>   drivers/gpu/drm/drm_connector.c     |   6 ++
>   drivers/gpu/drm/drm_edid.c          | 102 ++++++++++++++++++++
>   drivers/gpu/drm/i915/i915_reg.h     |   4 +
>   drivers/gpu/drm/i915/intel_atomic.c |  14 ++-
>   drivers/gpu/drm/i915/intel_ddi.c    |  13 +++
>   drivers/gpu/drm/i915/intel_drv.h    |   1 +
>   drivers/gpu/drm/i915/intel_hdmi.c   |  79 ++++++++++++++-
>   drivers/video/hdmi.c                | 186 ++++++++++++++++++++++++++++++++++++
>   include/drm/drm_connector.h         |  10 ++
>   include/drm/drm_edid.h              |   5 +
>   include/drm/drm_mode_config.h       |   6 ++
>   include/linux/hdmi.h                |  38 ++++++++
>   include/uapi/drm/drm_mode.h         |  22 +++++
>   15 files changed, 496 insertions(+), 5 deletions(-)
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2019-04-08  9:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 20:20 [v7 0/9] Add HDR Metadata Parsing and handling in DRM layer Uma Shankar
2019-04-02 20:14 ` ✗ Fi.CI.CHECKPATCH: warning for Add HDR Metadata Parsing and handling in DRM layer (rev7) Patchwork
2019-04-02 20:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-04-02 20:20 ` [v7 1/9] drm: Add HDR source metadata property Uma Shankar
2019-04-02 20:39   ` Sam Ravnborg
2019-04-08 10:20   ` Jonas Karlman
2019-04-09 16:17     ` Shankar, Uma
2019-04-02 20:20 ` [v7 2/9] drm: Parse HDR metadata info from EDID Uma Shankar
2019-04-02 20:20 ` [v7 3/9] drm: Enable HDR infoframe support Uma Shankar
2019-04-02 20:37   ` Sam Ravnborg
2019-04-02 20:20 ` [v7 4/9] drm/i915: Attach HDR metadata property to connector Uma Shankar
2019-04-02 20:20 ` [v7 5/9] drm/i915: Write HDR infoframe and send to panel Uma Shankar
2019-04-02 20:20 ` [v7 6/9] drm/i915: Add HLG EOTF Uma Shankar
2019-04-02 20:20 ` [v7 7/9] drm/i915: Enable infoframes on GLK+ for HDR Uma Shankar
2019-04-02 20:20 ` [v7 8/9] drm/i915:Enabled Modeset when HDR Infoframe changes Uma Shankar
2019-04-02 20:20 ` [v7 9/9] drm/i915: Set Infoframe for non modeset case for HDR Uma Shankar
2019-04-02 21:15 ` ✗ Fi.CI.BAT: failure for Add HDR Metadata Parsing and handling in DRM layer (rev7) Patchwork
2019-04-08  9:31 ` 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=177f83d1-de86-e357-1a28-e90b873df70f@intel.com \
    --to=shashank.sharma@intel.com \
    --cc=dcastagna@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@intel.com \
    --cc=seanpaul@chromium.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.