[PATCH 4/4] drm/i915: Implement Link Rate fallback on Link training failure

2016-12-08 Thread Jani Nikula
On Tue, 06 Dec 2016, Manasi Navare wrote: > If link training at a link rate optimal for a particular > mode fails during modeset's atomic commit phase, then we > let the modeset complete and then retry. We save the link rate > value at which link training failed, update the link status property >

[PATCH 4/4] drm/i915: Implement Link Rate fallback on Link training failure

2016-12-08 Thread Manasi Navare
On Thu, Dec 08, 2016 at 11:51:30PM +0200, Jani Nikula wrote: > On Tue, 06 Dec 2016, Manasi Navare wrote: > > If link training at a link rate optimal for a particular > > mode fails during modeset's atomic commit phase, then we > > let the modeset complete and then retry. We save the link rate > >

[PATCH 4/4] drm/i915: Implement Link Rate fallback on Link training failure

2016-12-08 Thread Manasi Navare
Hi Jani, Could you please review this patch? This patch was changed a bit from the last time you reviewed it based on feedback from Sean Paul that the driver need not validate the modes and prune the mode on link training failure. Instead it should just send the hotplug uevent after setting link

[PATCH 4/4] drm/i915: Implement Link Rate fallback on Link training failure

2016-12-05 Thread Manasi Navare
If link training at a link rate optimal for a particular mode fails during modeset's atomic commit phase, then we let the modeset complete and then retry. We save the link rate value at which link training failed, update the link status property to "BAD" and use a lower link rate to prune the