From: Manasi Navare <manasi.d.navare@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v1½ 00/13] drm/i915/dp: link rate and lane count refactoring
Date: Thu, 2 Feb 2017 11:01:42 -0800 [thread overview]
Message-ID: <20170202190141.GB22871@intel.com> (raw)
In-Reply-To: <20170201194006.GA21934@intel.com>
On Wed, Feb 01, 2017 at 11:40:06AM -0800, Manasi Navare wrote:
> Are you planning on submitting a v2 for these pretty soon
> that can make it to patchwork/
>
> Regards
> Manasi
>
> On Thu, Jan 26, 2017 at 09:44:14PM +0200, Jani Nikula wrote:
> > This is kind of version 1½ of [1], basically just rebased on current git
> > (including Manasi's test automation patches) and a couple of more
> > cleanups slammed on top.
> >
> > BR,
> > Jani.
> >
So the problem we still have with link rate fallback after link failure->uevent->
fetch new modes->link retrain is that after we send a uevent, userspace fetches new modes
which calls drm_helper_probe_single_connector_modes() that calls dp_detect which ends up
calling intel_dp_long_pulse(). So while userspace is just trying to fetch new modes
it overwrites the max_link_rate and max_lane_count values through intel_dp_long_pulse().
So while retraining, when it calls intel_dp_compute_config(), it will use the overwritten
values of common_rates/max_link_rate/max_lane_count as opposed to the ones
set in intel_dp_get_fallback_values().
I wonder if this patch series solves this problem somehow...
else, do you have any insight on how we can solve this?
Regards
Manasi
> >
> > [1] http://mid.mail-archive.com/cover.1485015599.git.jani.nikula@intel.com
> >
> >
> > Jani Nikula (13):
> > drm/i915/dp: use known correct array size in rate_to_index
> > drm/i915/dp: return errors from rate_to_index()
> > drm/i915/dp: rename rate_to_index() to intel_dp_find_rate() and reuse
> > drm/i915/dp: cache source rates at init
> > drm/i915/dp: generate and cache sink rate array for all DP, not just
> > eDP 1.4
> > drm/i915/dp: use the sink rates array for max sink rates
> > drm/i915/dp: cache common rates with sink rates
> > drm/i915/dp: do not limit rate seek when not needed
> > drm/i915/dp: don't call the link parameters sink parameters
> > drm/i915/dp: add functions for max common link rate and lane count
> > drm/i915/mst: use max link not sink lane count
> > drm/i915/dp: localize link rate index variable more
> > drm/i915/dp: use readb and writeb calls for single byte DPCD access
> >
> > drivers/gpu/drm/i915/intel_dp.c | 275 ++++++++++++++------------
> > drivers/gpu/drm/i915/intel_dp_link_training.c | 3 +-
> > drivers/gpu/drm/i915/intel_dp_mst.c | 4 +-
> > drivers/gpu/drm/i915/intel_drv.h | 19 +-
> > 4 files changed, 166 insertions(+), 135 deletions(-)
> >
> > --
> > 2.1.4
> >
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-02 19:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 19:44 [PATCH v1½ 00/13] drm/i915/dp: link rate and lane count refactoring Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 01/13] drm/i915/dp: use known correct array size in rate_to_index Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 02/13] drm/i915/dp: return errors from rate_to_index() Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 03/13] drm/i915/dp: rename rate_to_index() to intel_dp_find_rate() and reuse Jani Nikula
2017-02-01 21:46 ` Pandiyan, Dhinakaran
2017-02-02 8:44 ` Jani Nikula
2017-02-07 18:38 ` Pandiyan, Dhinakaran
2017-01-26 19:44 ` [PATCH v1½ 04/13] drm/i915/dp: cache source rates at init Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 05/13] drm/i915/dp: generate and cache sink rate array for all DP, not just eDP 1.4 Jani Nikula
2017-01-27 17:28 ` Ville Syrjälä
2017-01-27 19:52 ` Jani Nikula
2017-01-27 20:00 ` Ville Syrjälä
2017-01-28 10:16 ` [PATCH v2] " Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 06/13] drm/i915/dp: use the sink rates array for max sink rates Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 07/13] drm/i915/dp: cache common rates with " Jani Nikula
2017-02-01 22:08 ` Pandiyan, Dhinakaran
2017-02-02 8:38 ` Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 08/13] drm/i915/dp: do not limit rate seek when not needed Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 09/13] drm/i915/dp: don't call the link parameters sink parameters Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 10/13] drm/i915/dp: add functions for max common link rate and lane count Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 11/13] drm/i915/mst: use max link not sink " Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 12/13] drm/i915/dp: localize link rate index variable more Jani Nikula
2017-02-02 2:54 ` Manasi Navare
2017-02-02 8:42 ` Jani Nikula
2017-02-02 17:29 ` Manasi Navare
2017-02-03 14:11 ` Jani Nikula
2017-01-26 19:44 ` [PATCH v1½ 13/13] drm/i915/dp: use readb and writeb calls for single byte DPCD access Jani Nikula
2017-02-01 19:04 ` [PATCH v1½ 00/13] drm/i915/dp: link rate and lane count refactoring Pandiyan, Dhinakaran
2017-02-01 19:40 ` Manasi Navare
2017-02-02 19:01 ` Manasi Navare [this message]
2017-02-03 14:16 ` 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=20170202190141.GB22871@intel.com \
--to=manasi.d.navare@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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.