[Intel-gfx] Bug Team Status

[Jani Nikula]

The weekly bug team status for the past week.

== Daniel

Mostly looked at the ILK bug and stiched together a revert of the
shrinker changes. Still no idea about the underlying cause. Details in
the commit [1].

Otherwise the usual bug scrubbing activities with 1-2 failed patch
attempts.

[1] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?id=93927ca52a55c23e0a6a305e7e9082e8411ac9fa

== Ville

Working on bug https://bugs.freedesktop.org/show_bug.cgi?id=46800

Reading CEA-861 and HDMI specs to get to the bottom of how the RGB
quantization range stuff should be handled.

Fixed the current code for ILK-IVB.

Made a prototype patch for fixing it on HSW+ using the pipe CSC block.
Tried to check the power consuptiom impact of the pipe CSC method on my
ILK laptop, didn't see any real difference in ACPI power numbers. Asked
Ouping to make some measurements too, no results yet.

Started to code up support for parsing the QS bit from EDID CEA block,
and based on that setting the Q bits in the AVI infoframe to inform the
display about the currently used quantization range. Unfortunately my
test TV doesn't support this stuff, so it's untested as of now.

Currently working on an "Automatic" mode for the "Broadcast RGB"
property, which would follow the guidelines set forth by CEA-861.
Hopefully it will result in the driver picking the correct quantization
range in most cases w/o user intervention.

I'll try to post the infoframe and automatic property patches still
today.

== Jani

Went through all the open bugs, getting an overview of it all. While at
it, flipped the NEEDINFO state as necessary; roughly a third of our bugs
are pending info from the reporters. About half of the bugs seem to be
KMS related. Particularly in the backlight department we may have a
bunch of dupes, but we prefer to keep them separate to be sure any fix
handles them all.

Debugged a number of bugs, requesting info as necessary, but failed at
cracking them. There was one better FORCEWAKE posting read related patch
attempt that seemingly fixed the issue, but Ben wants us to get to the
bottom of it [2], and rightly so.

[2] https://bugzilla.kernel.org/show_bug.cgi?id=52411