intel-gfx.lists.freedesktop.org archive mirror
 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
Subject: Re: [PATCH v2 3/3] drm/i915/bios: abstract child device expected size
Date: Thu, 29 Feb 2024 14:20:58 +0200	[thread overview]
Message-ID: <ZeB2quRtvZ-eQTWN@intel.com> (raw)
In-Reply-To: <20240226175854.287871-3-jani.nikula@intel.com>

On Mon, Feb 26, 2024 at 07:58:54PM +0200, Jani Nikula wrote:
> Add a function to return the expected child device size. Flip the if
> ladder around and use the same versions as in documentation to make it
> easier to verify. Return an error for unknown versions. No functional
> changes.
> 
> v2: Move BUILD_BUG_ON() next to the expected sizes
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_bios.c | 40 ++++++++++++++---------
>  1 file changed, 24 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
> index c0f41bd1f946..343726de9aa7 100644
> --- a/drivers/gpu/drm/i915/display/intel_bios.c
> +++ b/drivers/gpu/drm/i915/display/intel_bios.c
> @@ -2699,27 +2699,35 @@ static void parse_ddi_ports(struct drm_i915_private *i915)
>  		print_ddi_port(devdata);
>  }
>  
> +static int child_device_expected_size(u16 version)
> +{
> +	BUILD_BUG_ON(sizeof(struct child_device_config) < 40);

Should we make that !=40 perhaps?

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

> +
> +	if (version > 256)
> +		return -ENOENT;
> +	else if (version >= 256)
> +		return 40;
> +	else if (version >= 216)
> +		return 39;
> +	else if (version >= 196)
> +		return 38;
> +	else if (version >= 195)
> +		return 37;
> +	else if (version >= 111)
> +		return LEGACY_CHILD_DEVICE_CONFIG_SIZE;
> +	else if (version >= 106)
> +		return 27;
> +	else
> +		return 22;
> +}
> +
>  static bool child_device_size_valid(struct drm_i915_private *i915, int size)
>  {
>  	int expected_size;
>  
> -	if (i915->display.vbt.version < 106) {
> -		expected_size = 22;
> -	} else if (i915->display.vbt.version < 111) {
> -		expected_size = 27;
> -	} else if (i915->display.vbt.version < 195) {
> -		expected_size = LEGACY_CHILD_DEVICE_CONFIG_SIZE;
> -	} else if (i915->display.vbt.version == 195) {
> -		expected_size = 37;
> -	} else if (i915->display.vbt.version <= 215) {
> -		expected_size = 38;
> -	} else if (i915->display.vbt.version <= 255) {
> -		expected_size = 39;
> -	} else if (i915->display.vbt.version <= 256) {
> -		expected_size = 40;
> -	} else {
> +	expected_size = child_device_expected_size(i915->display.vbt.version);
> +	if (expected_size < 0) {
>  		expected_size = sizeof(struct child_device_config);
> -		BUILD_BUG_ON(sizeof(struct child_device_config) < 40);
>  		drm_dbg(&i915->drm,
>  			"Expected child device config size for VBT version %u not known; assuming %d\n",
>  			i915->display.vbt.version, expected_size);
> -- 
> 2.39.2

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-02-29 12:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 17:58 [PATCH v2 1/3] drm/i915/bios: bump expected child device size Jani Nikula
2024-02-26 17:58 ` [PATCH v2 2/3] drm/i915/bios: abstract child device size check Jani Nikula
2024-02-26 17:58 ` [PATCH v2 3/3] drm/i915/bios: abstract child device expected size Jani Nikula
2024-02-29 12:20   ` Ville Syrjälä [this message]
2024-02-29 14:08     ` Jani Nikula
2024-03-05  4:26   ` Chauhan, Shekhar
2024-03-05 11:13     ` Jani Nikula
2024-03-06  2:29       ` Chauhan, Shekhar
2024-02-26 23:17 ` ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/3] drm/i915/bios: bump expected child device size Patchwork
2024-02-26 23:30 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-27  8:11 ` ✓ 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=ZeB2quRtvZ-eQTWN@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).