From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Uma Shankar" <uma.shankar@intel.com>
Cc: dcastagna@chromium.org, jonas@kwiboo.se,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
seanpaul@chromium.org
Subject: Re: [v11 00/12] Add HDR Metadata Parsing and handling in DRM layer
Date: Tue, 28 May 2019 13:35:45 +0200 [thread overview]
Message-ID: <c83b4fc7-ea7e-66e6-9d7e-379eeec6d199@linux.intel.com> (raw)
In-Reply-To: <20190522204522.GC6464@intel.com>
Op 22-05-2019 om 22:45 schreef Ville Syrjälä:
> On Thu, May 16, 2019 at 07:40:05PM +0530, 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.
>>
>> 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.
>>
>> v8: Addressed Jonas Karlman review comments. Added Shashank's RB to the series,
>> fixed a WARN_ON on BYT/CHT.
>>
>> v9: Addressed Ville and Jonas Karlman's review comments. Added the infoframe
>> state readout and metadata reference count.
>>
>> v10: Addressed review comments from Jonas and Ville. Dropped one patch related
>> to i915 fastset handling as per Ville's feedback.
>>
>> v11: Addressed Ville's review comments.
>>
>> Note: v9 version is already tested with Kodi and a confirmation from team kodi has been
>> received. Branch details for the same as below:
>> https://github.com/xbmc/xbmc/tree/feature_drmprime-vaapi
>>
>> v9 of this series is:
>> Tested-by: Jonas Karlman <jonas@kwiboo.se>
>>
>> Jonas Karlman (1):
>> drm: Add reference counting on HDR metadata blob
>>
>> Uma Shankar (9):
>> 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: Added DRM Infoframe handling for BYT/CHT
>> video/hdmi: Add Unpack function for DRM infoframe
>> drm/i915: Add state readout for DRM infoframe
>>
>> Ville Syrjälä (2):
>> drm: Add HLG EOTF
>> drm/i915: Enable infoframes on GLK+ for HDR
> Pushed the core/etc. bits to drm-misc-next so that other drivers
> can base their work on that. We'll need a backmerge to get the
> i915 stuff in via dinq.
>
Rest pushed as well. I reordered the series to be slightly more logical, from hw enabling bits to sw enabling bits. :)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-28 11:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 14:10 [v11 00/12] Add HDR Metadata Parsing and handling in DRM layer Uma Shankar
2019-05-16 14:10 ` [v11 01/12] drm: Add HDR source metadata property Uma Shankar
2019-05-16 14:10 ` [v11 02/12] drm: Add reference counting on HDR metadata blob Uma Shankar
2019-05-16 14:10 ` [v11 03/12] drm: Parse HDR metadata info from EDID Uma Shankar
2019-05-16 14:10 ` [v11 04/12] drm: Enable HDR infoframe support Uma Shankar
2019-05-16 14:10 ` [v11 05/12] drm/i915: Attach HDR metadata property to connector Uma Shankar
2019-05-17 14:06 ` Ville Syrjälä
2019-05-16 14:10 ` [v11 06/12] drm/i915: Write HDR infoframe and send to panel Uma Shankar
2019-05-17 14:06 ` Ville Syrjälä
2019-05-16 14:10 ` [v11 07/12] drm: Add HLG EOTF Uma Shankar
2019-05-16 14:10 ` [v11 08/12] drm/i915: Enable infoframes on GLK+ for HDR Uma Shankar
2019-05-17 14:01 ` Ville Syrjälä
2019-05-16 14:10 ` [v11 09/12] drm/i915:Enabled Modeset when HDR Infoframe changes Uma Shankar
2019-05-16 14:10 ` [v11 10/12] drm/i915: Added DRM Infoframe handling for BYT/CHT Uma Shankar
2019-05-16 14:10 ` [v11 11/12] video/hdmi: Add Unpack function for DRM infoframe Uma Shankar
2019-05-16 14:10 ` [v11 12/12] drm/i915: Add state readout " Uma Shankar
2019-05-22 20:45 ` [v11 00/12] Add HDR Metadata Parsing and handling in DRM layer Ville Syrjälä
2019-05-23 8:09 ` Jani Nikula
2019-05-23 8:41 ` [Intel-gfx] " Daniel Vetter
2019-05-28 11:35 ` Maarten Lankhorst [this message]
2019-05-28 11:43 ` Shankar, Uma
2019-05-29 9:43 ` Daniel Vetter
2019-05-29 13:58 ` Shankar, Uma
2019-05-29 15:03 ` [Intel-gfx] " Daniel Vetter
2019-05-29 17:28 ` Shankar, Uma
2019-05-29 17:35 ` Daniel Vetter
2019-05-29 17:39 ` [Intel-gfx] " 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=c83b4fc7-ea7e-66e6-9d7e-379eeec6d199@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dcastagna@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonas@kwiboo.se \
--cc=seanpaul@chromium.org \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).