From: Imre Deak <imre.deak@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, Jani Nikula <jani.nikula@intel.com>
Subject: Re: [PATCH v2 19/21] drm/i915/dp: Add debugfs entry to force link training failure
Date: Thu, 23 May 2024 19:32:06 +0300 [thread overview]
Message-ID: <Zk9vhqCU8kWTYsMs@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <Zk9g3nvs261GQtdz@intel.com>
On Thu, May 23, 2024 at 06:29:34PM +0300, Ville Syrjälä wrote:
> On Mon, May 20, 2024 at 09:58:17PM +0300, Imre Deak wrote:
> > Add a connector debugfs entry to force a failure during the following
> > 1-2 link training. The entry will auto-reset after the specified link
> > training events are complete.
> >
> > v2: Add the entry from intel_dp_link_training.c (Jani)
> >
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > .../drm/i915/display/intel_display_types.h | 1 +
> > .../drm/i915/display/intel_dp_link_training.c | 52 ++++++++++++++++++-
> > 2 files changed, 52 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> > index e1c41cece249d..dbe1468fe471d 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> > @@ -1770,6 +1770,7 @@ struct intel_dp {
> > bool retrain_disabled;
> > /* Sequential link training failures after a passing LT */
> > int seq_train_failures;
> > + int force_train_failure;
> > } link;
> > bool reset_link_params;
> > int mso_link_count;
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_link_training.c b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
> > index 764187bc42ff9..b40148a42f442 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_link_training.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_link_training.c
> > @@ -1489,7 +1489,10 @@ void intel_dp_start_link_train(struct intel_atomic_state *state,
> > else
> > passed = intel_dp_link_train_all_phys(intel_dp, crtc_state, lttpr_count);
> >
> > - if (passed) {
> > + if (intel_dp->link.force_train_failure) {
> > + intel_dp->link.force_train_failure--;
> > + lt_dbg(intel_dp, DP_PHY_DPRX, "Forcing link training failure\n");
> > + } else if (passed) {
> > intel_dp->link.seq_train_failures = 0;
> > intel_ddi_queue_link_check(dig_port, 2000);
> > return;
> > @@ -1799,6 +1802,50 @@ static int i915_dp_max_lane_count_show(void *data, u64 *val)
> > }
> > DEFINE_DEBUGFS_ATTRIBUTE(i915_dp_max_lane_count_fops, i915_dp_max_lane_count_show, NULL, "%llu\n");
> >
> > +static int i915_dp_force_link_training_failure_show(void *data, u64 *val)
> > +{
> > + struct intel_connector *connector = to_intel_connector(data);
> > + struct drm_i915_private *i915 = to_i915(connector->base.dev);
> > + struct intel_dp *intel_dp;
> > + int err;
> > +
> > + err = drm_modeset_lock_single_interruptible(&i915->drm.mode_config.connection_mutex);
> > + if (err)
> > + return err;
> > +
> > + intel_dp = intel_connector_to_intel_dp(connector);
> > + *val = intel_dp->link.force_train_failure;
> > +
> > + drm_modeset_unlock(&i915->drm.mode_config.connection_mutex);
> > +
> > + return 0;
> > +}
> > +
> > +static int i915_dp_force_link_training_failure_write(void *data, u64 val)
> > +{
> > + struct intel_connector *connector = to_intel_connector(data);
> > + struct drm_i915_private *i915 = to_i915(connector->base.dev);
> > + struct intel_dp *intel_dp;
> > + int err;
> > +
> > + if (val > 2)
>
> Why 2 specifically?
There are 2 back-to-back link trainings that can fail after a modeset or
later after detecting a bad link state, the initial one and a second
with the same LT parameters. That's followed by reducing the LT
parameters and probably a modeset changing the mode.
> > + return -EINVAL;
> > +
> > + err = drm_modeset_lock_single_interruptible(&i915->drm.mode_config.connection_mutex);
> > + if (err)
> > + return err;
> > +
> > + intel_dp = intel_connector_to_intel_dp(connector);
> > + intel_dp->link.force_train_failure = val;
> > +
> > + drm_modeset_unlock(&i915->drm.mode_config.connection_mutex);
> > +
> > + return 0;
> > +}
> > +DEFINE_DEBUGFS_ATTRIBUTE(i915_dp_force_link_training_failure_fops,
> > + i915_dp_force_link_training_failure_show,
> > + i915_dp_force_link_training_failure_write, "%llu\n");
> > +
> > void intel_dp_link_training_debugfs_add(struct intel_connector *connector)
> > {
> > struct dentry *root = connector->base.debugfs_entry;
> > @@ -1818,4 +1865,7 @@ void intel_dp_link_training_debugfs_add(struct intel_connector *connector)
> >
> > debugfs_create_file("i915_dp_max_lane_count", 0444, root,
> > connector, &i915_dp_max_lane_count_fops);
> > +
> > + debugfs_create_file("i915_dp_force_link_training_failure", 0644, root,
> > + connector, &i915_dp_force_link_training_failure_fops);
> > }
> > --
> > 2.43.3
>
> --
> Ville Syrjälä
> Intel
next prev parent reply other threads:[~2024-05-23 16:32 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 18:57 [PATCH v2 00/21] drm/i915/dp_mst: Enable link training fallback Imre Deak
2024-05-20 18:57 ` [PATCH v2 01/21] drm/i915/dp_mst: Align TUs to avoid splitting symbols across MTPs Imre Deak
2024-05-22 18:22 ` Ville Syrjälä
2024-05-20 18:58 ` [PATCH v2 02/21] drm/i915/dp: Move link train params to a substruct in intel_dp Imre Deak
2024-05-20 18:58 ` [PATCH v2 03/21] drm/i915/dp: Move link train fallback to intel_dp_link_training.c Imre Deak
2024-05-22 18:23 ` Ville Syrjälä
2024-06-10 16:13 ` Manasi Navare
2024-05-20 18:58 ` [PATCH v2 04/21] drm/i915/dp: Sanitize intel_dp_get_link_train_fallback_values() Imre Deak
2024-05-22 18:23 ` Ville Syrjälä
2024-05-22 18:45 ` Imre Deak
2024-05-23 15:48 ` Jani Nikula
2024-05-20 18:58 ` [PATCH v2 05/21] drm/i915: Factor out function to modeset commit a set of pipes Imre Deak
2024-05-22 18:23 ` Ville Syrjälä
2024-05-20 18:58 ` [PATCH v2 06/21] drm/i915/dp: Use a commit modeset for link retraining MST links Imre Deak
2024-05-23 12:58 ` Ville Syrjälä
2024-05-23 13:26 ` Imre Deak
2024-05-20 18:58 ` [PATCH v2 07/21] drm/i915/dp: Recheck link state after modeset Imre Deak
2024-05-22 13:38 ` Imre Deak
2024-05-23 13:23 ` Ville Syrjälä
2024-05-23 13:27 ` Ville Syrjälä
2024-05-23 13:30 ` Ville Syrjälä
2024-05-23 13:46 ` Imre Deak
2024-05-23 13:58 ` Ville Syrjälä
2024-05-23 14:12 ` Imre Deak
2024-05-20 18:58 ` [PATCH v2 08/21] drm/i915/dp: Reduce link params only after retrying with unchanged params Imre Deak
2024-05-20 18:58 ` [PATCH v2 09/21] drm/i915/dp: Pass atomic state to link training function Imre Deak
2024-05-23 14:41 ` Ville Syrjälä
2024-05-23 14:47 ` Imre Deak
2024-05-23 14:54 ` Ville Syrjälä
2024-05-23 14:58 ` Imre Deak
2024-05-23 15:05 ` Ville Syrjälä
2024-05-20 18:58 ` [PATCH v2 10/21] drm/i915/dp: Send a link training modeset-retry uevent to all MST connectors Imre Deak
2024-05-20 18:58 ` [PATCH v2 11/21] drm/i915/dp: Use check link state work in the hotplug handler Imre Deak
2024-05-20 18:58 ` [PATCH v2 12/21] drm/i915/dp: Use check link state work in the detect handler Imre Deak
2024-05-23 15:08 ` Ville Syrjälä
2024-05-23 15:29 ` Imre Deak
2024-05-23 15:43 ` Ville Syrjälä
2024-05-23 15:54 ` Imre Deak
2024-05-27 5:14 ` gareth.yu
2024-05-27 11:30 ` Imre Deak
2024-05-28 5:33 ` Yu, Gareth
2024-05-20 18:58 ` [PATCH v2 13/21] drm/i915/dp: Use check link state work in the HPD IRQ handler Imre Deak
2024-05-20 18:58 ` [PATCH v2 14/21] drm/i915/dp: Disable link retraining after the last fallback step Imre Deak
2024-05-23 15:28 ` Ville Syrjälä
2024-05-23 16:36 ` Imre Deak
2024-05-20 18:58 ` [PATCH v2 15/21] drm/i915/dp_mst: Reset intel_dp->link_trained during disabling Imre Deak
2024-05-20 18:58 ` [PATCH v2 16/21] drm/i915/dp_mst: Enable link training fallback for MST Imre Deak
2024-05-20 18:58 ` [PATCH v2 17/21] drm/i915/dp: Add debugfs entries to set a target link rate/lane count Imre Deak
2024-05-23 15:25 ` Ville Syrjälä
2024-05-23 16:15 ` Imre Deak
2024-05-20 18:58 ` [PATCH v2 18/21] drm/i915/dp: Add debugfs entries to get the max " Imre Deak
2024-05-20 18:58 ` [PATCH v2 19/21] drm/i915/dp: Add debugfs entry to force link training failure Imre Deak
2024-05-23 15:29 ` Ville Syrjälä
2024-05-23 16:32 ` Imre Deak [this message]
2024-05-20 18:58 ` [PATCH v2 20/21] drm/i915/dp: Add debugfs entry to force link retrain Imre Deak
2024-05-20 18:58 ` [PATCH v2 21/21] drm/i915/dp: Add debugfs entry for link training info Imre Deak
2024-05-20 19:30 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp_mst: Enable link training fallback (rev3) Patchwork
2024-05-20 19:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-05-20 19:41 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-21 5:58 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-22 4:20 ` ✓ Fi.CI.IGT: 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=Zk9vhqCU8kWTYsMs@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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