<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/gpu/drm/amd/display/dc/dc.h, branch linux-5.1.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2019-04-15T04:45:43Z</updated>
<entry>
<title>drm/amd/display: If one stream full updates, full update all planes</title>
<updated>2019-04-15T04:45:43Z</updated>
<author>
<name>David Francis</name>
<email>David.Francis@amd.com</email>
</author>
<published>2019-03-29T17:23:15Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c238bfe0be9ef7420f7669a69e27c8c8f4d8a568'/>
<id>urn:sha1:c238bfe0be9ef7420f7669a69e27c8c8f4d8a568</id>
<content type='text'>
[Why]
On some compositors, with two monitors attached, VT terminal
switch can cause a graphical issue by the following means:

There are two streams, one for each monitor. Each stream has one
plane

current state:
	M1:S1-&gt;P1
	M2:S2-&gt;P2

The user calls for a terminal switch and a commit is made to
change both planes to linear swizzle mode. In atomic check,
a new dc_state is constructed with new planes on each stream

new state:
	M1:S1-&gt;P3
	M2:S2-&gt;P4

In commit tail, each stream is committed, one at a time. The first
stream (S1) updates properly, triggerring a full update and replacing
the state

current state:
	M1:S1-&gt;P3
	M2:S2-&gt;P4

The update for S2 comes in, but dc detects that there is no difference
between the stream and plane in the new and current states, and so
triggers a fast update. The fast update does not program swizzle,
so the second monitor is corrupted

[How]
Add a flag to dc_plane_state that forces full updates

When a stream undergoes a full update, set this flag on all changed
planes, then clear it on the current stream

Subsequent streams will get full updates as a result

Signed-off-by: David Francis &lt;David.Francis@amd.com&gt;
Signed-off-by: Nicholas Kazlauskas &lt;nicholas.kazlauskas@amd.com&gt;
Reviewed-by: Roman Li &lt;Roman.Li@amd.com&gt;
Acked-by: Bhawanpreet Lakha &lt;Bhawanpreet Lakha@amd.com&gt;
Acked-by: Nicholas Kazlauskas &lt;Nicholas.Kazlauskas@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: interface to check if timing can be seamless</title>
<updated>2019-02-06T18:30:44Z</updated>
<author>
<name>Anthony Koo</name>
<email>Anthony.Koo@amd.com</email>
</author>
<published>2019-01-20T06:08:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=68f1a00c23d443c9d940fbd512a195e9e6c08b11'/>
<id>urn:sha1:68f1a00c23d443c9d940fbd512a195e9e6c08b11</id>
<content type='text'>
[Why]
Need to figure out whether a timing we want to commit matches
something that GOP already programmed, in which case
we can decide to some optimizations

[How]
1. Add way to check for DIG FE
2. Add way to check for matching OTG timing
3. Add way to check for matching pixel clock (if possible)
    - Currently only support DP for pixel clock, since it is easy to calc

Signed-off-by: Anthony Koo &lt;Anthony.Koo@amd.com&gt;
Reviewed-by: Aric Cyr &lt;Aric.Cyr@amd.com&gt;
Acked-by: Bhawanpreet Lakha &lt;Bhawanpreet.Lakha@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: 3.2.17</title>
<updated>2019-02-06T18:30:36Z</updated>
<author>
<name>mark mcgarrity</name>
<email>mark.mcgarrity@amd.com</email>
</author>
<published>2019-01-25T19:38:34Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=c00800c46e832ca27f4db489b8c28a56603f8d2c'/>
<id>urn:sha1:c00800c46e832ca27f4db489b8c28a56603f8d2c</id>
<content type='text'>
Signed-off-by: mark mcgarrity &lt;mark.mcgarrity@amd.com&gt;
Reviewed-by: Aric Cyr &lt;Aric.Cyr@amd.com&gt;
Acked-by: Bhawanpreet Lakha &lt;Bhawanpreet.Lakha@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: DC VM Fixes</title>
<updated>2019-02-06T18:30:12Z</updated>
<author>
<name>Eryk Brol</name>
<email>eryk.brol@amd.com</email>
</author>
<published>2019-01-21T19:40:16Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=00fbeb4e2f9eda0ebd57eefdcf25e41958f98fa5'/>
<id>urn:sha1:00fbeb4e2f9eda0ebd57eefdcf25e41958f98fa5</id>
<content type='text'>
[Why]
VM_helper needs to be intialized with the dc struct in order to fix
an unallocated memory issue. System aperture settings should be
initialized to 0 and guarded with a check to make sure vm_config
is valid.

[How]
Allocate and free memory for vm_helper with other dc members.
Check whether the vm_config valid bit is set before initializing
aperture settings.

Signed-off-by: Eryk Brol &lt;eryk.brol@amd.com&gt;
Reviewed-by: Jun Lei &lt;Jun.Lei@amd.com&gt;
Acked-by: Bhawanpreet Lakha &lt;Bhawanpreet.Lakha@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: add a debug flag to force odm combine</title>
<updated>2019-02-06T02:16:23Z</updated>
<author>
<name>Dmytro Laktyushkin</name>
<email>Dmytro.Laktyushkin@amd.com</email>
</author>
<published>2018-12-05T15:52:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=49782c638f6a33992f5c1c69414a7ef5c08a0d31'/>
<id>urn:sha1:49782c638f6a33992f5c1c69414a7ef5c08a0d31</id>
<content type='text'>
Adding a bit vector to allow forcing odm on specific otgs

Signed-off-by: Dmytro Laktyushkin &lt;Dmytro.Laktyushkin@amd.com&gt;
Reviewed-by: Charlene Liu &lt;Charlene.Liu@amd.com&gt;
Acked-by: Bhawanpreet Lakha &lt;Bhawanpreet.Lakha@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: 3.2.16</title>
<updated>2019-02-06T02:16:23Z</updated>
<author>
<name>Steven Chiu</name>
<email>steven.chiu@amd.com</email>
</author>
<published>2019-01-18T20:29:38Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=cf7d98d254e9ffe565fc736e101299cc02bc0aa1'/>
<id>urn:sha1:cf7d98d254e9ffe565fc736e101299cc02bc0aa1</id>
<content type='text'>
Signed-off-by: Steven Chiu &lt;steven.chiu@amd.com&gt;
Reviewed-by: Aric Cyr &lt;Aric.Cyr@amd.com&gt;
Acked-by: Bhawanpreet Lakha &lt;Bhawanpreet.Lakha@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: 3.2.15</title>
<updated>2019-01-25T21:15:37Z</updated>
<author>
<name>Steven Chiu</name>
<email>steven.chiu@amd.com</email>
</author>
<published>2019-01-11T21:55:54Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0f74e4849126266b797186a7433701df777af962'/>
<id>urn:sha1:0f74e4849126266b797186a7433701df777af962</id>
<content type='text'>
Signed-off-by: Steven Chiu &lt;steven.chiu@amd.com&gt;
Reviewed-by: Aric Cyr &lt;Aric.Cyr@amd.com&gt;
Acked-by: Leo Li &lt;sunpeng.li@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: 3.2.14</title>
<updated>2019-01-14T20:42:37Z</updated>
<author>
<name>Steven Chiu</name>
<email>steven.chiu@amd.com</email>
</author>
<published>2019-01-04T15:28:52Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=45a31b01b5f2ba08597fa36a2af797d9062fdeb4'/>
<id>urn:sha1:45a31b01b5f2ba08597fa36a2af797d9062fdeb4</id>
<content type='text'>
Signed-off-by: Steven Chiu &lt;steven.chiu@amd.com&gt;
Reviewed-by: Yongqiang Sun &lt;yongqiang.sun@amd.com&gt;
Acked-by: Leo Li &lt;sunpeng.li@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: 3.2.13</title>
<updated>2019-01-14T20:40:27Z</updated>
<author>
<name>Steven Chiu</name>
<email>steven.chiu@amd.com</email>
</author>
<published>2018-12-14T14:33:30Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=bbba983103842c31ae3013364d90b624df08087f'/>
<id>urn:sha1:bbba983103842c31ae3013364d90b624df08087f</id>
<content type='text'>
Signed-off-by: Steven Chiu &lt;steven.chiu@amd.com&gt;
Reviewed-by: Yongqiang Sun &lt;yongqiang.sun@amd.com&gt;
Acked-by: Leo Li &lt;sunpeng.li@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: Set link rate set if eDP ver &gt;= 1.4.</title>
<updated>2019-01-14T20:40:08Z</updated>
<author>
<name>Derek Lai</name>
<email>Derek.Lai@amd.com</email>
</author>
<published>2018-12-11T08:27:09Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=b03a599b3e1f520e79d3dbf487179bd0d70d4681'/>
<id>urn:sha1:b03a599b3e1f520e79d3dbf487179bd0d70d4681</id>
<content type='text'>
[Why]
If eDP ver &gt;= 1.4,
the Source device must use LINK_RATE_SET.

[How]
Get LINK_RATE_SET by reading DPCD 10h-1fh,
then write DPCD 00115h before link training.

Signed-off-by: Derek Lai &lt;Derek.Lai@amd.com&gt;
Reviewed-by: Tony Cheng &lt;Tony.Cheng@amd.com&gt;
Acked-by: Leo Li &lt;sunpeng.li@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
</feed>
