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 0/3] drm/i915/display: Try YCbCr420 color when RGB fails Date: Thu, 6 May 2021 19:23:22 +0200 [thread overview] Message-ID: <20210506172325.1995964-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 5. Only change to 4 is a small whitespace error fix. Resend because automation tools did not work with wrong e-mail format used before.
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 0/3] drm/i915/display: Try YCbCr420 color when RGB fails Date: Thu, 6 May 2021 19:23:22 +0200 [thread overview] Message-ID: <20210506172325.1995964-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 5. Only change to 4 is a small whitespace error fix. Resend because automation tools did not work with wrong e-mail format used before. _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-05-06 17:23 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-06 17:23 Werner Sembach [this message] 2021-05-06 17:23 ` [Intel-gfx] [PATCH 0/3] drm/i915/display: Try YCbCr420 color when RGB fails Werner Sembach 2021-05-06 17:23 ` [PATCH 1/3] drm/i915/display: New function to avoid duplicate code in upcomming commits Werner Sembach 2021-05-06 17:23 ` [Intel-gfx] " Werner Sembach 2021-05-06 17:23 ` [PATCH 2/3] drm/i915/display: Restructure output format computation for better expandability Werner Sembach 2021-05-06 17:23 ` [Intel-gfx] " Werner Sembach 2021-05-06 17:23 ` [PATCH 3/3] drm/i915/display: Use YCbCr420 as fallback when RGB fails Werner Sembach 2021-05-06 17:23 ` [Intel-gfx] " Werner Sembach 2021-05-06 17:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Try YCbCr420 color " Patchwork 2021-05-06 18:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-05-06 19:21 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork 2021-05-07 8:49 ` [PATCH v6 0/3] " Werner Sembach 2021-05-07 8:49 ` [Intel-gfx] " Werner Sembach 2021-05-07 8:49 ` [PATCH v6 1/3] drm/i915/display: New function to avoid duplicate code in upcomming commits Werner Sembach 2021-05-07 8:49 ` [Intel-gfx] " Werner Sembach 2021-05-07 17:47 ` Ville Syrjälä 2021-05-07 17:47 ` [Intel-gfx] " Ville Syrjälä 2021-05-07 17:47 ` Ville Syrjälä 2021-05-07 20:33 ` Werner Sembach 2021-05-07 20:33 ` [Intel-gfx] " Werner Sembach 2021-05-07 20:33 ` Werner Sembach 2021-05-07 8:49 ` [PATCH v6 2/3] drm/i915/display: Restructure output format computation for better expandability Werner Sembach 2021-05-07 8:49 ` [Intel-gfx] " Werner Sembach 2021-05-07 17:52 ` Ville Syrjälä 2021-05-07 17:52 ` [Intel-gfx] " Ville Syrjälä 2021-05-07 17:52 ` Ville Syrjälä 2021-05-07 17:56 ` Randy Dunlap 2021-05-07 17:56 ` [Intel-gfx] " Randy Dunlap 2021-05-07 17:56 ` Randy Dunlap 2021-05-07 21:24 ` Werner Sembach 2021-05-07 21:24 ` [Intel-gfx] " Werner Sembach 2021-05-07 21:24 ` Werner Sembach 2021-05-07 8:49 ` [PATCH v6 3/3] drm/i915/display: Use YCbCr420 as fallback when RGB fails Werner Sembach 2021-05-07 8:49 ` [Intel-gfx] " Werner Sembach -- strict thread matches above, loose matches on Subject: below -- 2021-05-05 17:23 [PATCH 0/3] drm/i915/display Try YCbCr420 color " Werner Sembach 2021-05-05 17:23 ` Werner Sembach 2021-05-05 17:14 Werner Sembach 2021-05-05 17:14 ` Werner Sembach
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=20210506172325.1995964-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: linkBe 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.