Re: The state of Quantization Range handling

2022-11-15 Thread Yussuf Khalil
Hello Sebastian, I've previously done some work on this topic [1]. My efforts were mostly about fixing the situation regarding overrides and providing proper means for userspace. I am affected by the issue myself as I own several DELL U2414H screens that declare a CE mode as their preferred

Re: [PATCH 1/5] drm/modes: Indicate CEA-861 CE modes to user-space

2020-04-16 Thread Yussuf Khalil
On Tue, 2020-04-14 at 14:41 +0200, Daniel Vetter wrote: > On Mon, Apr 13, 2020 at 11:40:22PM +0200, Yussuf Khalil wrote: > > Add a new flag to mark modes that are considered a CE mode > > according to the > > CEA-861 specification. Modes without this flag are impl

Re: [PATCH 5/5] drm/i915: Replace "Broadcast RGB" with "RGB quantization range" property

2020-04-16 Thread Yussuf Khalil
On Wed, 2020-04-15 at 13:13 +0200, Daniel Vetter wrote: > On Wed, Apr 15, 2020 at 10:33:25AM +0300, Jani Nikula wrote: > > On Tue, 14 Apr 2020, Yussuf Khalil wrote: > > > On Tue, 2020-04-14 at 14:34 +0200, Daniel Vetter wrote: > > > > On Tue, Apr 14, 2020 at 02:21

Re: [PATCH 5/5] drm/i915: Replace "Broadcast RGB" with "RGB quantization range" property

2020-04-14 Thread Yussuf Khalil
On Tue, 2020-04-14 at 14:34 +0200, Daniel Vetter wrote: > On Tue, Apr 14, 2020 at 02:21:06PM +0300, Jani Nikula wrote: > > On Tue, 14 Apr 2020, Jani Nikula > > wrote: > > > On Mon, 13 Apr 2020, Simon Ser wrote: > > > > On Monday, April 13, 2020 11:40 PM, Yus

[PATCH 4/5] drm/atomic-helper: Consider RGB quantization changes to be mode changes

2020-04-13 Thread Yussuf Khalil
Ensure RGB quantization range changes are applied immediately. Signed-off-by: Yussuf Khalil --- drivers/gpu/drm/drm_atomic_helper.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/gpu/drm/drm_atomic_helper.c b/drivers/gpu/drm/drm_atomic_helper.c index 85d163f16801

[PATCH 1/5] drm/modes: Indicate CEA-861 CE modes to user-space

2020-04-13 Thread Yussuf Khalil
). There is no use for this flag inside the kernel, so we set it only when communicating a mode to user-space. Signed-off-by: Yussuf Khalil --- drivers/gpu/drm/drm_modes.c | 14 ++ include/uapi/drm/drm_mode.h | 2 ++ 2 files changed, 16 insertions(+) diff --git a/drivers/gpu/drm/drm_modes.c b

[PATCH 3/5] drm: Add drm_connector_state_select_rgb_quantization_range() helper

2020-04-13 Thread Yussuf Khalil
This helper can be used to determine the appropriate RGB quantization range based on a connector's "RGB quantization range" property and a mode. Signed-off-by: Yussuf Khalil --- drivers/gpu/drm/drm_connector.c | 31 +++ include/drm/drm_connector.h |

[PATCH 2/5] drm: Add "RGB quantization range" connector property

2020-04-13 Thread Yussuf Khalil
Add a new "RGB quantization range" property with three possible values: Automatic, Limited, and Full. User-space may use this property to override the automatic selection of the RGB range as specified by CTA-861. Drivers should attach this property to all CTA-861 sinks. Signed-off-

[PATCH 5/5] drm/i915: Replace "Broadcast RGB" with "RGB quantization range" property

2020-04-13 Thread Yussuf Khalil
DRM now has a globally available "RGB quantization range" connector property. i915's "Broadcast RGB" that fulfils the same purpose is now considered deprecated, so drop it in favor of the DRM property. Signed-off-by: Yussuf Khalil --- drivers/gpu/drm/i915/display/i

[PATCH 0/5] Improving the situation regarding RGB quantization ranges

2020-04-13 Thread Yussuf Khalil
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 onl