linux_dsm_epyc7002/drivers/gpu/drm
Chris Wilson 990bbdadab drm/i915: Group the GT routines together in both code and vtable
Tidy up the routines for interacting with the GT (in particular the
forcewake dance) which are scattered throughout the code in a single
structure.

v2: use wait_for_atomic for polling.

v3: *really* use wait_for_atomic for polling.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-03 22:08:46 +02:00
..
ast
cirrus drm/cirrus: kick out conflicting framebuffers earlier 2012-06-01 11:11:09 +01:00
exynos drm/exynos: fixed blending for hdmi graphic layer 2012-06-05 13:25:18 +09:00
gma500
i2c
i810 i810: switch to vm_mmap() 2012-05-30 21:04:54 -04:00
i915 drm/i915: Group the GT routines together in both code and vtable 2012-07-03 22:08:46 +02:00
mga
mgag200 drm/mgag200: kick off conflicting framebuffers earlier. 2012-06-01 11:12:39 +01:00
nouveau nouveau: add vmap support to nouveau prime support 2012-05-31 14:14:00 +01:00
r128
radeon drm/radeon: SI tiling fixes for display 2012-06-20 19:55:56 +01:00
savage
sis drm sis: initialize object_idr 2012-06-16 11:18:53 +01:00
tdfx
ttm drm/ttm: Fix buffer object metadata accounting regression v2 2012-06-12 15:57:47 +01:00
udl drm/udl: only bind to the video devices on the hub. 2012-06-16 11:09:58 +01:00
via drm via: initialize object_idr 2012-06-16 11:18:38 +01:00
vmwgfx drm/vmwgfx: Fix nasty write past alloced memory area 2012-06-01 17:00:20 +01:00
ati_pcigart.c
drm_agpsupport.c
drm_auth.c
drm_buffer.c
drm_bufs.c
drm_cache.c
drm_context.c
drm_crtc_helper.c
drm_crtc.c drm: Use stdint types for consistency 2012-05-29 11:07:09 +01:00
drm_debugfs.c
drm_dma.c
drm_dp_i2c_helper.c
drm_drv.c
drm_edid_load.c
drm_edid_modes.h
drm_edid.c drm/edid: don't return stack garbage from supports_rb 2012-06-21 09:34:13 +01:00
drm_encoder_slave.c
drm_fb_helper.c
drm_fops.c
drm_gem.c
drm_global.c
drm_hashtab.c
drm_info.c
drm_ioc32.c
drm_ioctl.c
drm_irq.c
drm_lock.c
drm_memory.c
drm_mm.c
drm_modes.c
drm_pci.c
drm_platform.c
drm_prime.c
drm_proc.c
drm_scatter.c
drm_stub.c
drm_sysfs.c
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