<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu, branch v3.14.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu?h=v3.14.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu?h=v3.14.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-05-13T11:32:57Z</updated>
<entry>
<title>drm: bochs: add power management support</title>
<updated>2014-05-13T11:32:57Z</updated>
<author>
<name>Gerd Hoffmann</name>
<email>kraxel@redhat.com</email>
</author>
<published>2014-04-14T09:34:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=79f69c3a5f4ff4e9432086eab9f2af958f9eafb2'/>
<id>urn:sha1:79f69c3a5f4ff4e9432086eab9f2af958f9eafb2</id>
<content type='text'>
commit b8ccd70f1363f7d4e49219dbc46ec973a14f49cd upstream.

bochs kms driver lacks power management support, thus
the vga display doesn't work any more after S3 resume.

Fix this by adding suspend and resume functions.

Signed-off-by: Gerd Hoffmann &lt;kraxel@redhat.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm: cirrus: add power management support</title>
<updated>2014-05-13T11:32:57Z</updated>
<author>
<name>Gerd Hoffmann</name>
<email>kraxel@redhat.com</email>
</author>
<published>2014-04-14T09:34:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6bf8e2973f5c92510f8a6724a07d8713853ecb43'/>
<id>urn:sha1:6bf8e2973f5c92510f8a6724a07d8713853ecb43</id>
<content type='text'>
commit 2f1e800799bf478494cec3573cd63eb34ca89c9d upstream.

cirrus kms driver lacks power management support, thus
the vga display doesn't work any more after S3 resume.

Fix this by adding suspend and resume functions.
Also make the mode_set function unblank the screen.

Signed-off-by: Gerd Hoffmann &lt;kraxel@redhat.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Skip intel_crt_init for Dell XPS 8700</title>
<updated>2014-05-13T11:32:55Z</updated>
<author>
<name>Giacomo Comes</name>
<email>comes@naic.edu</email>
</author>
<published>2014-04-03T18:13:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e07b5528f1f4adf101968d8c730201fe38b9b514'/>
<id>urn:sha1:e07b5528f1f4adf101968d8c730201fe38b9b514</id>
<content type='text'>
commit 10b6ee4a87811a110cb01eaca01eb04da6801baf upstream.

The Dell XPS 8700 has a onboard Display port and HDMI port and no VGA port.
The call intel_crt_init freeze the machine, so skip such call.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73559
Signed-off-by: Giacomo Comes &lt;comes at naic.edu&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>DRM: armada: fix corruption while loading cursors</title>
<updated>2014-05-06T14:59:29Z</updated>
<author>
<name>Russell King</name>
<email>rmk+kernel@arm.linux.org.uk</email>
</author>
<published>2014-04-07T11:00:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5a8662c721425479147eb22de81d42e1f3bfc551'/>
<id>urn:sha1:5a8662c721425479147eb22de81d42e1f3bfc551</id>
<content type='text'>
commit c39b06951f1dc2e384650288676c5b7dcc0ec92c upstream.

Loading cursors to the LCD controller's SRAM can be corrupted when the
configured pixel clock is relatively slow.  This seems to be caused
when we write back-to-back to the SRAM registers.

There doesn't appear to be any status register we can read to check
when an access has completed.

Inserting a dummy read between the writes appears to fix the problem.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/i915: Undo gtt scratch pte unmapping again</title>
<updated>2014-03-28T02:33:50Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2014-03-26T19:10:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8ee661b505613ef2747b350ca2871a31b3781bee'/>
<id>urn:sha1:8ee661b505613ef2747b350ca2871a31b3781bee</id>
<content type='text'>
It apparently blows up on some machines. This functionally reverts

commit 828c79087cec61eaf4c76bb32c222fbe35ac3930
Author: Ben Widawsky &lt;benjamin.widawsky@intel.com&gt;
Date:   Wed Oct 16 09:21:30 2013 -0700

    drm/i915: Disable GGTT PTEs on GEN6+ suspend

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=64841
Reported-and-Tested-by: Brad  Jackson &lt;bjackson0971@gmail.com&gt;
Cc: stable@vger.kernel.org
Cc: Takashi Iwai &lt;tiwai@suse.de&gt;
Cc: Paulo Zanoni &lt;paulo.r.zanoni@intel.com&gt;
Cc: Todd Previte &lt;tprevite@gmail.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon: fix runtime suspend breaking secondary GPUs</title>
<updated>2014-03-28T02:27:25Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2014-03-27T02:31:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c53c6beddc0ebb6feb5d64488c2c0cd23dd7f43d'/>
<id>urn:sha1:c53c6beddc0ebb6feb5d64488c2c0cd23dd7f43d</id>
<content type='text'>
Same fix as for nouveau, when we fail with EINVAL, subsequent
gets fail hard, causing the device not to open.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau: fail runtime pm properly.</title>
<updated>2014-03-27T02:20:37Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2014-03-26T04:09:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=adbbdbac04f093c0abf946b1e93e4e5291808491'/>
<id>urn:sha1:adbbdbac04f093c0abf946b1e93e4e5291808491</id>
<content type='text'>
If we were on a non-optimus device, we'd return -EINVAL, this would
lead to the over engineered runtime pm system to go into an error
state, subsequent get_sync's would fail, so we'd never be able
to open the device again.

(like really get_sync shouldn't fail if the device isn't powered
down).

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/udl: take reference to device struct for dma-bufs</title>
<updated>2014-03-27T02:19:50Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2014-03-25T04:38:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=347cf10aed1657a2b385a95f92763a67062c5ad3'/>
<id>urn:sha1:347cf10aed1657a2b385a95f92763a67062c5ad3</id>
<content type='text'>
this stops the device from being deleted before all the dma-bufs
on it are freed, this fixes an oops when you unplug a udl device while
it has imported a buffer from another device.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'exynos-drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-fixes</title>
<updated>2014-03-20T03:20:00Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2014-03-20T03:20:00Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=004e5cf743086990e5fc04a14437b3966d7fa9a2'/>
<id>urn:sha1:004e5cf743086990e5fc04a14437b3966d7fa9a2</id>
<content type='text'>
 Just fixed resource release issue at open fail.

* 'exynos-drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos:
  drm/exynos: Fix (more) freeing issues in exynos_drm_drv.c
</content>
</entry>
<entry>
<title>drm/exynos: Fix (more) freeing issues in exynos_drm_drv.c</title>
<updated>2014-03-20T02:42:24Z</updated>
<author>
<name>Daniel Kurtz</name>
<email>djkurtz@chromium.org</email>
</author>
<published>2014-03-17T03:28:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=85d898bf8f638b7a23af95dc7d32b4a72c178637'/>
<id>urn:sha1:85d898bf8f638b7a23af95dc7d32b4a72c178637</id>
<content type='text'>
The following commit [0] fixed a use-after-free, but left the subdrv open
in the error path.

[0] commit 6ca605f7c70895a35737435f17ae9cc5e36f1466
drm/exynos: Fix freeing issues in exynos_drm_drv.c

Signed-off-by: Daniel Kurtz &lt;djkurtz@chromium.org&gt;
Acked-by: Sachin Kamat &lt;sachin.kamat@linaro.org&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
</feed>
