Re: [Intel-gfx] [PATCH 0/5] Handle link training failure during modeset

2016-11-17 Thread Manasi Navare
On Thu, Nov 17, 2016 at 02:29:30PM +0200, Jani Nikula wrote: > On Tue, 15 Nov 2016, Manasi Navare wrote: > > Submitting new series that adds proper commit messages/cover letter > > and kernel documentation. It also moved the set_link_status function > > to drm core so

Re: [Intel-gfx] [PATCH 0/5] Handle link training failure during modeset

2016-11-17 Thread Jani Nikula
On Tue, 15 Nov 2016, Manasi Navare wrote: > Submitting new series that adds proper commit messages/cover letter > and kernel documentation. It also moved the set_link_status function > to drm core so other kernel drivers can make use of it. > > The idea presented in

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-14 Thread Harry Wentland
Overall this patch set makes sense but I think it would be good to move some stuff to common code instead of leaving it in i915. I'm thinking about patch 2 (setting the link status property) in particular but also tend to agree with Ville and Daniel about their comments for patch 5. That

[Intel-gfx] [PATCH 0/5] Handle link training failure during modeset

2016-11-14 Thread Manasi Navare
Submitting new series that adds proper commit messages/cover letter and kernel documentation. It also moved the set_link_status function to drm core so other kernel drivers can make use of it. The idea presented in these patches is to address link training failure in a way that: a) changes the

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-14 Thread Manasi Navare
On Mon, Nov 14, 2016 at 08:07:39PM -0500, Harry Wentland wrote: > Overall this patch set makes sense but I think it would be good to > move some stuff to common code instead of leaving it in i915. I'm > thinking about patch 2 (setting the link status property) in > particular but also tend to

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-14 Thread Manasi Navare
: Cheng, Tony <tony.ch...@amd.com>; intel-gfx@lists.freedesktop.org; Peres, > Martin <martin.pe...@intel.com>; dri-de...@lists.freedesktop.org; Deucher, > Alexander <alexander.deuc...@amd.com>; Wentland, Harry > <harry.wentl...@amd.com> > Subject: Re: [Intel-gfx] [PATCH 0/

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-14 Thread Cheng, Tony
eucher, Alexander <alexander.deuc...@amd.com>; Wentland, Harry <harry.wentl...@amd.com> Subject: Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset On Sun, Nov 13, 2016 at 11:43:01PM -0800, Manasi Navare wrote: > On Fri, Nov 11, 2016 at 07:42:16PM +, Cheng, Tony wr

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-14 Thread Daniel Vetter
el.com>; Manasi Navare <manasi.d.nav...@intel.com>; > > dri-de...@lists.freedesktop.org; intel-gfx@lists.freedesktop.org; Wentland, > > Harry <harry.wentl...@amd.com>; Peres, Martin <martin.pe...@intel.com> > > Subject: Re: [Intel-gfx] [PATCH 0/5] Handle Link

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-13 Thread Manasi Navare
Cheng, Tony <tony.ch...@amd.com> > > Cc: Deucher, Alexander <alexander.deuc...@amd.com>; 'Jani Nikula' > > <jani.nik...@linux.intel.com>; Manasi Navare > > <manasi.d.nav...@intel.com>; dri-de...@lists.freedesktop.org; > > intel-gfx@lists.freedesktop

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-11 Thread Cheng, Tony
...@amd.com>; Peres, Martin <martin.pe...@intel.com> Subject: Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset On Fri, Nov 11, 2016 at 04:21:58PM +, Cheng, Tony wrote: > For HDMI, you can yank the cable, plug back in, HDMI will light up without > user mode

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-11 Thread Ville Syrjälä
TCH 0/5] Handle Link Training Failure > > during modeset > > > > Adding Harry and Tony from our display team to review. > > > > > -----Original Message- > > > From: Jani Nikula [mailto:jani.nik...@linux.intel.com] > > > Sent: Thursday, Novemb

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-11 Thread Cheng, Tony
si Navare > <manasi.d.nav...@intel.com>; dri-de...@lists.freedesktop.org; > intel-gfx@lists.freedesktop.org; Wentland, Harry > <harry.wentl...@amd.com>; Cheng, Tony <tony.ch...@amd.com> > Cc: Dave Airlie <airl...@gmail.com>; Peres, Martin > <martin.pe...@intel.com> &g

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-11 Thread Ville Syrjälä
reedesktop.org; > intel-gfx@lists.freedesktop.org; Wentland, Harry <harry.wentl...@amd.com>; > Cheng, Tony <tony.ch...@amd.com> > Cc: Dave Airlie <airl...@gmail.com>; Peres, Martin <martin.pe...@intel.com> > Subject: RE: [Intel-gfx] [PATCH 0/5] Handle Li

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-11 Thread Cheng, Tony
.@gmail.com>; Peres, Martin <martin.pe...@intel.com> Subject: RE: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset Adding Harry and Tony from our display team to review. > -Original Message- > From: Jani Nikula [mailto:jani.nik...@linux.intel.com] > Sent: Thu

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-10 Thread Deucher, Alexander
t; Cc: Dave Airlie; Peres, Martin; Deucher, Alexander > Subject: Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during > modeset > > On Thu, 10 Nov 2016, Manasi Navare <manasi.d.nav...@intel.com> wrote: > > Link training failure is handled by lowering the link r

Re: [Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-10 Thread Jani Nikula
On Thu, 10 Nov 2016, Manasi Navare wrote: > Link training failure is handled by lowering the link rate first > until it reaches the minimum and keeping the lane count maximum > and then lowering the lane count until it reaches minimim. These > fallback values are saved

[Intel-gfx] [PATCH 0/5] Handle Link Training Failure during modeset

2016-11-09 Thread Manasi Navare
Link training failure is handled by lowering the link rate first until it reaches the minimum and keeping the lane count maximum and then lowering the lane count until it reaches minimim. These fallback values are saved and hotplug uevent is sent to the userspace after setting the connector link