<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu/drm/Makefile, branch v3.11</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu/drm/Makefile?h=v3.11</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu/drm/Makefile?h=v3.11'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-06-27T00:08:04Z</updated>
<entry>
<title>drm: Renesas R-Car Display Unit DRM driver</title>
<updated>2013-06-27T00:08:04Z</updated>
<author>
<name>Laurent Pinchart</name>
<email>laurent.pinchart+renesas@ideasonboard.com</email>
</author>
<published>2013-06-19T11:54:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4bf8e1962f91eed5dbee168d2348983dda0a518f'/>
<id>urn:sha1:4bf8e1962f91eed5dbee168d2348983dda0a518f</id>
<content type='text'>
The R-Car Display Unit (DU) DRM driver supports both superposition
processors and all eight planes in RGB and YUV formats with alpha
blending.

Only VGA and LVDS encoders and connectors are currently supported.

Signed-off-by: Laurent Pinchart &lt;laurent.pinchart+renesas@ideasonboard.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'v3.10-rc2' into drm-intel-next-queued</title>
<updated>2013-05-21T07:52:16Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2013-05-21T07:52:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e1b73cba13a0cc68dd4f746eced15bd6bb24cda4'/>
<id>urn:sha1:e1b73cba13a0cc68dd4f746eced15bd6bb24cda4</id>
<content type='text'>
Backmerge Linux 3.10-rc2 since the various (rather trivial) conflicts
grew a bit out of hand. intel_dp.c has the only real functional
conflict since the logic changed while dev_priv-&gt;edp.bpp was moved
around.

Also squash in a whitespace fixup from Ben Widawsky for
i915_gem_gtt.c, git seems to do something pretty strange in there
(which I don't fully understand tbh).

Conflicts:
	drivers/gpu/drm/i915/i915_reg.h
	drivers/gpu/drm/i915/intel_dp.c

Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm: Add struct drm_rect and assorted utility functions</title>
<updated>2013-04-30T20:19:08Z</updated>
<author>
<name>Ville Syrjälä</name>
<email>ville.syrjala@linux.intel.com</email>
</author>
<published>2013-04-24T15:52:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3512f976d252bd5d07d04e9e157f0cd210c959a0'/>
<id>urn:sha1:3512f976d252bd5d07d04e9e157f0cd210c959a0</id>
<content type='text'>
struct drm_rect represents a simple rectangle. The utility
functions are there to help driver writers.

v2: Moved the region stuff into its own file, made the smaller funcs
    static inline, used 64bit maths in the scaled clipping function to
    avoid overflows (instead it will saturate to INT_MIN or INT_MAX).
v3: Renamed drm_region to drm_rect, drm_region_clip to
    drm_rect_intersect, and drm_region_subsample to drm_rect_downscale.
v4: Renamed some function parameters, improve kernel-doc comments a bit,
    and actually generate documentation for drm_rect.[ch].
v5: s/RETUTRNS/RETURNS/

Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Ville Syrjälä &lt;ville.syrjala@linux.intel.com&gt;
Acked-by: Dave Airlie &lt;airlied@gmail.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm/tegra: Move drm to live under host1x</title>
<updated>2013-04-22T10:39:11Z</updated>
<author>
<name>Terje Bergstrom</name>
<email>tbergstrom@nvidia.com</email>
</author>
<published>2013-03-22T14:34:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4231c6b01af9f0f3eeca4b8d0d87125d78233b41'/>
<id>urn:sha1:4231c6b01af9f0f3eeca4b8d0d87125d78233b41</id>
<content type='text'>
Make drm part of host1x driver.

Signed-off-by: Arto Merilainen &lt;amerilainen@nvidia.com&gt;
Signed-off-by: Terje Bergstrom &lt;tbergstrom@nvidia.com&gt;
Reviewed-by: Thierry Reding &lt;thierry.reding@avionic-design.de&gt;
Tested-by: Thierry Reding &lt;thierry.reding@avionic-design.de&gt;
Tested-by: Erik Faye-Lund &lt;kusmabite@gmail.com&gt;
Signed-off-by: Thierry Reding &lt;thierry.reding@avionic-design.de&gt;
</content>
</entry>
<entry>
<title>drm: add new QXL driver. (v1.4)</title>
<updated>2013-04-12T03:51:07Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@gmail.com</email>
</author>
<published>2013-02-25T04:47:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f64122c1f6ade301585569863b4b3b18f6e4e332'/>
<id>urn:sha1:f64122c1f6ade301585569863b4b3b18f6e4e332</id>
<content type='text'>
QXL is a paravirtual graphics device used by the Spice virtual desktop
interface.

The drivers uses GEM and TTM to manage memory, the qxl hw fencing however
is quite different than normal TTM expects, we have to keep track of a number
of non-linear fence ids per bo that we need to have released by the hardware.

The releases are freed from a workqueue that wakes up and processes the
release ring.

releases are suballocated from a BO, there are 3 release categories, drawables,
surfaces and cursor cmds. The hw also has 3 rings for commands, cursor and release handling.

The hardware also have a surface id tracking mechnaism and the driver encapsulates it completely inside the kernel, userspace never sees the actual hw surface
ids.

This requires a newer version of the QXL userspace driver, so shouldn't be
enabled until that has been placed into your distro of choice.

Authors: Dave Airlie, Alon Levy

v1.1: fixup some issues in the ioctl interface with padding
v1.2: add module device table
v1.3: fix nomodeset, fbcon leak, dumb bo create, release ring irq,
      don't try flush release ring (broken hw), fix -modesetting.
v1.4: fbcon cpu usage reduction + suitable accel flags.

Signed-off-by: Alon Levy &lt;alevy@redhat.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'tilcdc-next' of git://people.freedesktop.org/~robclark/linux into drm-next</title>
<updated>2013-02-20T23:31:47Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2013-02-20T23:31:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ca18e1426bb2db987b67030256477c9571aebd09'/>
<id>urn:sha1:ca18e1426bb2db987b67030256477c9571aebd09</id>
<content type='text'>
KMS driver for TI LCD controller

* 'tilcdc-next' of git://people.freedesktop.org/~robclark/linux:
  drm/tilcdc: add support for LCD panels (v5)
  drm/tilcdc: add encoder slave (v2)
  drm/i2c: nxp-tda998x (v3)
  drm/tilcdc: add TI LCD Controller DRM driver (v4)
  drm/nouveau: use i2c encoder helper wrappers
  drm: i2c encoder helper wrappers
  drm/cma: add debugfs helpers
  drm: small fix in drm_send_vblank_event()
  drm: Don't set the plane-&gt;fb to NULL on successfull set_plane
  drm/cma-helper: fixup compilation

Conflicts:
	drivers/gpu/drm/Kconfig
	drivers/gpu/drm/Makefile
	drivers/gpu/drm/drm_fb_cma_helper.c
</content>
</entry>
<entry>
<title>drm/tilcdc: add TI LCD Controller DRM driver (v4)</title>
<updated>2013-02-19T22:57:44Z</updated>
<author>
<name>Rob Clark</name>
<email>robdclark@gmail.com</email>
</author>
<published>2013-01-08T21:04:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=16ea975eac671fa40a78594a116a44fef8e3f4a9'/>
<id>urn:sha1:16ea975eac671fa40a78594a116a44fef8e3f4a9</id>
<content type='text'>
A simple DRM/KMS driver for the TI LCD Controller found in various
smaller TI parts (AM33xx, OMAPL138, etc).  This driver uses the
CMA helpers.  Currently only the TFP410 DVI encoder is supported
(tested with beaglebone + DVI cape).  There are also various LCD
displays, for which support can be added (as I get hw to test on),
and an external i2c HDMI encoder found on some boards.

The display controller supports a single CRTC.  And the encoder+
connector are split out into sub-devices.  Depending on which LCD
or external encoder is actually present, the appropriate output
module(s) will be loaded.

v1: original
v2: fix fb refcnting and few other cleanups
v3: get +/- vsync/hsync from timings rather than panel-info, add
    option DT max-bandwidth field so driver doesn't attempt to
    pick a display mode with too high memory bandwidth, and other
    small cleanups
v4: remove some unneeded stuff from panel-info struct, properly
    set high bits for hfp/hsw/hbp for rev 2, add DT bindings docs

Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Tested-by: Koen Kooi &lt;koen@dominion.thruhere.net&gt;
</content>
</entry>
<entry>
<title>drm/omap: move out of staging</title>
<updated>2013-02-16T22:38:06Z</updated>
<author>
<name>Rob Clark</name>
<email>robdclark@gmail.com</email>
</author>
<published>2013-02-11T17:43:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8bb0daffb0b8e45188066255b4203446eae181f1'/>
<id>urn:sha1:8bb0daffb0b8e45188066255b4203446eae181f1</id>
<content type='text'>
Now that the omapdss interface has been reworked so that omapdrm can use
dispc directly, we have been able to fix the remaining functional kms
issues with omapdrm.  And in the mean time the PM sequencing and many
other of that open issues have been solved.  So I think it makes sense
to finally move omapdrm out of staging.

Signed-off-by: Rob Clark &lt;robdclark@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm: only build ati_pcigart if PCI enabled</title>
<updated>2012-11-28T10:12:29Z</updated>
<author>
<name>James Hogan</name>
<email>james.hogan@imgtec.com</email>
</author>
<published>2012-11-23T11:12:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dff98e529e06fb1c801ba26953299b3390bdd34d'/>
<id>urn:sha1:dff98e529e06fb1c801ba26953299b3390bdd34d</id>
<content type='text'>
Prevent ati_pcigart.c being built unless PCI is enabled. The exported
functions in this file are only used by drivers which depend on PCI
(namely r128 and radeon), and it tries to use PCI specific functions
(pci_unmap_page, pci_map_page, and pci_dma_mapping_error) that cause
compiler errors when PCI is disabled.

Signed-off-by: James Hogan &lt;james.hogan@imgtec.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Add NVIDIA Tegra20 support</title>
<updated>2012-11-20T05:43:41Z</updated>
<author>
<name>Thierry Reding</name>
<email>thierry.reding@avionic-design.de</email>
</author>
<published>2012-11-15T21:28:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d8f4a9eda006788d8054b8500d9eb5b6efcd8755'/>
<id>urn:sha1:d8f4a9eda006788d8054b8500d9eb5b6efcd8755</id>
<content type='text'>
This commit adds a KMS driver for the Tegra20 SoC. This includes basic
support for host1x and the two display controllers found on the Tegra20
SoC. Each display controller can drive a separate RGB/LVDS output.

Signed-off-by: Thierry Reding &lt;thierry.reding@avionic-design.de&gt;
Tested-by: Stephen Warren &lt;swarren@nvidia.com&gt;
Acked-by: Mark Zhang &lt;markz@nvidia.com&gt;
Reviewed-by: Mark Zhang &lt;markz@nvidia.com&gt;
Tested-by: Mark Zhang &lt;markz@nvidia.com&gt;
Tested-and-acked-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Acked-by: Terje Bergstrom &lt;tbergstrom@nvidia.com&gt;
Tested-by: Terje Bergstrom &lt;tbergstrom@nvidia.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
</feed>
