linux/drivers/gpu/drm
Jerome Glisse ca2ccde5e2 drm/radeon: on hotplug force link training to happen (v2)
To have DP behave like VGA/DVI we need to retrain the link
on hotplug. For this to happen we need to force link
training to happen by setting connector dpms to off
before asking it turning it on again.

v2: agd5f
- drop the dp_get_link_status() change in atombios_dp.c
  for now.  We still need the dpms OFF change.

Signed-off-by: Jerome Glisse <jglisse@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-07-25 14:14:12 +10:00
..
ast drm: Make the .mode_fixup() operations mode argument a const pointer 2012-07-19 21:52:38 -04:00
cirrus drm: Make the .mode_fixup() operations mode argument a const pointer 2012-07-19 21:52:38 -04:00
exynos drm: Make the .mode_fixup() operations mode argument a const pointer 2012-07-19 21:52:38 -04:00
gma500 drm: kill reclaim_buffers callback 2012-07-19 22:50:28 -04:00
i2c drm: Make the .mode_fixup() operations mode argument a const pointer 2012-07-19 21:52:38 -04:00
i810 drm: kill dma queue support 2012-07-19 22:50:55 -04:00
i915 Linux 3.5-rc7 2012-07-20 00:53:28 -04:00
mga drm: kill reclaim_buffers callback 2012-07-19 22:50:28 -04:00
mgag200 drm/mgag200: fix null pointer dereference 2012-07-19 22:05:25 -04:00
nouveau drm: track dev_mapping in more robust and flexible way 2012-07-25 14:09:30 +10:00
r128 drm: kill reclaim_buffers callback 2012-07-19 22:50:28 -04:00
radeon drm/radeon: on hotplug force link training to happen (v2) 2012-07-25 14:14:12 +10:00
savage drm/savage: clean up reclaim_buffers 2012-07-19 22:50:16 -04:00
sis drm/sis: fixup sis_mm ioctl structs 2012-07-19 22:51:58 -04:00
tdfx drm: kill reclaim_buffers callback 2012-07-19 22:50:28 -04:00
ttm
udl Linux 3.5-rc7 2012-07-20 00:53:28 -04:00
via drm/via: clean up reclaim_buffers 2012-07-19 22:48:28 -04:00
vmwgfx drm: track dev_mapping in more robust and flexible way 2012-07-25 14:09:30 +10:00
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_buffer.c
drm_bufs.c drm: kill dma queue support 2012-07-19 22:50:55 -04:00
drm_cache.c
drm_context.c
drm_crtc_helper.c
drm_crtc.c
drm_debugfs.c drm: kill dma queue support 2012-07-19 22:50:55 -04:00
drm_dma.c drm: kill dma queue support 2012-07-19 22:50:55 -04:00
drm_dp_i2c_helper.c
drm_drv.c drm: kill dma queue support 2012-07-19 22:50:55 -04:00
drm_edid_load.c
drm_edid_modes.h
drm_edid.c drm: edid: Don't add inferred modes with higher resolution 2012-07-03 11:18:10 +01:00
drm_encoder_slave.c
drm_fb_helper.c drm/fb helper: don't call drm_crtc_helper_set_config 2012-07-19 21:24:32 -04:00
drm_fops.c drm: track dev_mapping in more robust and flexible way 2012-07-25 14:09:30 +10:00
drm_gem.c drm: Add colouring to the range allocator 2012-07-16 05:59:37 +10:00
drm_global.c
drm_hashtab.c
drm_info.c drm: kill dma queue support 2012-07-19 22:50:55 -04:00
drm_ioc32.c
drm_ioctl.c
drm_irq.c drm: Disallow DRM_IOCTL_MODESET_CTL for KMS drivers 2012-07-18 06:05:48 +10:00
drm_lock.c drm: ditch strange DRIVER_DMA_QUEUE only error bail-out 2012-07-19 22:50:47 -04:00
drm_memory.c
drm_mm.c drm: Add colouring to the range allocator 2012-07-16 05:59:37 +10:00
drm_modes.c
drm_pci.c drm/pci: add support for getting the supported link bw. 2012-07-19 22:29:25 -04:00
drm_platform.c
drm_prime.c
drm_proc.c drm: kill dma queue support 2012-07-19 22:50:55 -04:00
drm_scatter.c
drm_stub.c
drm_sysfs.c drm: fail gracefully when proc isn't setup. 2012-07-16 05:57:03 +10:00
drm_trace_points.c
drm_trace.h
drm_usb.c
drm_vm.c
Kconfig
Makefile
README.drm

************************************************************
* For the very latest on DRI development, please see:      *
*     http://dri.freedesktop.org/                          *
************************************************************

The Direct Rendering Manager (drm) is a device-independent kernel-level
device driver that provides support for the XFree86 Direct Rendering
Infrastructure (DRI).

The DRM supports the Direct Rendering Infrastructure (DRI) in four major
ways:

    1. The DRM provides synchronized access to the graphics hardware via
       the use of an optimized two-tiered lock.

    2. The DRM enforces the DRI security policy for access to the graphics
       hardware by only allowing authenticated X11 clients access to
       restricted regions of memory.

    3. The DRM provides a generic DMA engine, complete with multiple
       queues and the ability to detect the need for an OpenGL context
       switch.

    4. The DRM is extensible via the use of small device-specific modules
       that rely extensively on the API exported by the DRM module.


Documentation on the DRI is available from:
    http://dri.freedesktop.org/wiki/Documentation
    http://sourceforge.net/project/showfiles.php?group_id=387
    http://dri.sourceforge.net/doc/

For specific information about kernel-level support, see:

    The Direct Rendering Manager, Kernel Support for the Direct Rendering
    Infrastructure
    http://dri.sourceforge.net/doc/drm_low_level.html

    Hardware Locking for the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/hardware_locking_low_level.html

    A Security Analysis of the Direct Rendering Infrastructure
    http://dri.sourceforge.net/doc/security_low_level.html