aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/drm/drm_edid.h
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2017-01-11 14:57:24 +0200
committerVille Syrjälä <ville.syrjala@linux.intel.com>2017-01-26 18:37:13 +0200
commit779c4c2866150c1e5518d703b747f794f91f044c (patch)
tree95f70bfa6e8b22f4972134e19aa7ba5065fb1b81 /include/drm/drm_edid.h
parentdrm/edid: Introduce drm_hdmi_avi_infoframe_quant_range() (diff)
downloadwireguard-linux-779c4c2866150c1e5518d703b747f794f91f044c.tar.xz
wireguard-linux-779c4c2866150c1e5518d703b747f794f91f044c.zip
drm/edid: Set AVI infoframe Q even when QS=0
HDMI 2.0 recommends that we set the Q bits in the AVI infoframe even when the sink does not support quantization range selection (QS=0). According to CEA-861 we can do that as long as the Q we send matches the default quantization range for the mode. Previously I think I had misread the spec as saying that you can't send a non-zero Q at all when QS=0. But that's not what the spec actually says. v2: Fix typo in commit message (Jani) Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/20170111125725.8086-5-ville.syrjala@linux.intel.com Reviewed-by: Jani Nikula <jani.nikula@intel.com> Acked-by: Eric Anholt <eric@anholt.net>
Diffstat (limited to 'include/drm/drm_edid.h')
-rw-r--r--include/drm/drm_edid.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h
index cfad4d89589f..43fb0ac5eb9c 100644
--- a/include/drm/drm_edid.h
+++ b/include/drm/drm_edid.h
@@ -347,6 +347,7 @@ drm_hdmi_vendor_infoframe_from_display_mode(struct hdmi_vendor_infoframe *frame,
const struct drm_display_mode *mode);
void
drm_hdmi_avi_infoframe_quant_range(struct hdmi_avi_infoframe *frame,
+ const struct drm_display_mode *mode,
enum hdmi_quantization_range rgb_quant_range,
bool rgb_quant_range_selectable);