All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 12/12] drm/edid: split drm_add_edid_modes() to two
Date: Mon, 28 Mar 2022 20:48:08 +0300	[thread overview]
Message-ID: <YkH02F/kGQSBQDi+@intel.com> (raw)
In-Reply-To: <437c3c79f68d1144444fb2dd18a678f3aa97272c.1648477901.git.jani.nikula@intel.com>

On Mon, Mar 28, 2022 at 05:34:33PM +0300, Jani Nikula wrote:
> Reduce the size of the function that actually modifies the EDID.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/drm_edid.c | 42 ++++++++++++++++++++++----------------
>  1 file changed, 24 insertions(+), 18 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index d1abaa517867..d79b06f7f34c 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -5561,18 +5561,8 @@ static int add_displayid_detailed_modes(struct drm_connector *connector,
>  	return num_modes;
>  }
>  
> -/**
> - * drm_add_edid_modes - add modes from EDID data, if available
> - * @connector: connector we're probing
> - * @edid: EDID data
> - *
> - * Add the specified modes to the connector's mode list. Also fills out the
> - * &drm_display_info structure and ELD in @connector with any information which
> - * can be derived from the edid.
> - *
> - * Return: The number of modes added or 0 if we couldn't find any.
> - */
> -int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
> +static int drm_edid_connector_update(struct drm_connector *connector,
> +				     const struct edid *edid)
>  {
>  	int num_modes = 0;
>  	u32 quirks;
> @@ -5581,12 +5571,6 @@ int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
>  		clear_eld(connector);
>  		return 0;
>  	}
> -	if (!drm_edid_is_valid(edid)) {
> -		clear_eld(connector);
> -		drm_warn(connector->dev, "%s: EDID invalid.\n",
> -			 connector->name);
> -		return 0;
> -	}
>  
>  	drm_edid_to_eld(connector, edid);
>  
> @@ -5638,6 +5622,28 @@ int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
>  
>  	return num_modes;
>  }
> +
> +/**
> + * drm_add_edid_modes - add modes from EDID data, if available
> + * @connector: connector we're probing
> + * @edid: EDID data
> + *
> + * Add the specified modes to the connector's mode list. Also fills out the
> + * &drm_display_info structure and ELD in @connector with any information which
> + * can be derived from the edid.
> + *
> + * Return: The number of modes added or 0 if we couldn't find any.
> + */
> +int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
> +{
> +	if (edid && !drm_edid_is_valid(edid)) {

drm_edid_is_valid() is very poorly named since it can mutate the EDID.
Also calling it here is kinda crazy instead of just validating when we
originally read the EDID. But those are things for to be fixed later.

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

> +		drm_warn(connector->dev, "%s: EDID invalid.\n",
> +			 connector->name);
> +		edid = NULL;
> +	}
> +
> +	return drm_edid_connector_update(connector, edid);
> +}
>  EXPORT_SYMBOL(drm_add_edid_modes);
>  
>  /**
> -- 
> 2.30.2

-- 
Ville Syrjälä
Intel

WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 12/12] drm/edid: split drm_add_edid_modes() to two
Date: Mon, 28 Mar 2022 20:48:08 +0300	[thread overview]
Message-ID: <YkH02F/kGQSBQDi+@intel.com> (raw)
In-Reply-To: <437c3c79f68d1144444fb2dd18a678f3aa97272c.1648477901.git.jani.nikula@intel.com>

On Mon, Mar 28, 2022 at 05:34:33PM +0300, Jani Nikula wrote:
> Reduce the size of the function that actually modifies the EDID.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/drm_edid.c | 42 ++++++++++++++++++++++----------------
>  1 file changed, 24 insertions(+), 18 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index d1abaa517867..d79b06f7f34c 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -5561,18 +5561,8 @@ static int add_displayid_detailed_modes(struct drm_connector *connector,
>  	return num_modes;
>  }
>  
> -/**
> - * drm_add_edid_modes - add modes from EDID data, if available
> - * @connector: connector we're probing
> - * @edid: EDID data
> - *
> - * Add the specified modes to the connector's mode list. Also fills out the
> - * &drm_display_info structure and ELD in @connector with any information which
> - * can be derived from the edid.
> - *
> - * Return: The number of modes added or 0 if we couldn't find any.
> - */
> -int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
> +static int drm_edid_connector_update(struct drm_connector *connector,
> +				     const struct edid *edid)
>  {
>  	int num_modes = 0;
>  	u32 quirks;
> @@ -5581,12 +5571,6 @@ int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
>  		clear_eld(connector);
>  		return 0;
>  	}
> -	if (!drm_edid_is_valid(edid)) {
> -		clear_eld(connector);
> -		drm_warn(connector->dev, "%s: EDID invalid.\n",
> -			 connector->name);
> -		return 0;
> -	}
>  
>  	drm_edid_to_eld(connector, edid);
>  
> @@ -5638,6 +5622,28 @@ int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
>  
>  	return num_modes;
>  }
> +
> +/**
> + * drm_add_edid_modes - add modes from EDID data, if available
> + * @connector: connector we're probing
> + * @edid: EDID data
> + *
> + * Add the specified modes to the connector's mode list. Also fills out the
> + * &drm_display_info structure and ELD in @connector with any information which
> + * can be derived from the edid.
> + *
> + * Return: The number of modes added or 0 if we couldn't find any.
> + */
> +int drm_add_edid_modes(struct drm_connector *connector, struct edid *edid)
> +{
> +	if (edid && !drm_edid_is_valid(edid)) {

drm_edid_is_valid() is very poorly named since it can mutate the EDID.
Also calling it here is kinda crazy instead of just validating when we
originally read the EDID. But those are things for to be fixed later.

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

> +		drm_warn(connector->dev, "%s: EDID invalid.\n",
> +			 connector->name);
> +		edid = NULL;
> +	}
> +
> +	return drm_edid_connector_update(connector, edid);
> +}
>  EXPORT_SYMBOL(drm_add_edid_modes);
>  
>  /**
> -- 
> 2.30.2

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-03-28 17:48 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 14:34 [Intel-gfx] [PATCH v3 00/12] drm/edid: constify EDID parsing, with fixes Jani Nikula
2022-03-28 14:34 ` Jani Nikula
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 01/12] drm/edid: don't modify EDID while parsing Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 02/12] drm/edid: fix reduced blanking support check Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:27   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:27     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 03/12] drm/edid: pass a timing pointer to is_display_descriptor() Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:28   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:28     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 04/12] drm/edid: pass a timing pointer to is_detailed_timing_descriptor() Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:29   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:29     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 05/12] drm/edid: use struct detailed_timing member access in is_rb() Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:29   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:29     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 06/12] drm/edid: use struct detailed_timing member access in gtf2 functions Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:34   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:34     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 07/12] drm/edid: constify struct detailed_timing in lower level parsing Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:35   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:35     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 08/12] drm/edid: constify struct detailed_timing in parsing callbacks Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:37   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:37     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 09/12] drm/edid: constify struct edid passed to detailed blocks Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:39   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:39     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 10/12] drm/edid: constify struct edid passed around in callbacks and closure Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:40   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:40     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 11/12] drm/edid: add more general struct edid constness in the interfaces Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:41   ` [Intel-gfx] " Ville Syrjälä
2022-03-28 17:41     ` Ville Syrjälä
2022-03-28 14:34 ` [Intel-gfx] [PATCH v3 12/12] drm/edid: split drm_add_edid_modes() to two Jani Nikula
2022-03-28 14:34   ` Jani Nikula
2022-03-28 17:48   ` Ville Syrjälä [this message]
2022-03-28 17:48     ` Ville Syrjälä
2022-03-28 18:35     ` [Intel-gfx] " Jani Nikula
2022-03-28 18:35       ` Jani Nikula
2022-03-28 18:00 ` [Intel-gfx] [PATCH v3 00/12] drm/edid: constify EDID parsing, with fixes Emil Velikov
2022-03-28 18:00   ` Emil Velikov
2022-03-28 18:36   ` [Intel-gfx] " Jani Nikula
2022-03-28 18:36     ` Jani Nikula
2022-03-29  1:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/edid: constify EDID parsing, with fixes (rev2) Patchwork
2022-03-29  1:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-29  1:34 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-29  1:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-29  4:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-29  9:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/edid: constify EDID parsing, with fixes (rev3) Patchwork
2022-03-29  9:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-29  9:27 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-29  9:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-29 12:55 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=YkH02F/kGQSBQDi+@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.