From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
alex.hung@amd.com, harry.wentland@amd.com, siqueira@igalia.com
Subject: Re: [PATCH] drm/amd/display: Reject YUV422 encoding over DP on DCE
Date: Wed, 24 Sep 2025 12:44:08 +0200 [thread overview]
Message-ID: <b445a38f-2fb1-4f4f-b91e-925624295113@gmail.com> (raw)
In-Reply-To: <CADnq5_Pj43m4C2esgH5wVFfbq5rSehSeL-7NkdwHU0ByNSRdUg@mail.gmail.com>
On 9/19/25 17:09, Alex Deucher wrote:
> On Fri, Sep 19, 2025 at 4:14 AM Timur Kristóf <timur.kristof@gmail.com> wrote:
>>
>> Mark YUV422 unsupported over DP on DCE to work around a
>> regression caused by the recent YUV422 fallback patch.
>>
>> See https://gitlab.freedesktop.org/drm/amd/-/issues/4585
>>
>> The recent YUV422 fallback breaks DisplayPort on DCE6-10 because
>> it can select a high refresh rate mode with YUV422 and 6 BPC,
>> which is apparently not actually supported by the HW, causing
>> it to boot to a "no signal" screen.
>>
>> Tested with a Samsung Odyssey G7 on the following GPUs:
>>
>> - Cape Verde (DCE 6): affected
>> - Tonga (DCE 10): affected
>> - Polaris (DCE 11.2): not affected
>> - Vega (DCE 12): not affected
>>
>> Polaris and Vega are not affected because the same mode
>> gets rejected by other parts of the code base, possibly the
>> bandwidth calculation which exists for DCE11+ but not older HW.
>>
>> It is not documented whether YUV422 is actually supported over DP
>> on DCE, but considering that this encoding was never used before,
>> and that YUV420 is already marked unsupported, probably not.
>>
>> Signed-off-by: Timur Kristóf <timur.kristof@gmail.com>
>
> Fixes: db291ed1732e02 ("drm/amd/display: Add fallback path for YCBCR422")
> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4585
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
>
> Would be good to get feedback from the display team on what the actual
> capabilities are, but seems reasonable to me.
>
> Alex
Please disregard this patch.
I will send a different patch which will instead reject modes that would
require a pixel clock higher than the maximum display clock.
Thanks,
Timur
prev parent reply other threads:[~2025-09-24 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 8:14 [PATCH] drm/amd/display: Reject YUV422 encoding over DP on DCE Timur Kristóf
2025-09-19 15:09 ` Alex Deucher
2025-09-19 15:20 ` timur.kristof
2025-09-24 10:44 ` Timur Kristóf [this message]
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=b445a38f-2fb1-4f4f-b91e-925624295113@gmail.com \
--to=timur.kristof@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=siqueira@igalia.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.