Improving the situation regarding RGB quantization ranges
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 13 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | drm/modes: Indicate CEA-861 CE modes to user-spacedrivers/ include/ | +16 | 3 replies | |
| 2/5 | drm: Add "RGB quantization range" connector propertydrivers/ drivers/ include/ +1 more | +69 | 1 reply | |
| 3/5 | drm: Add drm_connector_state_select_rgb_quantization_range() helperdrivers/ include/ | +35 | 0 replies | |
| 4/5 | drm/atomic-helper: Consider RGB quantization changes to be mode changesdrivers/ | +6 | 0 replies | |
| 5/5 | drm/i915: Replace "Broadcast RGB" with "RGB quantization range" propertydrivers/ drivers/ drivers/ +6 more | +34 | 9 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Improving the situation regarding RGB quantization ranges
The CTA-861 specification differentiates between IT and CE modes. For the latter, it requires sources to send "limited RGB quantization range", i.e., allowed RGB values are constrained to 16 - 235 (in the 8 bit case). A sink may indicate support for full range RGB (0 - 255) in CE modes through its EDID, allowing the source to override the recommendations set by CTA-861.
For computer screens it is usually desirable to have full range RGB output. In reality, though, many displays set a CE mode as preferred in their EDID and leave the "Quantization Range Selectable" bit unset despite having no issues with full range output. Therefore, it makes sense to provide the user with a method of overriding the standards-compliant selection.
The current situation in DRM regarding the RGB quantization range is somewhat messy. We have drivers that
- behave standards-compliant and provide a custom override property (e.g., i915, gma500)
- behave standards-compliant and provide no override (e.g., vc4)
- behave standards-compliant and select full range for CE modes if the screen indicates support (e.g., tda998x)
- probably don't care at all
This series is an effort to fix the situation. It introduces a property for overriding the RGB quantization range that is defined in the DRM core and can be attached to connectors by all drivers, providing a driver-independent way of overriding the defaults to userspace. So far, I've wired up the new property in i915 only.
Yussuf Khalil (5):
drm/modes: Indicate CEA-861 CE modes to user-space
drm: Add "RGB quantization range" connector property
drm: Add drm_connector_state_select_rgb_quantization_range() helper drm/atomic-helper: Consider RGB quantization changes to be mode
changes
drm/i915: Replace "Broadcast RGB" with "RGB quantization range"
property
drivers/gpu/drm/drm_atomic_helper.c | 6 ++ drivers/gpu/drm/drm_atomic_uapi.c | 4 ++ drivers/gpu/drm/drm_connector.c | 66 +++++++++++++++++++ drivers/gpu/drm/drm_modes.c | 14 ++++ drivers/gpu/drm/i915/display/intel_atomic.c | 8 --- .../gpu/drm/i915/display/intel_connector.c | 39 ++++------- .../gpu/drm/i915/display/intel_connector.h | 2 +- .../drm/i915/display/intel_display_types.h | 8 --- drivers/gpu/drm/i915/display/intel_dp.c | 24 ++----- drivers/gpu/drm/i915/display/intel_dp_mst.c | 2 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 19 ++---- drivers/gpu/drm/i915/display/intel_sdvo.c | 18 ++--- drivers/gpu/drm/i915/i915_drv.h | 1 - include/drm/drm_connector.h | 27 ++++++++ include/drm/drm_mode_config.h | 7 ++ include/uapi/drm/drm_mode.h | 2 + 16 files changed, 160 insertions(+), 87 deletions(-)
Signature · 6 lines
2.26.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel