[PATCH] drm: Use a nondestructive mode for output detect when polling (v2)

2010-09-14 Thread Chris Wilson
v2: Julien Cristau pointed out that @nondestructive results in double-negatives and confusion when trying to interpret the parameter, so use @force instead. Much easier to type as well. ;-) And fix the miscompilation of vmgfx reported by Sedat Dilek. Signed-off-by: Chris Wilson Cc: stable at

[PATCH] drm: Use a nondestructive mode for output detect when polling (v2)

2010-09-14 Thread Chris Wilson
v2: Julien Cristau pointed out that @nondestructive results in double-negatives and confusion when trying to interpret the parameter, so use @force instead. Much easier to type as well. ;-) And fix the miscompilation of vmgfx reported by Sedat Dilek. Signed-off-by: Chris Wilson

[PATCH] drm: Use a nondestructive mode for output detect when polling (v2)

2010-09-10 Thread Chris Wilson
Destructive load-detection is very expensive and due to failings elsewhere can trigger system wide stalls of up to 600ms. A simple first step to correcting this is not to invoke such an expensive and destructive load-detection operation automatically. Whilst updating the other drivers, I did not

[PATCH] drm: Use a nondestructive mode for output detect when polling

2010-09-10 Thread Chris Wilson
Destructive load-detection is very expensive and due to failings elsewhere can trigger system wide stalls of up to 600ms. A simple first step to correcting this is not to invoke such an expensive and destructive load-detection operation automatically. Bugzilla:

[PATCH] drm: Use a nondestructive mode for output detect when polling (v2)

2010-09-10 Thread Chris Wilson
Destructive load-detection is very expensive and due to failings elsewhere can trigger system wide stalls of up to 600ms. A simple first step to correcting this is not to invoke such an expensive and destructive load-detection operation automatically. Whilst updating the other drivers, I did not

[PATCH] drm: Use a nondestructive mode for output detect when polling

2010-09-09 Thread Chris Wilson
Destructive load-detection is very expensive and due to failings elsewhere can trigger system wide stalls of up to 600ms. A simple first step to correcting this is not to invoke such an expensive and destructive load-detection operation automatically. Bugzilla: