All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: denis <den.demchenko@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Denis Demchenko <den.demchenko@gmail.com>
Subject: Re: [PATCH] drm/edid: Add quirk for YUK monitor 0xaa01
Date: Tue, 07 Apr 2026 10:51:44 +0300	[thread overview]
Message-ID: <ef9f7a9da9de1fbda178e6ee4c92bbb9d4faad92@intel.com> (raw)
In-Reply-To: <20260401044238.15201-1-den.demchenko@gmail.com>

On Wed, 01 Apr 2026, denis <den.demchenko@gmail.com> wrote:
> From: Denis Demchenko <den.demchenko@gmail.com>
>
> This monitor results in a black screen with amdgpu unless
> EDID_QUIRK_FORCE_8BPC is applied.
>
> Add a quirk to force 8bpc which fixes the issue.
>
> Signed-off-by: Denis Demchenko <den.demchenko@gmail.com>

Would be really useful to have an fdo gitlab issue with the EDID and
possibly dmesg attached before applying quirks.

BR,
Jani.

> ---
>  drivers/gpu/drm/drm_edid.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index ff432ac6b..b533eb74e 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -253,6 +253,9 @@ static const struct edid_quirk {
>  	/* LQ116M1JW10 displays noise when 8 bpc, but display fine as 6 bpc */
>  	EDID_QUIRK('S', 'H', 'P', 0x154c, BIT(EDID_QUIRK_FORCE_6BPC)),
>  
> +	/* YUK */
> +	EDID_QUIRK('Y', 'U', 'K', 0xaa01, EDID_QUIRK_FORCE_8BPC),
> +
>  	/*
>  	 * @drm_edid_internal_quirk entries end here, following with the
>  	 * @drm_edid_quirk entries.

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-04-07  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  4:42 [PATCH] drm/edid: Add quirk for YUK monitor 0xaa01 denis
2026-04-07  7:51 ` Jani Nikula [this message]
2026-04-08 13:06   ` Denis Demchenko
2026-04-08 13:22     ` Jani Nikula
2026-04-20 18:21       ` Alex Deucher

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=ef9f7a9da9de1fbda178e6ee4c92bbb9d4faad92@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=den.demchenko@gmail.com \
    --cc=dri-devel@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.