Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 2/3] drm/i915/bios: Add function to check if edp data override is needed
Date: Mon, 28 Jul 2025 15:57:56 +0300	[thread overview]
Message-ID: <0601423daeaa9bcdf1b5ceb2c2d92cc92c189551@intel.com> (raw)
In-Reply-To: <20250725061548.2704697-3-suraj.kandpal@intel.com>

On Fri, 25 Jul 2025, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Add a function that helps identify if the rate provided needs to
> be overridden. For this we need a function that compares the rate
> provided and bitmask of rates provided in VBT.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_bios.c | 58 +++++++++++++++++++++++
>  drivers/gpu/drm/i915/display/intel_bios.h |  2 +
>  2 files changed, 60 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
> index 8337ebe0f2c8..3eac804b2449 100644
> --- a/drivers/gpu/drm/i915/display/intel_bios.c
> +++ b/drivers/gpu/drm/i915/display/intel_bios.c
> @@ -2480,6 +2480,54 @@ static int parse_bdb_216_dp_max_link_rate(const int vbt_max_link_rate)
>  	}
>  }
>  
> +static bool parse_bdb_263_edp_data_override(const u32 edp_data_override_mask, int rate)

We don't really use const like this anywhere.

> +{
> +	u32 val;
> +
> +	switch (rate) {
> +	case 2000000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_20;
> +		break;
> +	case 1350000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_13_5;
> +		break;
> +	case 1000000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_10;
> +		break;
> +	case 810000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_8_1;
> +		break;
> +	case 675000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_6_75;
> +		break;
> +	case 540000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_5_4;
> +		break;
> +	case 432000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_4_32;
> +		break;
> +	case 324000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_3_24;
> +		break;
> +	case 270000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_2_7;
> +		break;
> +	case 243000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_2_43;
> +		break;
> +	case 216000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_2_16;
> +		break;
> +	case 162000:
> +		val = BDB_263_VBT_EDP_LINK_RATE_1_62;
> +		break;
> +	default:
> +		break;
> +	}
> +
> +	return edp_data_override_mask & val;

I think you're better off having a helper function that returns the mask
for a rate, possibly 0, that you don't pass edp_data_override_mask at
all.

> +}
> +
>  int intel_bios_dp_max_link_rate(const struct intel_bios_encoder_data *devdata)
>  {
>  	if (!devdata || devdata->display->vbt.version < 216)
> @@ -2499,6 +2547,16 @@ int intel_bios_dp_max_lane_count(const struct intel_bios_encoder_data *devdata)
>  	return devdata->child.dp_max_lane_count + 1;
>  }
>  
> +bool
> +intel_bios_need_edp_data_override(const struct intel_bios_encoder_data *devdata,
> +				  int rate)

intel_bios_encoder_supports_edp_rate() or something, "need edp data
override" doesn't mean anything.

> +{
> +	if (!devdata || devdata->display->vbt.version < 263)
> +		return false;
> +
> +	return parse_bdb_263_edp_data_override(devdata->child.edp_data_override, rate);

This would become:

	return devdata->child.edp_data_override & edp_rate_override_mask(rate);

except negated with the positive function naming.

Also child.edp_data_override is a misleading name, because it's about
data *rate* override, not some random data override.

> +}
> +
>  static void sanitize_device_type(struct intel_bios_encoder_data *devdata,
>  				 enum port port)
>  {
> diff --git a/drivers/gpu/drm/i915/display/intel_bios.h b/drivers/gpu/drm/i915/display/intel_bios.h
> index 6cd7a011b8c4..aeba0e9b5228 100644
> --- a/drivers/gpu/drm/i915/display/intel_bios.h
> +++ b/drivers/gpu/drm/i915/display/intel_bios.h
> @@ -274,5 +274,7 @@ void intel_bios_for_each_encoder(struct intel_display *display,
>  					      const struct intel_bios_encoder_data *devdata));
>  
>  void intel_bios_debugfs_register(struct intel_display *display);
> +bool
> +intel_bios_need_edp_data_override(const struct intel_bios_encoder_data *devdata, int rate);

Place this next to the other intel_bios_encoder_supports_* declarations.

BR,
Jani.

>  
>  #endif /* _INTEL_BIOS_H_ */

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-07-28 12:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  6:15 [PATCH 0/3] eDP Data Override Suraj Kandpal
2025-07-25  6:15 ` [PATCH 1/3] drm/i915/vbt: Add eDP Data Overrride field in VBT Suraj Kandpal
2025-07-28 12:45   ` Jani Nikula
2025-07-29  4:16     ` Kandpal, Suraj
2025-07-25  6:15 ` [PATCH 2/3] drm/i915/bios: Add function to check if edp data override is needed Suraj Kandpal
2025-07-26 11:20   ` kernel test robot
2025-07-28 12:57   ` Jani Nikula [this message]
2025-07-29  4:22     ` Kandpal, Suraj
2025-07-25  6:15 ` [PATCH 3/3] drm/i915/edp: eDP Data Overrride Suraj Kandpal
2025-07-28 13:00   ` Jani Nikula
2025-07-29  4:59     ` Kandpal, Suraj
2025-07-25  6:22 ` ✓ CI.KUnit: success for eDP Data Override (rev3) Patchwork
2025-07-25  6:36 ` ✗ CI.checksparse: warning " Patchwork
2025-07-25  8:36 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-28 12:35 ` [PATCH 0/3] eDP Data Override Jani Nikula

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=0601423daeaa9bcdf1b5ceb2c2d92cc92c189551@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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