All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: William Tseng <william.tseng@intel.com>, dri-devel@lists.freedesktop.org
Cc: Wayne Lin <waynelin@amd.com>, Lee Shawn C <shawn.c.lee@intel.com>,
	William Tseng <william.tseng@intel.com>
Subject: Re: [PATCH] drm/edid: ignore the CEA modes not defined in CEA-861-D
Date: Tue, 31 May 2022 14:06:30 +0300	[thread overview]
Message-ID: <87r14aq7ux.fsf@intel.com> (raw)
In-Reply-To: <87y1yiq8ce.fsf@intel.com>

On Tue, 31 May 2022, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Tue, 31 May 2022, William Tseng <william.tseng@intel.com> wrote:
>> This is a workaround for HDMI 1.4 sink which has a CEA mode with higher vic
>> than what is defined in CEA-861-D.
>>
>> As an example, a HDMI 1.4 sink has the video format 2560x1080p to be
>> displayed and the video format is indicated by both SVD (with vic 90 and
>> pictuure aspect ratio 64:27) and DTD.  When connecting to such sink,
>> source can't output the video format in SVD because an error is returned by
>> drm_hdmi_avi_infoframe_from_display_mode(), which can't fill the infoframe
>> with pictuure aspect ratio 64:27 and the vic, which is originally 90 and is
>> changed to 0 by drm_mode_cea_vic().
>>
>> To work around it, this patch ignores such CEA modes in do_cea_modes() so
>> the modes won't be processed in drm_hdmi_avi_infoframe_from_display_mode().
>> And only the video format in DTD can be dispalyed.

I think we should also have a bug filed on this, with the offending EDID
attached for posterity.

BR,
Jani.


>>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Wayne Lin <waynelin@amd.com>
>> Cc: Lee Shawn C <shawn.c.lee@intel.com>
>> Signed-off-by: William Tseng <william.tseng@intel.com>
>> ---
>>  drivers/gpu/drm/drm_edid.c | 39 +++++++++++++++++++++++++-------------
>>  1 file changed, 26 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
>> index bc43e1b32092..a93f68878bfd 100644
>> --- a/drivers/gpu/drm/drm_edid.c
>> +++ b/drivers/gpu/drm/drm_edid.c
>> @@ -3982,6 +3982,19 @@ drm_display_mode_from_cea_vic(struct drm_device *dev,
>>  }
>>  EXPORT_SYMBOL(drm_display_mode_from_cea_vic);
>>  
>> +static bool is_hdmi2_sink(const struct drm_connector *connector)
>> +{
>> +	/*
>> +	 * FIXME: sil-sii8620 doesn't have a connector around when
>> +	 * we need one, so we have to be prepared for a NULL connector.
>> +	 */
>> +	if (!connector)
>> +		return true;
>> +
>> +	return connector->display_info.hdmi.scdc.supported ||
>> +		connector->display_info.color_formats & DRM_COLOR_FORMAT_YCBCR420;
>> +}
>> +
>>  static int
>>  do_cea_modes(struct drm_connector *connector, const u8 *db, u8 len)
>>  {
>> @@ -3993,6 +4006,19 @@ do_cea_modes(struct drm_connector *connector, const u8 *db, u8 len)
>>  
>>  		mode = drm_display_mode_from_vic_index(connector, db, len, i);
>>  		if (mode) {
>> +			u8 vic = svd_to_vic(db[i]);
>> +
>> +			if (!drm_valid_cea_vic(vic))
>> +				continue;
>
> drm_display_mode_from_vic_index() returns NULL in this case.
>
>> +
>> +			/*
>> +			 * HDMI 1.4 VIC range: 1 <= VIC <= 64 (CEA-861-D) but
>> +			 * HDMI 2.0 VIC range: 1 <= VIC <= 107 (CEA-861-F). So we
>> +			 * have to make sure we dont break HDMI 1.4 sinks.
>> +			 */
>> +			if (!is_hdmi2_sink(connector) && vic > 64)
>> +				continue;
>
> I'll need to double check if this is the right thing to do... but I
> guess the question becomes if this shouldn't be within
> drm_display_mode_from_vic_index().
>
> Duplicating the condition from drm_mode_cea_vic() is probably not a good
> idea.
>
> The continues in both above branches leak the mode.
>
>
> BR,
> Jani.
>
>
>> +
>>  			/*
>>  			 * YCBCR420 capability block contains a bitmap which
>>  			 * gives the index of CEA modes from CEA VDB, which
>> @@ -5846,19 +5872,6 @@ void drm_set_preferred_mode(struct drm_connector *connector,
>>  }
>>  EXPORT_SYMBOL(drm_set_preferred_mode);
>>  
>> -static bool is_hdmi2_sink(const struct drm_connector *connector)
>> -{
>> -	/*
>> -	 * FIXME: sil-sii8620 doesn't have a connector around when
>> -	 * we need one, so we have to be prepared for a NULL connector.
>> -	 */
>> -	if (!connector)
>> -		return true;
>> -
>> -	return connector->display_info.hdmi.scdc.supported ||
>> -		connector->display_info.color_formats & DRM_COLOR_FORMAT_YCBCR420;
>> -}
>> -
>>  static u8 drm_mode_hdmi_vic(const struct drm_connector *connector,
>>  			    const struct drm_display_mode *mode)
>>  {

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-05-31 11:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 10:34 [Intel-gfx] [PATCH] drm/edid: ignore the CEA modes not defined in CEA-861-D William Tseng
2022-05-31 10:34 ` William Tseng
2022-05-31 10:56 ` Jani Nikula
2022-05-31 11:06   ` Jani Nikula [this message]
2022-06-01  9:43     ` Tseng, William
2022-06-01  9:56       ` Jani Nikula
2022-06-01 10:02         ` Tseng, William
2022-06-01 10:15           ` Jani Nikula
2022-06-01  9:42   ` Tseng, William
2022-05-31 13:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/edid: ignore the CEA modes not defined in CEA-861-D (rev2) Patchwork
2022-05-31 16:15 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-31 16:42 ` [PATCH] drm/edid: ignore the CEA modes not defined in CEA-861-D Ville Syrjälä
2022-06-01  9:57   ` Tseng, William
2022-06-13  4:27 ` [PATCH v2] " William Tseng
2022-06-13  7:25   ` Lin, Wayne
2022-06-13  8:05     ` Tseng, William
2022-06-13  8:11       ` Lin, Wayne
2022-06-13 12:22     ` Tseng, William
2022-06-13 12:26   ` [PATCH v3] " William Tseng
2022-09-20  6:23     ` [Intel-gfx] [PATCH v4] " William Tseng
2022-09-20  6:23       ` William Tseng
2022-09-20  6:49       ` Jani Nikula
2022-09-20  8:22         ` Tseng, William
2022-12-06  9:53           ` Tseng, William
2023-01-04 10:25             ` Jani Nikula
2022-09-20  7:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/edid: ignore the CEA modes not defined in CEA-861-D (rev3) Patchwork
2022-09-20  7:24 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=87r14aq7ux.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=shawn.c.lee@intel.com \
    --cc=waynelin@amd.com \
    --cc=william.tseng@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.