[PATCH] drm/edid: limit printk when facing bad edid

2012-08-17 Thread Jerome Glisse
On Fri, Aug 17, 2012 at 3:01 AM, Jani Nikula wrote: > On Thu, 16 Aug 2012, Jerome Glisse wrote: >> On Thu, Aug 16, 2012 at 11:13 AM, Jani Nikula >> wrote: >>> >>> There's a bug [1] where the faster GMBUS transmissions fail with some >>> CRTs, and the fix [2] is to fallback to GPIO bit-banging up

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-17 Thread Jani Nikula
On Thu, 16 Aug 2012, Jerome Glisse wrote: > On Thu, Aug 16, 2012 at 11:13 AM, Jani Nikula > wrote: >> >> There's a bug [1] where the faster GMBUS transmissions fail with some >> CRTs, and the fix [2] is to fallback to GPIO bit-banging upon errors. As >> noted in the bug, the fix still leaves plen

Re: [PATCH] drm/edid: limit printk when facing bad edid

2012-08-17 Thread Jerome Glisse
On Fri, Aug 17, 2012 at 3:01 AM, Jani Nikula wrote: > On Thu, 16 Aug 2012, Jerome Glisse wrote: >> On Thu, Aug 16, 2012 at 11:13 AM, Jani Nikula >> wrote: >>> >>> There's a bug [1] where the faster GMBUS transmissions fail with some >>> CRTs, and the fix [2] is to fallback to GPIO bit-banging up

Re: [PATCH] drm/edid: limit printk when facing bad edid

2012-08-17 Thread Jani Nikula
On Thu, 16 Aug 2012, Jerome Glisse wrote: > On Thu, Aug 16, 2012 at 11:13 AM, Jani Nikula > wrote: >> >> There's a bug [1] where the faster GMBUS transmissions fail with some >> CRTs, and the fix [2] is to fallback to GPIO bit-banging upon errors. As >> noted in the bug, the fix still leaves plen

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-16 Thread Jani Nikula
There's a bug [1] where the faster GMBUS transmissions fail with some CRTs, and the fix [2] is to fallback to GPIO bit-banging upon errors. As noted in the bug, the fix still leaves plenty of EDID dumps in dmesg, so some measures to reduce the EDID error messages would be most welcome. [1] https:

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-16 Thread Jerome Glisse
On Thu, Aug 16, 2012 at 11:13 AM, Jani Nikula wrote: > > There's a bug [1] where the faster GMBUS transmissions fail with some > CRTs, and the fix [2] is to fallback to GPIO bit-banging upon errors. As > noted in the bug, the fix still leaves plenty of EDID dumps in dmesg, so > some measures to re

Re: [PATCH] drm/edid: limit printk when facing bad edid

2012-08-16 Thread Jerome Glisse
On Thu, Aug 16, 2012 at 11:13 AM, Jani Nikula wrote: > > There's a bug [1] where the faster GMBUS transmissions fail with some > CRTs, and the fix [2] is to fallback to GPIO bit-banging upon errors. As > noted in the bug, the fix still leaves plenty of EDID dumps in dmesg, so > some measures to re

Re: [PATCH] drm/edid: limit printk when facing bad edid

2012-08-16 Thread Jani Nikula
There's a bug [1] where the faster GMBUS transmissions fail with some CRTs, and the fix [2] is to fallback to GPIO bit-banging upon errors. As noted in the bug, the fix still leaves plenty of EDID dumps in dmesg, so some measures to reduce the EDID error messages would be most welcome. [1] https:

Re: [PATCH] drm/edid: limit printk when facing bad edid

2012-08-14 Thread Jerome Glisse
On Tue, Aug 14, 2012 at 10:54 AM, Adam Jackson wrote: > On 8/9/12 11:25 AM, j.gli...@gmail.com wrote: >> >> From: Jerome Glisse >> >> Limit printing bad edid information at one time per connector. >> Connector that are connected to a bad monitor/kvm will likely >> stay connected to the same bad m

Re: [PATCH] drm/edid: limit printk when facing bad edid

2012-08-14 Thread Adam Jackson
On 8/9/12 11:25 AM, j.gli...@gmail.com wrote: From: Jerome Glisse Limit printing bad edid information at one time per connector. Connector that are connected to a bad monitor/kvm will likely stay connected to the same bad monitor/kvm and it makes no sense to keep printing the bad edid message.

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-14 Thread Jerome Glisse
On Tue, Aug 14, 2012 at 10:54 AM, Adam Jackson wrote: > On 8/9/12 11:25 AM, j.glisse at gmail.com wrote: >> >> From: Jerome Glisse >> >> Limit printing bad edid information at one time per connector. >> Connector that are connected to a bad monitor/kvm will likely >> stay connected to the same ba

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-14 Thread Adam Jackson
On 8/9/12 11:25 AM, j.glisse at gmail.com wrote: > From: Jerome Glisse > > Limit printing bad edid information at one time per connector. > Connector that are connected to a bad monitor/kvm will likely > stay connected to the same bad monitor/kvm and it makes no > sense to keep printing the bad ed

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-09 Thread j.gli...@gmail.com
From: Jerome Glisse Limit printing bad edid information at one time per connector. Connector that are connected to a bad monitor/kvm will likely stay connected to the same bad monitor/kvm and it makes no sense to keep printing the bad edid message. Signed-off-by: Jerome Glisse --- drivers/gpu/

[PATCH] drm/edid: limit printk when facing bad edid

2012-08-09 Thread j . glisse
From: Jerome Glisse Limit printing bad edid information at one time per connector. Connector that are connected to a bad monitor/kvm will likely stay connected to the same bad monitor/kvm and it makes no sense to keep printing the bad edid message. Signed-off-by: Jerome Glisse --- drivers/gpu/