From: Marco Nenciarini <mnencia@kcore.it>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, ville.syrjala@linux.intel.com,
imre.deak@intel.com, jani.nikula@linux.intel.com,
lyude@redhat.com, xiaolu.xie@intel.com
Subject: Re: [PATCH] drm/i915/dp: clear and restore MSTM_CTRL around MST DPMS off/on
Date: Wed, 14 Oct 2026 11:55:19 +0200 [thread overview]
Message-ID: <as9Rh1Yt8Fkj6JpE@spark.kcore.it> (raw)
In-Reply-To: <20261014081448.2320363-1-xiaolu.xie@intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Tested-by: Marco Nenciarini <mnencia@kcore.it>
Tested on a Dell Pro Max 16 (Arrow Lake-P) with Debian 7.2.6 and a Dell
WD19DC dock (Synaptics VMM5331 MST hub, fw 05.07.08) with two monitors
behind it, i915 driving the dock over TBT-alt.
Without the patch, a DPMS off of more than about 6 s leaves both
monitors black on wake: the link status of the sink behind the hub goes
from 0x77 to 0x00 and the hub does not retrain it. With the patch,
30 s, 60 s and 120 s DPMS off all kept the link and both monitors came
back. The log shows MSTM_CTRL cleared before D3 and restored after D0,
before POWER_UP_PHY, as intended. Details are in
drm/i915/kernel#16901.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEfCO4BD5l0pgKIbbiWJ8D8BulUDgFAmrPUYUACgkQWJ8D8Bul
UDimag/+L0A6aKYws/asUDWsKnx4DjKXbQtXjYCVXx8Sqv7wG7PgYvXOONOJzvD1
dxUOxuWLDBx6sRBA6zLmtIdkkifPUHbWhADQLIOnmNqIGutzjg/Rg/TIqmtufy+w
J4lxsmO6khoLa16dZZMp9p4CYgQMOd36NuWG/uSBNcNF96uxzZYjCoO5uXorCkg/
7SCa2neKrIoXXwSEuamQC3FB83I0PXoaxP/FgzZmYDzN1IEUya4EkS78jIPCGmWC
54gz9+hNz0yRT7IgfoluNzHVnP8GftLS7t2DPH1ClZVxw6bE+UnBwpJRQ9mpCkXd
DX3RCZq9E176ESqIDKI/4d+nO8AKQp06aiOExDylNU38NlSNOpPH8iN4XqwYZ2hv
WlpR33hPneA1zosdZ6oFOAPNDLvF1FFuUFtA+wVLJLNNoNTRAVseHGZsR/xdL7kh
X0gIyu1h2SP4wfKySiuvUmgQVm0uFphr4x+FgKn1XoZ+P0CDyjxqoFVDvE8iplb4
1IixcQAPvFasF7wq3pd2eAUh7n2zMcroi99cllGY2uPbxiOPhiWzcVV1NmQ7nHhq
uFcyTlM8nV+TdZYYGCRLFkH7MHskzEGbKO+CQkYrayRPcZxZwnytnHY+CyqGr4sY
732Djo9oELBZF/fYhSBiVi7cij0NFDdadvhV1gfThIT7BH+5qhs=
=2SVO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2026-10-14 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:14 [PATCH] drm/i915/dp: clear and restore MSTM_CTRL around MST DPMS off/on Xiao Lu
2026-10-14 8:40 ` sashiko-bot
2026-10-14 8:54 ` ✓ CI.KUnit: success for " Patchwork
2026-10-14 9:41 ` ✗ i915.CI.BAT: failure " Patchwork
2026-10-14 9:55 ` Marco Nenciarini [this message]
2026-10-14 15:09 ` ✓ Xe.CI.BAT: success " Patchwork
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=as9Rh1Yt8Fkj6JpE@spark.kcore.it \
--to=mnencia@kcore.it \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=lyude@redhat.com \
--cc=ville.syrjala@linux.intel.com \
--cc=xiaolu.xie@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.