diff options
| author | Maxime Ripard <maxime@cerno.tech> | 2022-01-20 16:16:10 +0100 |
|---|---|---|
| committer | Maxime Ripard <maxime@cerno.tech> | 2022-01-25 10:00:13 +0100 |
| commit | 4a46e5d251a39e7c10493743ac89a31f6f3ce5b5 (patch) | |
| tree | cf042eab43b5fae0d2a0e15dd1ad93da71279736 /include/drm | |
| parent | 4fd5e720b709b87f67809a871fde9fb6cb910f28 (diff) | |
| download | linux-stable-4a46e5d251a39e7c10493743ac89a31f6f3ce5b5.tar.gz linux-stable-4a46e5d251a39e7c10493743ac89a31f6f3ce5b5.tar.bz2 linux-stable-4a46e5d251a39e7c10493743ac89a31f6f3ce5b5.zip | |
drm/edid: Rename drm_hdmi_avi_infoframe_colorspace to _colorimetry
The drm_hdmi_avi_infoframe_colorspace() function actually sets the
colorimetry and extended_colorimetry fields in the hdmi_avi_infoframe
structure with DRM_MODE_COLORIMETRY_* values.
To make things worse, the hdmi_avi_infoframe structure also has a
colorspace field used to signal whether an RGB or YUV output is being
used.
Let's remove the inconsistency and allow for the colorspace usage by
renaming the function.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Link: https://patchwork.freedesktop.org/patch/msgid/20220120151625.594595-2-maxime@cerno.tech
Diffstat (limited to 'include/drm')
| -rw-r--r-- | include/drm/drm_edid.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h index 18f6c700f6d0..144c495b99c4 100644 --- a/include/drm/drm_edid.h +++ b/include/drm/drm_edid.h @@ -401,8 +401,8 @@ drm_hdmi_vendor_infoframe_from_display_mode(struct hdmi_vendor_infoframe *frame, const struct drm_display_mode *mode); void -drm_hdmi_avi_infoframe_colorspace(struct hdmi_avi_infoframe *frame, - const struct drm_connector_state *conn_state); +drm_hdmi_avi_infoframe_colorimetry(struct hdmi_avi_infoframe *frame, + const struct drm_connector_state *conn_state); void drm_hdmi_avi_infoframe_bars(struct hdmi_avi_infoframe *frame, |