On Fri, Jun 27, 2014 at 03:21:20PM -0700, Rodrigo Vivi wrote:
Reviewed-by: Rodrigo Vivi [1]rodrigo.v...@intel.com
On Fri, Jun 27, 2014 at 3:09 PM, Ben Widawsky
[2]benjamin.widaw...@intel.com wrote:
There are some cases in the code where we need to know how many rings to
There seems to be a regression in the upcoming Linux 3.16-rc2 release
candidate that I bisected down to this first bad commit:
[dbb42748ac4929987c1449ecb296b39ef8956b62] drm/i915: Move the C3 LP
write bit setup to gen3_init_clock_gating() for KMS.
Can you attach the dmesg with rc2 and
On Fri, 27 Jun 2014, Jesse Barnes jesse.bar...@intel.com wrote:
On Tue, 24 Jun 2014 18:27:40 +0300
Jani Nikula jani.nik...@intel.com wrote:
Historically we've exposed the full backlight PWM duty cycle range to
the userspace, in the name of mechanism, not policy. However, it turns
out there
On Fri, 27 Jun 2014, Scot Doyle lkm...@scotdoyle.com wrote:
The Dell 11 Chromebook laptop has a controllable backlight although its
VBT reports otherwise.
Signed-off-by: Scot Doyle lkm...@scotdoyle.com
CC: Jani Nikula jani.nik...@intel.com
Tested-bys on patches 3-4 would be awesome.
BR,
On Fri, 27 Jun 2014, Scot Doyle lkm...@scotdoyle.com wrote:
Add a quirk to assert the presence of a controllable backlight. Use it to
ignore the VBT backlight presence check during backlight setup.
Tested-by: James Duley jagdu...@gmail.com
Signed-off-by: Scot Doyle lkm...@scotdoyle.com
CC:
On Fri, 27 Jun 2014, Scot Doyle lkm...@scotdoyle.com wrote:
commit c675949ec58ca50d5a3ae3c757892f1560f6e896
drm/i915: do not setup backlight if not available according to VBT
caused a regression on machines with a misconfigured VBT. Add a quirk to
assert the presence of a controllable
On Sat, Jun 28, 2014 at 07:20:38AM +0100, Chris Wilson wrote:
On Fri, Jun 27, 2014 at 03:21:20PM -0700, Rodrigo Vivi wrote:
Reviewed-by: Rodrigo Vivi [1]rodrigo.v...@intel.com
On Fri, Jun 27, 2014 at 3:09 PM, Ben Widawsky
[2]benjamin.widaw...@intel.com wrote:
There are
Hello Daniel,
just to close my request:
The latest git pull from Linus' tree fixed my issue.
vmlinuz-3.16.0-rc2-00211-gd7933ab (26.6. 21:19) was bad
vmlinuz-3.16.0-rc2-00319-g3e7b256 (28.6. 09:23) works again
There are two pulls with 'drm-fixes' and 'x86/urgent' in this area.
Don't know what
On Sat, Jun 28, 2014 at 08:28:55PM +0100, Chris Wilson wrote:
On Sat, Jun 28, 2014 at 08:26:15AM -0700, Ben Widawsky wrote:
On Sat, Jun 28, 2014 at 07:20:38AM +0100, Chris Wilson wrote:
diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c
b/drivers/gpu/drm/i915/i915_gpu_error.c
