From: Eriksen Xie <xiaolu.xie@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Suraj Kandpal" <suraj.kandpal@intel.com>,
"Arun R Murthy" <arun.r.murthy@intel.com>,
"Mika Kahola" <mika.kahola@intel.com>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Imre Deak" <imre.deak@intel.com>,
"Eriksen Xie" <xiaolu.xie@intel.com>
Subject: [PATCH v2 0/2] drm/i915/lt_phy: Fix the ML to TX mapping
Date: Fri, 20 Nov 2026 14:34:57 +0800 [thread overview]
Message-ID: <cover.1795156437.git.xiaolu.xie@intel.com> (raw)
In-Reply-To: <DS4PPFE901A304FFE20F33BBF2CAE5C4009E3782@DS4PPFE901A304F.namprd11.prod.outlook.com>
v2: Split into two patches as requested by Suraj Kandpal.
Eriksen Xie (2):
drm/i915/lt_phy: Enable TX2 for single lane DP-alt links
drm/i915/lt_phy: Fix the ML to TX mapping for voltage swing
drivers/gpu/drm/i915/display/intel_lt_phy.c | 32 ++++++++++++++-------
1 file changed, 22 insertions(+), 10 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-11-20 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 7:04 [PATCH] drm/i915/lt_phy: Fix the main link to TX mapping Eriksen Xie
2026-11-19 8:00 ` ✓ i915.CI.BAT: success for " Patchwork
2026-11-19 18:02 ` ✗ i915.CI.Full: failure " Patchwork
2026-11-20 6:06 ` [PATCH] " Kandpal, Suraj
2026-11-20 6:34 ` Eriksen Xie [this message]
2026-11-20 6:34 ` [PATCH v2 1/2] drm/i915/lt_phy: Enable TX2 for single lane DP-alt links Eriksen Xie
2026-11-20 6:34 ` [PATCH v2 2/2] drm/i915/lt_phy: Fix the ML to TX mapping for voltage swing Eriksen Xie
2026-11-20 7:02 ` [PATCH] drm/i915/lt_phy: Fix the main link to TX mapping Eriksen Xie
-- strict thread matches above, loose matches on Subject: below --
2026-11-20 6:58 [PATCH v2 0/2] drm/i915/lt_phy: Fix the ML " Eriksen Xie
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=cover.1795156437.git.xiaolu.xie@intel.com \
--to=xiaolu.xie@intel.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=mika.kahola@intel.com \
--cc=suraj.kandpal@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox