From: Jani Nikula <jani.nikula@linux.intel.com>
To: Manasi Navare <manasi.d.navare@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v7 3/4] drm/i915: Find fallback link rate/lane count
Date: Tue, 13 Dec 2016 16:36:29 +0200 [thread overview]
Message-ID: <87vaunsxoy.fsf@intel.com> (raw)
In-Reply-To: <87shpxv358.fsf@intel.com>
On Fri, 09 Dec 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Fri, 09 Dec 2016, Manasi Navare <manasi.d.navare@intel.com> wrote:
>> If link training fails, then we need to fallback to lower
>> link rate first and if link training fails at RBR, then
>> fallback to lower lane count.
>> This function finds the next lower link rate/lane count
>> value after link training failure and limits the max
>> link_rate and lane_count values to these fallback values.
>>
>> v7:
>> * Remove unnecessary intializations and remove redundant
>> call to intel_dp_common_rates (Jani Nikula)
>> v6:
>> * Cap the max link rate and lane count to the max
>> values obtained during fallback link training (Daniel Vetter)
>> v5:
>> * Start the fallback at the lane count value passed not
>> the max lane count (Jani Nikula)
>> v4:
>> * Remove the redundant variable link_train_failed
>> v3:
>> * Remove fallback_link_rate_index variable, just obtain
>> that using the helper intel_dp_link_rate_index (Jani Nikula)
>> v2:
>> Squash the patch that returns the link rate index (Jani Nikula)
>>
>> Acked-by: Tony Cheng <tony.cheng@amd.com>
>> Acked-by: Harry Wentland <harry.wentland@amd.com>
>> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Daniel Vetter <daniel.vetter@intel.com>
>> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
And pushed this one to dinq, thanks for the patch.
BR,
Jani.
>
>
>> ---
>> drivers/gpu/drm/i915/intel_dp.c | 38 ++++++++++++++++++++++++++++++++++++++
>> drivers/gpu/drm/i915/intel_drv.h | 2 ++
>> 2 files changed, 40 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 434dc7d..1b5e0d0 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -278,6 +278,44 @@ static int intel_dp_common_rates(struct intel_dp *intel_dp,
>> common_rates);
>> }
>>
>> +static int intel_dp_link_rate_index(struct intel_dp *intel_dp,
>> + int *common_rates, int link_rate)
>> +{
>> + int common_len;
>> + int index;
>> +
>> + common_len = intel_dp_common_rates(intel_dp, common_rates);
>> + for (index = 0; index < common_len; index++) {
>> + if (link_rate == common_rates[common_len - index - 1])
>> + return common_len - index - 1;
>> + }
>> +
>> + return -1;
>> +}
>> +
>> +int intel_dp_get_link_train_fallback_values(struct intel_dp *intel_dp,
>> + int link_rate, uint8_t lane_count)
>> +{
>> + int common_rates[DP_MAX_SUPPORTED_RATES];
>> + int link_rate_index;
>> +
>> + link_rate_index = intel_dp_link_rate_index(intel_dp,
>> + common_rates,
>> + link_rate);
>> + if (link_rate_index > 0) {
>> + intel_dp->max_sink_link_bw = drm_dp_link_rate_to_bw_code(common_rates[link_rate_index - 1]);
>> + intel_dp->max_sink_lane_count = lane_count;
>> + } else if (lane_count > 1) {
>> + intel_dp->max_sink_link_bw = intel_dp_max_link_bw(intel_dp);
>> + intel_dp->max_sink_lane_count = lane_count >> 1;
>> + } else {
>> + DRM_ERROR("Link Training Unsuccessful\n");
>> + return -1;
>> + }
>> +
>> + return 0;
>> +}
>> +
>> static enum drm_mode_status
>> intel_dp_mode_valid(struct drm_connector *connector,
>> struct drm_display_mode *mode)
>> diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
>> index 377693e..0a20422 100644
>> --- a/drivers/gpu/drm/i915/intel_drv.h
>> +++ b/drivers/gpu/drm/i915/intel_drv.h
>> @@ -1400,6 +1400,8 @@ bool intel_dp_init_connector(struct intel_digital_port *intel_dig_port,
>> void intel_dp_set_link_params(struct intel_dp *intel_dp,
>> int link_rate, uint8_t lane_count,
>> bool link_mst);
>> +int intel_dp_get_link_train_fallback_values(struct intel_dp *intel_dp,
>> + int link_rate, uint8_t lane_count);
>> void intel_dp_start_link_train(struct intel_dp *intel_dp);
>> void intel_dp_stop_link_train(struct intel_dp *intel_dp);
>> void intel_dp_sink_dpms(struct intel_dp *intel_dp, int mode);
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-12-13 14:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 0:27 [PATCH 0/4] Link Training failure handling by sending Hotplug Uevent Manasi Navare
2016-12-06 0:27 ` [PATCH 1/4] drm: Add a new connector atomic property for link status Manasi Navare
2016-12-06 7:23 ` [Intel-gfx] " Daniel Vetter
2016-12-06 15:56 ` Manasi Navare
2016-12-06 16:07 ` [PATCH v4 " Manasi Navare
2016-12-08 15:05 ` Jani Nikula
2016-12-08 15:28 ` [Intel-gfx] " Daniel Vetter
2016-12-08 19:04 ` [PATCH v5 " Manasi Navare
2016-12-08 19:36 ` Sean Paul
2016-12-08 19:48 ` Manasi Navare
2016-12-08 19:47 ` [PATCH v6 " Manasi Navare
2016-12-06 0:27 ` [PATCH 2/4] drm/i915: Compute sink's max lane count/link BW at Hotplug Manasi Navare
2016-12-08 18:15 ` Manasi Navare
2016-12-08 21:23 ` Jani Nikula
2016-12-08 21:39 ` Manasi Navare
2016-12-08 21:48 ` Manasi Navare
2016-12-13 14:28 ` Jani Nikula
2016-12-06 0:27 ` [PATCH 3/4] drm/i915: Find fallback link rate/lane count Manasi Navare
2016-12-08 18:19 ` Manasi Navare
2016-12-08 21:46 ` Jani Nikula
2016-12-08 22:05 ` Manasi Navare
2016-12-09 3:05 ` [PATCH v7 " Manasi Navare
2016-12-09 9:54 ` Jani Nikula
2016-12-13 14:36 ` Jani Nikula [this message]
2016-12-06 0:27 ` [PATCH 4/4] drm/i915: Implement Link Rate fallback on Link training failure Manasi Navare
2016-12-08 18:23 ` Manasi Navare
2016-12-08 21:51 ` Jani Nikula
2016-12-08 22:09 ` Manasi Navare
2016-12-06 0:53 ` ✗ Fi.CI.BAT: failure for Link Training failure handling by sending Hotplug Uevent Patchwork
2016-12-06 16:53 ` ✗ Fi.CI.BAT: failure for Link Training failure handling by sending Hotplug Uevent (rev2) Patchwork
2016-12-08 19:53 ` ✗ Fi.CI.BAT: failure for Link Training failure handling by sending Hotplug Uevent (rev3) Patchwork
2016-12-08 20:23 ` ✗ Fi.CI.BAT: failure for Link Training failure handling by sending Hotplug Uevent (rev4) Patchwork
2016-12-09 4:23 ` ✗ Fi.CI.BAT: failure for Link Training failure handling by sending Hotplug Uevent (rev5) 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=87vaunsxoy.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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.