<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu/drm, branch v3.15.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu/drm?h=v3.15.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu/drm?h=v3.15.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-06-02T08:57:04Z</updated>
<entry>
<title>drm/radeon: use the CP DMA on CIK</title>
<updated>2014-06-02T08:57:04Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-05-30T15:52:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=91b0275c0ecd1870c5f8bfb73e2da2d6c29414b3'/>
<id>urn:sha1:91b0275c0ecd1870c5f8bfb73e2da2d6c29414b3</id>
<content type='text'>
The SDMA sometimes doesn't seem to work reliable.

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Cc: stable@vger.kernel.org
</content>
</entry>
<entry>
<title>drm/radeon: sync page table updates</title>
<updated>2014-06-02T08:56:21Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-05-30T13:21:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=37903b5e08ec9a481a811287b4db3dfe61f6e31f'/>
<id>urn:sha1:37903b5e08ec9a481a811287b4db3dfe61f6e31f</id>
<content type='text'>
Only necessary if we don't use the same engine for buffer moves and table updates.

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon: fix vm buffer size estimation</title>
<updated>2014-06-02T08:54:02Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-05-31T18:38:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2f93dc32b09a2c97f6f33bafe4c6bdcec7cae774'/>
<id>urn:sha1:2f93dc32b09a2c97f6f33bafe4c6bdcec7cae774</id>
<content type='text'>
Only relevant if we got VM_BLOCK_SIZE&gt;9, but better save than sorry.

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/crtc-helper: skip locking checks in panicking path</title>
<updated>2014-06-02T03:36:52Z</updated>
<author>
<name>Sergei Antonov</name>
<email>saproj@gmail.com</email>
</author>
<published>2014-05-11T22:30:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ba6f582606655754d9dfbfc9dffe75dcf806f1dd'/>
<id>urn:sha1:ba6f582606655754d9dfbfc9dffe75dcf806f1dd</id>
<content type='text'>
Skip locking checks in drm_helper_*_in_use() if they are called in panicking
path. See similar code in drm_warn_on_modeset_not_all_locked().

After panic information has been output, these WARN_ONs go off outputing a lot
of lines and scrolling the panic information out of the screen. Here is a
partial call trace showing how execution reaches them:

? drm_helper_crtc_in_use()
? __drm_helper_disable_unused_functions()
? several *_set_config functions
? drm_fb_helper_restore_fbdev_mode()

Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Sergei Antonov &lt;saproj@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon/dpm: resume fixes for some systems</title>
<updated>2014-06-02T03:33:03Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexdeucher@gmail.com</email>
</author>
<published>2014-05-30T16:40:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3640da2faa952a2e9439a254c1ce76033ca0a6dc'/>
<id>urn:sha1:3640da2faa952a2e9439a254c1ce76033ca0a6dc</id>
<content type='text'>
Setting the power state prior to restoring the display
hardware leads to blank screens on some systems.  Drop
the power state set from dpm resume.  The power state
will get set as part of the mode set sequence.  Also
add an explicit power state set after mode set resume
to cover PX and headless systems.

bug:
https://bugzilla.kernel.org/show_bug.cgi?id=76761

Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon: Resume fbcon last</title>
<updated>2014-05-30T23:19:51Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2014-05-30T14:41:23Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=18ee37a485653aa635cfab9a3710e9bcf5fbca01'/>
<id>urn:sha1:18ee37a485653aa635cfab9a3710e9bcf5fbca01</id>
<content type='text'>
So a few people complained that

commit 177cf92de4aa97ec1435987e91696ed8b5023130
Author: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Date:   Tue Apr 1 22:14:59 2014 +0200

    drm/crtc-helpers: fix dpms on logic

which was merged into 3.15-rc1, broke resume on radeons. Strangely git
bisect lead everyone to

commit 25f397a429dfa43f22c278d0119a60a343aa568f
Author: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Date:   Fri Jul 19 18:57:11 2013 +0200

    drm/crtc-helper: explicit DPMS on after modeset

which was merged long ago and actually part of 3.14.

Digging deeper I've noticed (again) that the call to
drm_helper_resume_force_mode in the radeon resume handlers was a no-op
previously because everything gets shut down on suspend. radeon does
this with explicit calls to drm_helper_connector_dpms with DPMS_OFF.
But with 177c we now force the dpms state to ON, so suddenly
resume_force_mode actually forced the crtcs back on.

This is the intention of the change after all, the problem is that
radeon resumes the fbdev console layer _before_ restoring the display,
through calling fb_set_suspend. And fbcon does an immediate -&gt;set_par,
which in turn causes the same forced mode restore to happen.

Two concurrent modeset operations didn't lead to happiness. Fix this
by delaying the fbcon resume until the end of the readeon resum
functions.

v2: Fix up a bit of the spelling fail.

References: https://lkml.org/lkml/2014/5/29/1043
References: https://lkml.org/lkml/2014/5/2/388
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=74751
Tested-by: Ken Moffat &lt;zarniwhoop@ntlworld.com&gt;
Cc: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Cc: Ken Moffat &lt;zarniwhoop@ntlworld.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Signed-off-by: Dave Airlie &lt;airlied@gmail.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon: only allocate necessary size for vm bo list</title>
<updated>2014-05-30T12:21:54Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-05-28T10:24:17Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7d95f6cc4ef73572a43d4a0a1907a13ace17a62a'/>
<id>urn:sha1:7d95f6cc4ef73572a43d4a0a1907a13ace17a62a</id>
<content type='text'>
No need to always allocate the theoretical maximum here.

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/radeon: don't allow RADEON_GEM_DOMAIN_CPU for command submission</title>
<updated>2014-05-30T12:21:49Z</updated>
<author>
<name>Marek Olšák</name>
<email>marek.olsak@amd.com</email>
</author>
<published>2014-05-27T00:56:36Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ec65da385d46f63740c1c9230b891a6dcbd64c71'/>
<id>urn:sha1:ec65da385d46f63740c1c9230b891a6dcbd64c71</id>
<content type='text'>
It hangs the hardware.

Signed-off-by: Marek Olšák &lt;marek.olsak@amd.com&gt;
Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Cc: stable@vger.kernel.org
</content>
</entry>
<entry>
<title>drm/radeon: avoid crash if VM command submission isn't available</title>
<updated>2014-05-30T12:21:44Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-05-21T15:43:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=60a445405a1731bac2279eab354173c9c3156747'/>
<id>urn:sha1:60a445405a1731bac2279eab354173c9c3156747</id>
<content type='text'>
Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
CC: stable@vger.kernel.org
</content>
</entry>
<entry>
<title>drm/radeon: lower the ref * post PLL maximum once more</title>
<updated>2014-05-30T12:13:30Z</updated>
<author>
<name>Christian König</name>
<email>christian.koenig@amd.com</email>
</author>
<published>2014-05-21T13:25:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4b21ce1b4b5d262e7d4656b8ececc891fc3cb806'/>
<id>urn:sha1:4b21ce1b4b5d262e7d4656b8ececc891fc3cb806</id>
<content type='text'>
Let's be conservative and use 100 here until we find something better.

Bugs: https://bugzilla.kernel.org/show_bug.cgi?id=75241

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
</content>
</entry>
</feed>
