linux.git/include/drm, branch v2.6.29

drm: fix EDID parser problem with positive/negative hsync/vsync

2009-03-11T02:18:48+00:00

Comparing the layouts of struct detail_pixel_timing with
x.org's struct detailed_timings and how those are handled,
it appears that the hsync_positive and vsync_positive
fields are backwards.

This patch fixes https://bugs.freedesktop.org/show_bug.cgi?id=20019
for me. It was tested on 2 monitors, LG FLATRON L225WS 22" and
a YAKUMO 17" for which more details are unknown.

Signed-off-by: Pantelis Koukousoulas 
Signed-off-by: Dave Airlie

drm: disable encoders before re-routing them

2009-02-25T04:42:23+00:00

In some cases we may receive a mode config that has a different
CRTC<->encoder map that the current configuration.  In that case, we
need to disable any re-routed encoders before setting the mode,
otherwise they may not pick up the new CRTC (if the output types are
incompatible for example).

Tested-by: Kristian Høgsberg 
Signed-off-by: Jesse Barnes 
Signed-off-by: Dave Airlie

drm: Fix ordering of bit fields in EDID structure leading huge vsync values.

2009-02-25T04:11:00+00:00

Signed-off-by: Jesse Barnes 
Reviewed-by: Eric Anholt 
Signed-off-by: Dave Airlie

drm/i915: Keep refs on the object over the lifetime of vmas for GTT mmap.

2009-02-20T02:21:13+00:00

This fixes potential fault at fault time if the object was unreferenced
while the mapping still existed.  Now, while the mmap_offset only lives
for the lifetime of the object, the object also stays alive while a vma
exists that needs it.

Signed-off-by: Jesse Barnes 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie

drm: Propagate failure from setting crtc base.

2009-02-20T02:21:12+00:00

Check the error paths within intel_pipe_set_base() to first cleanup and
then report back the error.

Signed-off-by: Chris Wilson 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie

drm: Release user fbs in drm_release

2009-02-20T02:21:11+00:00

Avoids leaking fbs and associated buffers on release.

Signed-off-by: Kristian Høgsberg 
Tested-by: Tested-by: Chris Wilson 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie

drm/i915: add fence register management to execbuf

2009-02-08T11:38:02+00:00

Adds code to set up fence registers at execbuf time on pre-965 chips as
necessary.  Also fixes up a few bugs in the pre-965 tile register support
(get_order != ffs).  The number of fences available to the kernel defaults
to the hw limit minus 3 (for legacy X front/back/depth), but a new parameter
allows userspace to override that as needed.

Signed-off-by: Jesse Barnes 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie

drm: Rip out the racy, unused vblank signal code.

2009-01-28T15:50:14+00:00

Schedule a vblank signal, kill the process, and we'll go walking over freed
memory.  Given that no open-source userland exists using this, nor have I
ever heard of a consumer, just let this code die.

Signed-off-by: Eric Anholt 
Requested-by: Linus Torvalds 
Acked-by: Dave Airlie 
Signed-off-by: Linus Torvalds

drm: create mode_config idr lock

2009-01-22T07:53:05+00:00

Create a separate mode_config IDR lock for simplicity.  The core DRM
config structures (connector, mode, etc. lists) are still protected by
the mode_config mutex, but the CRTC IDR (used for the various identifier
IDs) is now protected by the mode_config idr_mutex.  Simplifies the
locking a bit and removes a warning.

All objects are protected by the config mutex, we may in the future,
split the object further to have reference counts.

Signed-off-by: Jesse Barnes 
Signed-off-by: Dave Airlie

drm: initial KMS config fixes

2009-01-16T08:40:54+00:00

When mode setting is first initialized, the driver will call into
drm_helper_initial_config() to set up an initial output and framebuffer
configuration.  This routine is responsible for probing the available
connectors, encoders, and crtcs, looking for modes and putting together
something reasonable (where reasonable is defined as "allows kernel
messages to be visible on as many displays as possible").

However, the code was a bit too aggressive in setting default modes when
none were found on a given connector.  Even if some connectors had modes,
any connectors found lacking modes would have the default 800x600 mode added
to their mode list, which in some cases could cause problems later down the
line.  In my case, the LVDS was perfectly available, but the initial config
code added 800x600 modes to both of the detected but unavailable HDMI
connectors (which are on my non-existent docking station).  This ended up
preventing later code from setting a mode on my LVDS, which is bad.

This patch fixes that behavior by making the initial config code walk
through the connectors first, counting the available modes, before it decides
to add any default modes to a possibly connected output.  It also fixes the
logic in drm_target_preferred() that was causing zeroed out modes to be set
as the preferred mode for a given connector, even if no modes were available.

Signed-off-by: Jesse Barnes 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie