All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/hdmi: Prune modes that require HDMI2.1 FRL
Date: Fri, 8 Jul 2022 04:00:56 +0000	[thread overview]
Message-ID: <DM6PR11MB317775DC2D990594E3297055BA829@DM6PR11MB3177.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220707052712.2033748-1-ankit.k.nautiyal@intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ankit
> Nautiyal
> Sent: Thursday, July 7, 2022 10:57 AM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH] drm/i915/hdmi: Prune modes that require
> HDMI2.1 FRL
> 
> HDMI2.1 requires some higher resolution video modes to be enumerated
> only if HDMI2.1 Fixed Rate Link (FRL) is supported.
> Current platforms do not support FRL transmission so prune modes that
> require HDMI2.1 FRL.
>
If the hardware doesn't support FRL then it basically blocks HDMI2.1 feature.
Then it wont be possible to use any resolution above 4k60 is it?

> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_hdmi.c | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c
> b/drivers/gpu/drm/i915/display/intel_hdmi.c
> index ebd91aa69dd2..93c00b61795f 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdmi.c
> @@ -1974,6 +1974,20 @@ intel_hdmi_mode_clock_valid(struct
> drm_connector *connector, int clock,
>  	return status;
>  }
> 
> +/*
> + * HDMI2.1 requires higher resolution modes like 8k60, 4K120 to be
> + * enumerated only if FRL is supported. Platforms not supporting FRL
> + * must prune these modes.
> + */
> +static bool
> +hdmi21_frl_quirk(int dotclock, bool frl_supported) {
> +	if (dotclock >= 600000 && !frl_supported)
> +		return true;
> +
> +	return false;
> +}
> +
>  static enum drm_mode_status
>  intel_hdmi_mode_valid(struct drm_connector *connector,
>  		      struct drm_display_mode *mode)
> @@ -2001,6 +2015,13 @@ intel_hdmi_mode_valid(struct drm_connector
> *connector,
>  		clock *= 2;
>  	}
> 
> +	/*
> +	 * Current Platforms do not support HDMI2.1 FRL mode of
> transmission,
> +	 * so prune the modes that require FRL.
> +	 */
> +	if (hdmi21_frl_quirk(clock, false))
> +		return MODE_BAD;
> +
Instead of setting this frl_supported as false, can we get this info from hardware, so that when
our hardware supports it later it would be easy to enable this.

Thanks and Regards,
Arun R Murthy
-------------------

  parent reply	other threads:[~2022-07-08  4:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  5:27 [Intel-gfx] [PATCH] drm/i915/hdmi: Prune modes that require HDMI2.1 FRL Ankit Nautiyal
2022-07-07  6:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-07-07 14:15 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-08  4:00 ` Murthy, Arun R [this message]
2022-07-08 10:06   ` [Intel-gfx] [PATCH] " Nautiyal, Ankit K
2022-07-19  3:15     ` Murthy, Arun R
2022-07-19  6:10       ` Nautiyal, Ankit K
2022-07-19  7:02         ` Murthy, Arun R
2022-07-21  8:54           ` Nautiyal, Ankit K

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=DM6PR11MB317775DC2D990594E3297055BA829@DM6PR11MB3177.namprd11.prod.outlook.com \
    --to=arun.r.murthy@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.