![]() ![]() This comes with the added benefit of future-proofing metadata What the display supports it doesn't make sense for DRM to blockĪn HDR_OUTPUT_METADATA if it contains an EOTF the kernel doesn't Since it is expected that userspace reads the EDID to understand The kernel doesn't know about a new EOTF this check willįail, even if the EDID advertises support. When an HDR_OUTPUT_METADATA is set it then checks to While doing so it alsoįilters the EOTFs to the EOTFs the kernel knows about. In drm_parse_hdr_metadata_block the kernel reads the supportedĮOTFs from the EDID and stores them in theĭrm_connector->hdr_sink_metadata. Userspace is expected to read the EDID and set an appropriate The EDID of an HDR display defines EOTFs that are supportedīy the display and can be set in the HDR metadata infoframe. ` (15 subsequent siblings) 16 siblings, 0 replies 46+ messages in threadĬc: Sebastian Wick, Pekka Paalanen, Pekka Paalanen, Uma Shankar, 18:21 ` drm/connector: print max_requested_bpc in state debugfs Harry Wentland 18:21 Enable Colorspace connector property in amdgpu Harry 18:21 ` Harry Wentland * drm/display: Don't block HDR_OUTPUT_METADATA on unknown EOTF.gpu/drm/i915/display/intel_connector.c | 4 +-ĩ files changed, 261 insertions(+), 138 deletions(-) Refrain from merging this until we can confirm the DP/HDMI analyzerĭrm/display: Don't block HDR_OUTPUT_METADATA on unknown EOTFĭrm/connector: print max_requested_bpc in state debugfsĭrm/connector: Convert DRM_MODE_COLORIMETRY to enumĭrm/connector: Pull out common create_colorspace_property codeĭrm/connector: Allow drivers to pass list of supported colorspacesĭrm/connector: Print connector colorspace in state debugfsĭrm/amd/display: Always pass connector_state to stream validationĭrm/amd/display: Register Colorspace property for DP and HDMIĭrm/amd/display: Set colorspace for HDMI infoframeĭrm/amd/display: Send correct DP colorspace infopacketĭrm/amd/display: Add support for explicit BT601_YCCĭrm/amd/display: Add debugfs for testing output colorspaceĭrm/amd/display: Add default case for output_color_space switchĭrm/amd/display: Don't restrict bpc to 8 bpcĭrm/amd/display: Always set crtcinfo from create_stream_for_sink Since I don't have a DP and HDMI analyzer I could not test thisĮnd-to-end but someone will test it in the coming days. The relevant patchset can be found on the IGT Since the Colorspace property didn't have an IGT test I added ![]() The rest of the patches deal with the Colorspace enablement ![]() The following patches rework the connector colorspace code toġ) allow for easy printing of the colorspace in the drm_atomicĢ) allow drivers to specify the supported colorspaces on a The second one prints a connector's max_bpc as part of the atomic Theįirst patch allows for HDR_OUTPUT_METADATA with EOTFs that are The first two patches are not completely related to the rest. This patchset enables the DP and HDMI infoframe properties ` (16 more replies) 0 siblings, 17 replies 46+ messages in threadįrom: Harry Wentland 18:21 UTC ( / raw)Ĭc: Sebastian Wick, Pekka Paalanen, Uma Shankar, Vitaly.Prosyak, 18:21 ` drm/display: Don't block HDR_OUTPUT_METADATA on unknown EOTF Harry Wentland Enable Colorspace connector property in amdgpu archive mirror help / color / mirror / Atom feed * Enable Colorspace connector property in amdgpu 18:21 Harry Wentland
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |