From: Manasi Navare <manasi.d.navare@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/5] drm/i915: Find fallback link rate/lane count
Date: Thu, 17 Nov 2016 11:44:45 -0800 [thread overview]
Message-ID: <20161117194444.GA18199@intel.com> (raw)
In-Reply-To: <87d1huz2ih.fsf@intel.com>
On Thu, Nov 17, 2016 at 02:58:46PM +0200, Jani Nikula wrote:
> On Tue, 15 Nov 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.
> >
> > 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>
> > ---
> > drivers/gpu/drm/i915/intel_dp.c | 42 ++++++++++++++++++++++++++++++++++++++++
> > drivers/gpu/drm/i915/intel_drv.h | 6 ++++++
> > 2 files changed, 48 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > index a1b0181..e87b451 100644
> > --- a/drivers/gpu/drm/i915/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > @@ -288,6 +288,48 @@ 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 common_len;
> > + int link_rate_index = -1;
> > +
> > + common_len = intel_dp_common_rates(intel_dp, common_rates);
> > + link_rate_index = intel_dp_link_rate_index(intel_dp,
> > + common_rates,
> > + link_rate);
> > + if (link_rate_index > 0) {
> > + intel_dp->fallback_link_rate_index = link_rate_index - 1;
> > + intel_dp->fallback_link_rate = common_rates[intel_dp->fallback_link_rate_index];
>
> fallback_link_rate_index and fallback_link_rate are two ways to express
> the same thing, and you can derive one from the other. When you have
> two, you run the risk of having them out of sync. I thought I'd
> mentioned this in earlier review.
>
> Please do not store fallback_link_rate_index in intel_dp. Only store
> fallback_link_rate. You can use your intel_dp_link_rate_index() function
> when you need to convert rate to index.
>
> Moreover, resetting the state becomes more clear when all can be set to
> 0.
>
> BR,
> Jani.
>
Thanks Jani.
From the previous feedback, I removed the redundant link_train_failed variable
stored in intel_dp, but retained the link_rate_index. I will look at this and see
if this can be optimized.
Manasi
> > + intel_dp->fallback_lane_count = intel_dp_max_lane_count(intel_dp);
> > + } else if (lane_count > 1) {
> > + intel_dp->fallback_link_rate_index = common_len - 1;
> > + intel_dp->fallback_link_rate = common_rates[intel_dp->fallback_link_rate_index];
> > + intel_dp->fallback_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 75252ec..55ceb44 100644
> > --- a/drivers/gpu/drm/i915/intel_drv.h
> > +++ b/drivers/gpu/drm/i915/intel_drv.h
> > @@ -887,6 +887,10 @@ struct intel_dp {
> > uint32_t DP;
> > int link_rate;
> > uint8_t lane_count;
> > + int fallback_link_rate;
> > + uint8_t fallback_lane_count;
> > + int fallback_link_rate_index;
> > + bool link_train_failed;
> > uint8_t sink_count;
> > bool link_mst;
> > bool has_audio;
> > @@ -1383,6 +1387,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-11-17 19:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 3:13 [PATCH 0/5] Handle link training failure during modeset Manasi Navare
2016-11-15 3:13 ` [PATCH 1/5] drm: Add a new connector property for link status Manasi Navare
2016-11-15 3:13 ` [PATCH 2/5] drm: Set DRM connector link status property Manasi Navare
2016-11-15 3:23 ` Manasi Navare
2016-11-15 7:50 ` Daniel Vetter
2016-11-15 7:49 ` [Intel-gfx] " Daniel Vetter
2016-11-15 23:56 ` Manasi Navare
2016-11-16 7:35 ` [Intel-gfx] " Daniel Vetter
2016-11-15 7:53 ` Daniel Vetter
2016-11-16 1:13 ` Manasi Navare
2016-11-16 7:29 ` Daniel Vetter
2016-11-16 1:58 ` [PATCH v2 " Manasi Navare
2016-11-15 3:13 ` [PATCH 3/5] drm/i915: Update CRTC state if connector link status property changed Manasi Navare
2016-11-15 3:13 ` [PATCH 4/5] drm/i915: Find fallback link rate/lane count Manasi Navare
2016-11-16 17:32 ` Manasi Navare
2016-11-17 12:58 ` Jani Nikula
2016-11-17 19:44 ` Manasi Navare [this message]
2016-11-15 3:13 ` [PATCH 5/5] drm/i915: Implement Link Rate fallback on Link training failure Manasi Navare
2016-11-16 17:34 ` Manasi Navare
2016-11-17 12:49 ` Jani Nikula
2016-11-17 19:55 ` Manasi Navare
2016-11-15 4:24 ` ✓ Fi.CI.BAT: success for Handle Link Training Failure during modeset (rev2) Patchwork
2016-11-17 12:29 ` [PATCH 0/5] Handle link training failure during modeset Jani Nikula
2016-11-17 19:48 ` Manasi Navare
-- strict thread matches above, loose matches on Subject: below --
2016-11-19 2:58 [PATCH 0/5] Clean series for Link training failure handling Manasi Navare
2016-11-19 2:59 ` [PATCH 4/5] drm/i915: Find fallback link rate/lane count Manasi Navare
2016-11-18 7:29 [PATCH 5/5] drm/i915: Implement Link Rate fallback on Link training failure Manasi Navare
2016-11-18 7:13 [PATCH 0/5] Link Training failure handling during modeset Manasi Navare
2016-11-18 7:13 ` [PATCH 4/5] drm/i915: Find fallback link rate/lane count Manasi Navare
2016-11-18 7:29 ` Manasi Navare
2016-11-18 13:22 ` Jani Nikula
2016-11-18 15:39 ` Manasi Navare
2016-11-19 2:09 ` Manasi Navare
2016-11-10 4:42 [PATCH 0/5] Handle Link Training Failure during modeset Manasi Navare
2016-11-10 4:42 ` [PATCH 4/5] drm/i915: Find fallback link rate/lane count Manasi Navare
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=20161117194444.GA18199@intel.com \
--to=manasi.d.navare@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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).