From: Ioann Komarov <kivan1337@gmail.com>
To: Arun R Murthy <arun.r.murthy@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Imre Deak <imre.deak@intel.com>,
Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH] drm/i915/mst: let the branch-sink check uncompressed with 18bpp
Date: Mon, 19 Oct 2026 09:36:55 +0300 [thread overview]
Message-ID: <1792391815.ae0036ac0925@gmail.com> (raw)
In-Reply-To: <20260804094450.125307-1-arun.r.murthy@intel.com>
On Tue, Aug 04, 2026 at 03:14:50PM +0530, Arun R Murthy wrote:
> mst_connector_mode_valid_ctx() uses a single 18bpp floor for both
Tested on ADL-P (ThinkPad T14 Gen 3, 8086:46a6) with a Lenovo 40AY
USB-C dock (Synaptics MST branch, fw 5.6) and a 2560x1440@180 monitor
without DSC, so the dock decompresses. The link is 2 lanes of HBR3.
Without the patch the 180Hz mode is pruned with CLOCK_HIGH. With it
(backported to 7.2.8, which still has intel_dp_max_link_rate()) the
mode is listed and runs with DSC at compressed-bpp 16, port_clock
810000, lane_count 2. Logs are in
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/17207
The same dock and failure on MTL are reported in issue 17207, and on
RPL-P in issue 16640.
Tested-by: Ioann Komarov <ioannkomarov@proton.me>
Adding Imre and Ankit, since the patch went out without reviewers on
Cc. Could one of you take a look?
next prev parent reply other threads:[~2026-10-19 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 9:44 [PATCH] drm/i915/mst: let the branch-sink check uncompressed with 18bpp Arun R Murthy
2026-08-05 1:41 ` ✓ i915.CI.BAT: success for " Patchwork
2026-08-05 12:11 ` ✓ i915.CI.Full: " Patchwork
2026-08-05 13:11 ` ✓ CI.KUnit: success for drm/i915/mst: let the branch-sink check uncompressed with 18bpp (rev2) Patchwork
2026-08-05 13:47 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-08-06 0:27 ` ✗ Xe.CI.FULL: " Patchwork
2026-10-07 7:37 ` [PATCH] drm/i915/mst: let the branch-sink check uncompressed with 18bpp Murthy, Arun R
2026-10-19 6:36 ` Ioann Komarov [this message]
2026-10-19 12:06 ` Jani Nikula
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=1792391815.ae0036ac0925@gmail.com \
--to=kivan1337@gmail.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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.