linux-toradex.git/drivers/gpu/drm, branch v3.2.8

drm/i915: no lvds quirk for AOpen MP45

2012-02-20T20:46:14+00:00

commit e57b6886f555ab57f40a01713304e2053efe51ec upstream.

According to a bug report, it doesn't have one.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44263
Acked-by: Chris Wilson 
Signed-Off-by: Daniel Vetter 
Signed-off-by: Keith Packard 
Signed-off-by: Greg Kroah-Hartman

drm/i915: Force explicit bpp selection for intel_dp_link_required

2012-02-20T20:46:14+00:00

commit c898261c0dad617f0f1080bedc02d507a2fcfb92 upstream.

It is never correct to use intel_crtc->bpp in intel_dp_link_required,
so instead pass an explicit bpp in to this function. This patch
only supports 18bpp and 24bpp modes, which means that 10bpc modes will
be computed incorrectly. Fixing that will require more extensive
changes, and so must be addressed separately from this bugfix.

intel_dp_link_required is called from intel_dp_mode_valid and
intel_dp_mode_fixup.

* intel_dp_mode_valid is called to list supported modes; in this case,
  the current crtc values cannot be relevant as the modes in question
  may never be selected. Thus, using intel_crtc->bpp is never right.

* intel_dp_mode_fixup is called during mode setting, but it is run
  well before ironlake_crtc_mode_set is called to set intel_crtc->bpp,
  so using intel_crtc-bpp in this path can only ever get a stale
  value.

Cc: Lubos Kolouch 
Cc: Adam Jackson 
Reviewed-by: Daniel Vetter 
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=42263
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44881
Tested-by: Dave Airlie 
Tested-by: camalot@picnicpark.org (Dell Latitude 6510)
Tested-by: Roland Dreier 
Signed-off-by: Keith Packard 
Signed-off-by: Greg Kroah-Hartman

drm/i915: protect force_wake_(get|put) with the gt_lock

2012-02-13T19:16:58+00:00

commit 9f1f46a45a681d357d1ceedecec3671a5ae957f4 upstream.

The problem this patch solves is that the forcewake accounting
necessary for register reads is protected by dev->struct_mutex. But the
hangcheck and error_capture code need to access registers without
grabbing this mutex because we hold it while waiting for the gpu.
So a new lock is required. Because currently the error_state capture
is called from the error irq handler and the hangcheck code runs from
a timer, it needs to be an irqsafe spinlock (note that the registers
used by the irq handler (neglecting the error handling part) only uses
registers that don't need the forcewake dance).

We could tune this down to a normal spinlock when we rework the
error_state capture and hangcheck code to run from a workqueue.  But
we don't have any read in a fastpath that needs forcewake, so I've
decided to not care much about overhead.

This prevents tests/gem_hangcheck_forcewake from i-g-t from killing my
snb on recent kernels - something must have slightly changed the
timings. On previous kernels it only trigger a WARN about the broken
locking.

v2: Drop the previous patch for the register writes.

v3: Improve the commit message per Chris Wilson's suggestions.

Signed-Off-by: Daniel Vetter 
Reviewed-by: Chris Wilson 
Reviewed-by: Eugeni Dodonov 
Signed-off-by: Keith Packard 
Signed-off-by: Eugeni Dodonov 
Signed-off-by: Greg Kroah-Hartman

drm/i915: convert force_wake_get to func pointer in the gpu reset code

2012-02-13T19:16:57+00:00

commit 8109021313c7a3d8947677391ce6ab9cd0bb1d28 upstream.

This was forgotten in the original multi-threaded forcewake
conversion:

commit 8d715f0024f64ad1b1be85d8c081cf577944c847
Author: Keith Packard 
Date:   Fri Nov 18 20:39:01 2011 -0800

    drm/i915: add multi-threaded forcewake support

Signed-off-by: Daniel Vetter 
Reviewed-by: Eugeni Dodonov 
Signed-off-by: Keith Packard 
Signed-off-by: Eugeni Dodonov 
Signed-off-by: Greg Kroah-Hartman

drm/i915: handle 3rd pipe

2012-02-13T19:16:57+00:00

commit 07c1e8c1462fa7324de4c36ae9e55da2abd79cee upstream.

We don't need to check 3rd pipe specifically, as it shares PLL with some
other one.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=41977
Signed-off-by: Eugeni Dodonov 
Reviewed-by: Jesse Barnes 
Signed-off-by: Keith Packard 
Signed-off-by: Greg Kroah-Hartman

drm/i915: Fix TV Out refresh rate.

2012-02-13T19:16:57+00:00

commit 23bd15ec662344dc10e9918fdd0dbc58bc71526d upstream.

TV Out refresh rate was half of the specification for almost all modes.
Due to this reason pixel clock was so low for some modes causing flickering screen.

Signed-off-by: Rodrigo Vivi 
Reviewed-by: Jesse Barnes 
Signed-off-by: Keith Packard 
Signed-off-by: Eugeni Dodonov 
Signed-off-by: Greg Kroah-Hartman

drm/i915: check ACTHD of all rings

2012-02-13T19:16:57+00:00

commit 097354eb14fa94d31a09c64d640643f58e4a5a9a upstream.

Otherwise hangcheck spuriously fires when running blitter/bsd-only
workloads.

Contrary to a similar patch by Ben Widawsky this does not check
INSTDONE of the other rings. Chris Wilson implied that in a failure to
detect a hang, most likely because INSTDONE was fluctuating. Thus only
check ACTHD, which as far as I know is rather reliable. Also, blitter
and bsd rings can't launch complex tasks from a single instruction
(like 3D_PRIM on the render with complex or even infinite shaders).

This fixes spurious gpu hang detection when running
tests/gem_hangcheck_forcewake on snb/ivb.

Signed-Off-by: Daniel Vetter 
Reviewed-by: Chris Wilson 
Signed-off-by: Keith Packard 
Signed-off-by: Eugeni Dodonov 
Signed-off-by: Greg Kroah-Hartman

drm/i915: DisplayPort hot remove notification to audio driver

2012-02-13T19:16:57+00:00

commit 832afda6a7d7235ef0e09f4ec46736861540da6d upstream.

On DP monitor hot remove, clear DP_AUDIO_OUTPUT_ENABLE accordingly,
so that the audio driver will receive hot plug events and take action
to refresh its device state and ELD contents.

Note that the DP_AUDIO_OUTPUT_ENABLE bit may be enabled or disabled
only when the link training is complete and set to "Normal".

Tested OK for both hot plug/remove and DPMS on/off.

Signed-off-by: Wu Fengguang 
Signed-off-by: Keith Packard 
Signed-off-by: Eugeni Dodonov 
Signed-off-by: Greg Kroah-Hartman

drm/i915: HDMI hot remove notification to audio driver

2012-02-13T19:16:57+00:00

commit 2deed761188d7480eb5f7efbfe7aa77f09322ed8 upstream.

On HDMI monitor hot remove, clear SDVO_AUDIO_ENABLE accordingly, so that
the audio driver will receive hot plug events and take action to refresh
its device state and ELD contents.

The cleared SDVO_AUDIO_ENABLE bit needs to be restored to prevent losing
HDMI audio after DPMS on.

CC: Wang Zhenyu 
Signed-off-by: Wu Fengguang 
Signed-off-by: Keith Packard 
Signed-off-by: Eugeni Dodonov 
Signed-off-by: Greg Kroah-Hartman

drm/radeon/kms: fix TRAVIS panel setup

2012-02-13T19:16:56+00:00

commit 304a48400d9718f74ec35ae46f30868a5f4c4516 upstream.

Different versions of the DP to LVDS bridge chip
need different panel mode settings depending on
the chip version used.

Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=41569

Signed-off-by: Alex Deucher 
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman