diff options
| author | Imre Deak <imre.deak@intel.com> | 2024-06-10 19:49:29 +0300 |
|---|---|---|
| committer | Imre Deak <imre.deak@intel.com> | 2024-06-13 21:26:49 +0300 |
| commit | c3c90de3a7dec171c671ffcc99eb5cdfe5e88c23 (patch) | |
| tree | ef923670499ae96e7c1235034dd63d5e31077396 /drivers/message | |
| parent | 73afc1e2fd1d3b3f086a4ba1714c8d1ecc40d4f9 (diff) | |
| download | linux-c3c90de3a7dec171c671ffcc99eb5cdfe5e88c23.tar.gz linux-c3c90de3a7dec171c671ffcc99eb5cdfe5e88c23.tar.bz2 linux-c3c90de3a7dec171c671ffcc99eb5cdfe5e88c23.zip | |
drm/i915/dp: Add debugfs entries to force the link rate/lane count
Add connector debugfs entries to force the link rate/lane count to be
used by a link training afterwards. These settings will be clamped to
the supported, i.e. the source's and sink's common rate/lane count.
After forcing the link rate/lane count reset the link training
parameters and for a non-auto setting disable reducing the link
parameters via the fallback logic. The former one can be used after
testing link training failure scenarios - via debugfs entries added
later - to reset the reduced link parameters after the test.
v2:
- Add the entries from intel_dp_link_training.c (Jani)
- Rename the entries to i915_dp_set_link_rate/lane_count.
v3: (Ville)
- Rename the entries/struct fields to force_link_rate/lane_count.
- Lock connection_mutex only for the required intel_dp state.
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240610164933.2947366-18-imre.deak@intel.com
Diffstat (limited to 'drivers/message')
0 files changed, 0 insertions, 0 deletions