Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Cooper Chiou <cooper.chiou@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Cooper Chiou <cooper.chiou@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/edid: filter DisplayID v2.0 CTA block in audio detection
Date: Mon, 21 Mar 2022 11:05:33 +0200	[thread overview]
Message-ID: <87h77rllpe.fsf@intel.com> (raw)
In-Reply-To: <20220321044330.27723-1-cooper.chiou@intel.com>

On Mon, 21 Mar 2022, Cooper Chiou <cooper.chiou@intel.com> wrote:
> In DisplayID v2.0 CTS data block 0x81 case, there is no any audio
> information definition, but drm_detect_monitor_audio didn't filter
> it so that it caused eDP dummy audio card be detected improperly.
>
> We observed this issue on some AUO/BOE eDP panel with DID v2.0 CTA
> block, and fix issue by adding filter for edid_ext[0]=DATA_BLOCK_CTA
> case.

Please let's not add hacks like this, at all.

BR,
Jani.

>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Shawn C Lee <shawn.c.lee@intel.com>
>
> Signed-off-by: Cooper Chiou <cooper.chiou@intel.com>
> ---
>  drivers/gpu/drm/drm_edid.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index f5f5de362ff2..6c9ae4b130bd 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -4845,7 +4845,7 @@ bool drm_detect_monitor_audio(struct edid *edid)
>  	int start_offset, end_offset;
>  
>  	edid_ext = drm_find_cea_extension(edid);
> -	if (!edid_ext)
> +	if (!edid_ext || (edid_ext[0] == DATA_BLOCK_CTA))
>  		goto end;
>  
>  	has_audio = ((edid_ext[3] & EDID_BASIC_AUDIO) != 0);

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2022-03-21  9:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  4:43 [Intel-gfx] [PATCH] drm/edid: filter DisplayID v2.0 CTA block in audio detection Cooper Chiou
2022-03-21  4:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-03-21  5:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-21  7:13 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-21  9:05 ` Jani Nikula [this message]
2022-03-23  5:45 ` [Intel-gfx] [v2] drm/edid: check basic audio support on CEA extension block Lee Shawn C
2022-03-23  9:40   ` Jani Nikula
2022-03-23  5:53 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/edid: filter DisplayID v2.0 CTA block in audio detection (rev2) Patchwork
2022-03-23  6:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-23  9:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-23 10:03 ` [Intel-gfx] [PATCH] drm/edid: filter DisplayID v2.0 CTA block in audio detection Jani Nikula
2022-03-23 10:31   ` Lee, Shawn C
2022-03-23 10:40     ` Jani Nikula
2022-03-23 13:35       ` Lee, Shawn C
2022-03-24  6:12 ` [Intel-gfx] [v3] drm/edid: check basic audio support on CEA extension block Lee Shawn C
2022-03-24  6:16 ` Lee Shawn C
2022-03-24  9:57   ` Jani Nikula
2022-03-24  6:19 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/edid: filter DisplayID v2.0 CTA block in audio detection (rev4) Patchwork
2022-03-24  6:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-24  7: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=87h77rllpe.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=cooper.chiou@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox