dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Dom Cobley <dom@raspberrypi.com>,
	Tim Gover <tim.gover@raspberrypi.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Werner Sembach <wse@tuxedocomputers.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Phil Elwell <phil@raspberrypi.com>
Subject: Re: [PATCH v2 02/14] drm/edid: Rename drm_hdmi_avi_infoframe_colorspace to _colorimetry
Date: Wed, 15 Dec 2021 15:50:29 +0200	[thread overview]
Message-ID: <YbnypVBnehElJTVI@intel.com> (raw)
In-Reply-To: <20211215124406.340180-3-maxime@cerno.tech>

On Wed, Dec 15, 2021 at 01:43:54PM +0100, Maxime Ripard wrote:
> 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.
> 
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Sadly we can't rename the property itself.

> ---
>  drivers/gpu/drm/drm_edid.c                  | 8 ++++----
>  drivers/gpu/drm/i915/display/intel_hdmi.c   | 2 +-
>  drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
>  drivers/gpu/drm/vc4/vc4_hdmi.c              | 2 +-
>  include/drm/drm_edid.h                      | 4 ++--
>  5 files changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index e57d1b8cdaaa..dec7aecfc655 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -5890,13 +5890,13 @@ static const u32 hdmi_colorimetry_val[] = {
>  #undef ACE
>  
>  /**
> - * drm_hdmi_avi_infoframe_colorspace() - fill the HDMI AVI infoframe
> - *                                       colorspace information
> + * drm_hdmi_avi_infoframe_colorimetry() - fill the HDMI AVI infoframe
> + *                                       colorimetry information
>   * @frame: HDMI AVI infoframe
>   * @conn_state: connector state
>   */
>  void
> -drm_hdmi_avi_infoframe_colorspace(struct hdmi_avi_infoframe *frame,
> +drm_hdmi_avi_infoframe_colorimetry(struct hdmi_avi_infoframe *frame,
>  				  const struct drm_connector_state *conn_state)
>  {
>  	u32 colorimetry_val;
> @@ -5915,7 +5915,7 @@ drm_hdmi_avi_infoframe_colorspace(struct hdmi_avi_infoframe *frame,
>  	frame->extended_colorimetry = (colorimetry_val >> 2) &
>  					EXTENDED_COLORIMETRY_MASK;
>  }
> -EXPORT_SYMBOL(drm_hdmi_avi_infoframe_colorspace);
> +EXPORT_SYMBOL(drm_hdmi_avi_infoframe_colorimetry);
>  
>  /**
>   * drm_hdmi_avi_infoframe_quant_range() - fill the HDMI AVI infoframe
> diff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c
> index 3b5b9e7b05b7..96e508ddc4af 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdmi.c
> @@ -730,7 +730,7 @@ intel_hdmi_compute_avi_infoframe(struct intel_encoder *encoder,
>  	else
>  		frame->colorspace = HDMI_COLORSPACE_RGB;
>  
> -	drm_hdmi_avi_infoframe_colorspace(frame, conn_state);
> +	drm_hdmi_avi_infoframe_colorimetry(frame, conn_state);
>  
>  	/* nonsense combination */
>  	drm_WARN_ON(encoder->base.dev, crtc_state->limited_color_range &&
> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
> index 05d2d750fa53..092a925c6cf5 100644
> --- a/drivers/gpu/drm/i915/display/intel_lspcon.c
> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
> @@ -537,7 +537,7 @@ void lspcon_set_infoframes(struct intel_encoder *encoder,
>  		frame.avi.colorspace = HDMI_COLORSPACE_RGB;
>  
>  	/* Set the Colorspace as per the HDMI spec */
> -	drm_hdmi_avi_infoframe_colorspace(&frame.avi, conn_state);
> +	drm_hdmi_avi_infoframe_colorimetry(&frame.avi, conn_state);
>  
>  	/* nonsense combination */
>  	drm_WARN_ON(encoder->base.dev, crtc_state->limited_color_range &&
> diff --git a/drivers/gpu/drm/vc4/vc4_hdmi.c b/drivers/gpu/drm/vc4/vc4_hdmi.c
> index 053fbaf765ca..be39e55ae113 100644
> --- a/drivers/gpu/drm/vc4/vc4_hdmi.c
> +++ b/drivers/gpu/drm/vc4/vc4_hdmi.c
> @@ -502,7 +502,7 @@ static void vc4_hdmi_set_avi_infoframe(struct drm_encoder *encoder)
>  					   vc4_encoder->limited_rgb_range ?
>  					   HDMI_QUANTIZATION_RANGE_LIMITED :
>  					   HDMI_QUANTIZATION_RANGE_FULL);
> -	drm_hdmi_avi_infoframe_colorspace(&frame.avi, cstate);
> +	drm_hdmi_avi_infoframe_colorimetry(&frame.avi, cstate);
>  	drm_hdmi_avi_infoframe_bars(&frame.avi, cstate);
>  
>  	vc4_hdmi_write_infoframe(encoder, &frame);
> 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,
> -- 
> 2.33.1

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2021-12-15 13:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 12:43 [PATCH v2 00/14] drm/vc4: hdmi: Yet Another Approach to HDMI YUV output Maxime Ripard
2021-12-15 12:43 ` [PATCH v2 01/14] drm/edid: Don't clear YUV422 if using deep color Maxime Ripard
2021-12-15 13:48   ` Ville Syrjälä
2022-01-11 15:55     ` Maxime Ripard
2022-01-12 13:22       ` Ville Syrjälä
2021-12-15 12:43 ` [PATCH v2 02/14] drm/edid: Rename drm_hdmi_avi_infoframe_colorspace to _colorimetry Maxime Ripard
2021-12-15 13:50   ` Ville Syrjälä [this message]
2021-12-15 12:43 ` [PATCH v2 03/14] drm/vc4: hdmi: Add full range RGB helper Maxime Ripard
2021-12-15 12:43 ` [PATCH v2 04/14] drm/vc4: hdmi: Use full range helper in csc functions Maxime Ripard
2021-12-15 12:43 ` [PATCH v2 05/14] drm/vc4: hdmi: Move XBAR setup to csc_setup Maxime Ripard
2021-12-15 12:43 ` [PATCH v2 06/14] drm/vc4: hdmi: Replace CSC_CTL hardcoded value by defines Maxime Ripard
2021-12-15 12:43 ` [PATCH v2 07/14] drm/vc4: hdmi: Define colorspace matrices Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 08/14] drm/vc4: hdmi: Change CSC callback prototype Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 09/14] drm/vc4: hdmi: Move clock validation to its own function Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 10/14] drm/vc4: hdmi: Move clock calculation into " Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 11/14] drm/vc4: hdmi: Take the sink maximum TMDS clock into account Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 12/14] drm/vc4: hdmi: Take bpp into account for the scrambler Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 13/14] drm/vc4: hdmi: Always try to have the highest bpc Maxime Ripard
2021-12-15 12:44 ` [PATCH v2 14/14] drm/vc4: hdmi: Support HDMI YUV output Maxime Ripard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YbnypVBnehElJTVI@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dom@raspberrypi.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maxime@cerno.tech \
    --cc=phil@raspberrypi.com \
    --cc=tim.gover@raspberrypi.com \
    --cc=tzimmermann@suse.de \
    --cc=wse@tuxedocomputers.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox