From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org,
Arun R Murthy <arun.r.murthy@intel.com>
Subject: Re: [PATCH v2 2/6] drm/i915/mst: improve debug logging of DP MST mode detect
Date: Thu, 15 Feb 2024 13:46:48 +0200 [thread overview]
Message-ID: <87jzn654rb.fsf@intel.com> (raw)
In-Reply-To: <Zc0D2L1F5JCXC4ID@intel.com>
On Wed, 14 Feb 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Feb 13, 2024 at 01:30:57PM +0200, Jani Nikula wrote:
>> Rename intel_dp_can_mst() to intel_dp_mst_detect(), and move all DP MST
>> detect debug logging there. Debug log the sink's MST capability,
>> including single-stream sideband messaging support, and the decision
>> whether to enable MST mode or not. Do this regardless of whether we're
>> actually enabling MST or not.
>>
>> Cc: Arun R Murthy <arun.r.murthy@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_dp.c | 45 +++++++++++++++++--------
>> 1 file changed, 31 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index a1c304f451bd..944f566525dd 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -4007,31 +4007,48 @@ intel_dp_get_dpcd(struct intel_dp *intel_dp)
>> intel_dp->downstream_ports) == 0;
>> }
>>
>> +static const char *intel_dp_mst_mode_str(enum drm_dp_mst_mode mst_mode)
>> +{
>> + if (mst_mode == DRM_DP_SST_SIDEBAND_MSG)
>> + return "single-stream sideband messaging";
>> + else
>> + return str_yes_no(mst_mode == DRM_DP_MST);
>
> I wonder if this should also just say "sst"/"mst"/"sst sideband" etc.
> Shrug.
>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
I realize there's an issue here.
intel_dp_detect_dpcd() bails out early for !drm_dp_is_branch(), before
the intel_dp_can_mst() call. (Renamed intel_dp_mst_detect() here.)
We'll still happily call intel_dp_configure_mst() later also for
!branch.
We'll need to call intel_dp_mst_detect() earlier and/or somehow combine
these together. I don't think branch devices need to support MST, but I
think MST devices need to support branching. And single-stream sideband
support does not mean branching.
The intention of this patch was to improve MST debug logging, but the
end result is that it reduces it! Auch.
I wonder if we should branch (eh) the detect earlier for eDP, SST and
MST/branch paths. Just to make it easier for our poor brains to follow.
BR,
Jani.
>
>> +}
>> +
>> static bool
>> -intel_dp_can_mst(struct intel_dp *intel_dp)
>> +intel_dp_mst_detect(struct intel_dp *intel_dp)
>> {
>> struct drm_i915_private *i915 = dp_to_i915(intel_dp);
>> + struct intel_encoder *encoder = &dp_to_dig_port(intel_dp)->base;
>> + enum drm_dp_mst_mode sink_mst_mode;
>> + enum drm_dp_mst_mode mst_detect;
>> +
>> + sink_mst_mode = drm_dp_read_mst_cap(&intel_dp->aux, intel_dp->dpcd);
>> +
>> + if (i915->display.params.enable_dp_mst &&
>> + intel_dp_mst_source_support(intel_dp) &&
>> + sink_mst_mode == DRM_DP_MST)
>> + mst_detect = DRM_DP_MST;
>> + else
>> + mst_detect = DRM_DP_SST;
>>
>> - return i915->display.params.enable_dp_mst &&
>> - intel_dp_mst_source_support(intel_dp) &&
>> - drm_dp_read_mst_cap(&intel_dp->aux, intel_dp->dpcd) == DRM_DP_MST;
>> + drm_dbg_kms(&i915->drm,
>> + "[ENCODER:%d:%s] MST support: port: %s, sink: %s, modparam: %s -> enable: %s\n",
>> + encoder->base.base.id, encoder->base.name,
>> + str_yes_no(intel_dp_mst_source_support(intel_dp)),
>> + intel_dp_mst_mode_str(sink_mst_mode),
>> + str_yes_no(i915->display.params.enable_dp_mst),
>> + intel_dp_mst_mode_str(mst_detect));
>> +
>> + return mst_detect != DRM_DP_SST;
>> }
>>
>> static void
>> intel_dp_configure_mst(struct intel_dp *intel_dp)
>> {
>> struct drm_i915_private *i915 = dp_to_i915(intel_dp);
>> - struct intel_encoder *encoder =
>> - &dp_to_dig_port(intel_dp)->base;
>> bool sink_can_mst = drm_dp_read_mst_cap(&intel_dp->aux, intel_dp->dpcd) == DRM_DP_MST;
>>
>> - drm_dbg_kms(&i915->drm,
>> - "[ENCODER:%d:%s] MST support: port: %s, sink: %s, modparam: %s\n",
>> - encoder->base.base.id, encoder->base.name,
>> - str_yes_no(intel_dp_mst_source_support(intel_dp)),
>> - str_yes_no(sink_can_mst),
>> - str_yes_no(i915->display.params.enable_dp_mst));
>> -
>> if (!intel_dp_mst_source_support(intel_dp))
>> return;
>>
>> @@ -5390,7 +5407,7 @@ intel_dp_detect_dpcd(struct intel_dp *intel_dp)
>> connector_status_connected : connector_status_disconnected;
>> }
>>
>> - if (intel_dp_can_mst(intel_dp))
>> + if (intel_dp_mst_detect(intel_dp))
>> return connector_status_connected;
>>
>> /* If no HPD, poke DDC gently */
>> --
>> 2.39.2
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-15 11:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:30 [PATCH v2 0/6] drm/i915/mst: enable MST mode for 128b/132b single-stream sideband Jani Nikula
2024-02-13 11:30 ` [PATCH v2 1/6] drm/mst: read sideband messaging cap Jani Nikula
2024-02-13 12:56 ` Murthy, Arun R
2024-02-13 13:42 ` Jani Nikula
2024-02-14 18:14 ` Ville Syrjälä
2024-02-13 11:30 ` [PATCH v2 2/6] drm/i915/mst: improve debug logging of DP MST mode detect Jani Nikula
2024-02-14 18:18 ` Ville Syrjälä
2024-02-15 11:46 ` Jani Nikula [this message]
2024-02-15 15:16 ` Ville Syrjälä
2024-02-13 11:30 ` [PATCH v2 3/6] drm/i915/mst: abstract choosing the MST mode to use Jani Nikula
2024-02-14 18:18 ` Ville Syrjälä
2024-02-13 11:30 ` [PATCH v2 4/6] drm/i915/mst: use the MST mode detected previously Jani Nikula
2024-02-14 18:34 ` Ville Syrjälä
2024-02-14 18:41 ` Jani Nikula
2024-02-13 11:31 ` [PATCH v2 5/6] drm/i915/mst: add intel_dp_mst_disconnect() Jani Nikula
2024-02-14 18:34 ` Ville Syrjälä
2024-02-13 11:31 ` [PATCH v2 6/6] drm/i915/mst: enable MST mode for 128b/132b single-stream sideband 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=87jzn654rb.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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: 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;
as well as URLs for NNTP newsgroup(s).