From: Jani Nikula <jani.nikula@intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>,
intel-gfx@lists.freedesktop.org, imre.deak@intel.com
Subject: Re: [PATCH] drm/i915/display/dp: 128/132b DP-capable with SST
Date: Mon, 08 Jan 2024 15:30:42 +0200 [thread overview]
Message-ID: <875y04x88t.fsf@intel.com> (raw)
In-Reply-To: <20240103090715.307309-1-arun.r.murthy@intel.com>
On Wed, 03 Jan 2024, Arun R Murthy <arun.r.murthy@intel.com> wrote:
> With a value of '0' read from MSTM_CAP register MST to be enabled.
> DP2.1 SCR updates the spec for 128/132b DP capable supporting only one
> stream and not supporting single stream sideband MSG.
> The underlying protocol will be MST to enable use of MTP.
>
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 9ff0cbd9c0df..40d3280f8d98 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -4038,8 +4038,13 @@ intel_dp_configure_mst(struct intel_dp *intel_dp)
> if (!intel_dp_mst_source_support(intel_dp))
> return;
>
> - intel_dp->is_mst = sink_can_mst &&
> - i915->display.params.enable_dp_mst;
> + /*
> + * Even if dpcd reg MSTM_CAP is 0, if the sink supports UHBR rates then
> + * DP2.1 can be enabled with underlying protocol using MST for MTP
> + */
> + intel_dp->is_mst = (sink_can_mst ||
> + drm_dp_is_uhbr_rate(intel_dp_max_common_rate(intel_dp)))
> + && i915->display.params.enable_dp_mst;
We use drm_dp_is_uhbr_rate() in intel_dp_is_uhbr() to determine whether
the link rate in the *crtc state* is uhbr, and by proxy whether the link
in the *crtc state* is 128b/132b.
There, we've already decided to use uhbr and 128b/132b.
This one here is different, and I think it's taking us to the wrong
direction. For example, it should be possible to downgrade the link from
uhbr to non-uhbr on link failures. We don't have that yet. But this
makes untangling that even harder.
BR,
Jani.
>
> drm_dp_mst_topology_mgr_set_mst(&intel_dp->mst_mgr,
> intel_dp->is_mst);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-08 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 9:07 [PATCH] drm/i915/display/dp: 128/132b DP-capable with SST Arun R Murthy
2024-01-04 6:08 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display/dp: 128/132b DP-capable with SST (rev2) Patchwork
2024-01-04 6:27 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-01-05 1:24 ` [PATCH] drm/i915/display/dp: 128/132b DP-capable with SST Almahallawy, Khaled
2024-01-08 11:38 ` Nautiyal, Ankit K
2024-01-08 11:58 ` Murthy, Arun R
2024-01-08 13:30 ` Jani Nikula [this message]
2024-01-09 2:50 ` Murthy, Arun R
2024-01-09 9:28 ` Jani Nikula
2024-01-09 9:29 ` Jani Nikula
2024-01-10 10:50 ` Murthy, Arun R
2024-01-10 10:53 ` Jani Nikula
2024-01-10 11:05 ` Murthy, Arun R
2024-01-10 10:42 ` Murthy, Arun R
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=875y04x88t.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.