From: Werner Sembach <wse@tuxedocomputers.com>
To: ville.syrjala@linux.intel.com, airlied@linux.ie, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/3] drm/i915/display: Try YCbCr420 color when RGB fails
Date: Mon, 10 May 2021 15:33:46 +0200 [thread overview]
Message-ID: <20210510133349.14491-1-wse@tuxedocomputers.com> (raw)
When encoder validation of a display mode fails, retry with less bandwidth
heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups
to support 4k60Hz output, which previously failed silently.
AMDGPU had nearly the exact same issue. This problem description is
therefore copied from my commit message of the AMDGPU patch.
On some setups, while the monitor and the gpu support display modes with
pixel clocks of up to 600MHz, the link encoder might not. This prevents
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be
possible. However, which color mode is used is decided before the link
encoder capabilities are checked. This patch fixes the problem by retrying
to find a display mode with YCbCr420 enforced and using it, if it is
valid.
This patchset is revision 7. Fixed a rebase issue in 1/3 and moved message
from error output to debug output in 2/3.
WARNING: multiple messages have this Message-ID (diff)
From: Werner Sembach <wse@tuxedocomputers.com>
To: ville.syrjala@linux.intel.com, airlied@linux.ie, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [Intel-gfx] [PATCH v7 0/3] drm/i915/display: Try YCbCr420 color when RGB fails
Date: Mon, 10 May 2021 15:33:46 +0200 [thread overview]
Message-ID: <20210510133349.14491-1-wse@tuxedocomputers.com> (raw)
When encoder validation of a display mode fails, retry with less bandwidth
heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups
to support 4k60Hz output, which previously failed silently.
AMDGPU had nearly the exact same issue. This problem description is
therefore copied from my commit message of the AMDGPU patch.
On some setups, while the monitor and the gpu support display modes with
pixel clocks of up to 600MHz, the link encoder might not. This prevents
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be
possible. However, which color mode is used is decided before the link
encoder capabilities are checked. This patch fixes the problem by retrying
to find a display mode with YCbCr420 enforced and using it, if it is
valid.
This patchset is revision 7. Fixed a rebase issue in 1/3 and moved message
from error output to debug output in 2/3.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-05-10 13:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 13:33 Werner Sembach [this message]
2021-05-10 13:33 ` [Intel-gfx] [PATCH v7 0/3] drm/i915/display: Try YCbCr420 color when RGB fails Werner Sembach
2021-05-10 13:33 ` [PATCH v7 1/3] drm/i915/display: New function to avoid duplicate code in upcomming commits Werner Sembach
2021-05-10 13:33 ` [Intel-gfx] " Werner Sembach
2021-05-10 13:33 ` [PATCH v7 2/3] drm/i915/display: Restructure output format computation for better expandability Werner Sembach
2021-05-10 13:33 ` [Intel-gfx] " Werner Sembach
2021-05-10 13:33 ` [PATCH v7 3/3] drm/i915/display: Use YCbCr420 as fallback when RGB fails Werner Sembach
2021-05-10 13:33 ` [Intel-gfx] " Werner Sembach
2021-05-10 16:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Try YCbCr420 color when RGB fails (rev2) Patchwork
2021-05-10 18:57 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-05-11 14:31 ` [PATCH v7 0/3] drm/i915/display: Try YCbCr420 color when RGB fails Ville Syrjälä
2021-05-11 14:31 ` [Intel-gfx] " Ville Syrjälä
2021-05-11 14:31 ` Ville Syrjälä
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=20210510133349.14491-1-wse@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.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.