<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-dev/drivers/gpu/drm/amd/display/dc/dcn31, branch linus/master</title>
<subtitle>Linux kernel development work - see feature branches</subtitle>
<id>https://git.zx2c4.com/linux-dev/atom/drivers/gpu/drm/amd/display/dc/dcn31?h=linus%2Fmaster</id>
<link rel='self' href='https://git.zx2c4.com/linux-dev/atom/drivers/gpu/drm/amd/display/dc/dcn31?h=linus%2Fmaster'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/'/>
<updated>2022-06-01T19:56:48Z</updated>
<entry>
<title>drm/amd/display: Don't clear ref_dtbclk value</title>
<updated>2022-06-01T19:56:48Z</updated>
<author>
<name>Alvin</name>
<email>Alvin.Lee2@amd.com</email>
</author>
<published>2022-05-12T20:49:16Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=f0ad66f42a3d914ac5f9972731ec5bc97f35002d'/>
<id>urn:sha1:f0ad66f42a3d914ac5f9972731ec5bc97f35002d</id>
<content type='text'>
[Description]
ref_dtbclk value is assigned in clk_mgr_construct,
but the clks struct is cleared in init_clocks.
Make sure to restore the value or we will get
0 value for ref_dtbclk in DCN31.

Reviewed-by: Chris Park &lt;Chris.Park@amd.com&gt;
Acked-by: Jasdeep Dhillon &lt;jdhillon@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Alvin Lee &lt;Alvin.Lee2@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: Fix DMUB outbox trace in S4 (#4465)</title>
<updated>2022-06-01T19:56:48Z</updated>
<author>
<name>Hung, Cruise</name>
<email>Cruise.Hung@amd.com</email>
</author>
<published>2022-05-13T01:16:42Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=6ecf9773a5030aa4932096754bacff20e1b944b8'/>
<id>urn:sha1:6ecf9773a5030aa4932096754bacff20e1b944b8</id>
<content type='text'>
[Why]
DMUB Outbox0 read/write pointer not sync after resumed from S4.
And that caused old traces were sent to outbox.

[How]
Disable DMUB Outbox0 interrupt
and clear DMUB Outbox0 read/write pointer when resumes from S4.
And then enable Outbox0 interrupt before starts DMCUB.

Reviewed-by: Nicholas Kazlauskas &lt;Nicholas.Kazlauskas@amd.com&gt;
Acked-by: Jasdeep Dhillon &lt;jdhillon@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Cruise Hung &lt;Cruise.Hung@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: revert Blank eDP on disable/enable drv</title>
<updated>2022-06-01T19:56:48Z</updated>
<author>
<name>Leung, Martin</name>
<email>Martin.Leung@amd.com</email>
</author>
<published>2022-05-10T16:27:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=0ec744084793db817990424cc3cc9da63f665f3f'/>
<id>urn:sha1:0ec744084793db817990424cc3cc9da63f665f3f</id>
<content type='text'>
why and how:
Revert this change. It was causing a black screen with certain blocks

Reviewed-by: George Shen &lt;George.Shen@amd.com&gt;
Acked-by: Jasdeep Dhillon &lt;jdhillon@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Leung, Martin &lt;Martin.Leung@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: Read Golden Settings Table from VBIOS</title>
<updated>2022-06-01T19:56:48Z</updated>
<author>
<name>Sherry Wang</name>
<email>YAO.WANG1@amd.com</email>
</author>
<published>2022-05-10T10:42:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=4b81dd2cc6f4f4e8cea0ed6ee8d5193a8ae14a72'/>
<id>urn:sha1:4b81dd2cc6f4f4e8cea0ed6ee8d5193a8ae14a72</id>
<content type='text'>
[Why]
Dmub read AUX_DPHY_RX_CONTROL0 from Golden Setting Table,
but driver will set it to default value 0x103d1110, which
causes issue in some case

[How]
Remove the driver code, use the value set by dmub in
dp_aux_init

Reviewed-by: Nicholas Kazlauskas &lt;Nicholas.Kazlauskas@amd.com&gt;
Acked-by: Jasdeep Dhillon &lt;jdhillon@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Sherry Wang &lt;YAO.WANG1@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: Move FPU associated DCN30 code to DML folder</title>
<updated>2022-05-26T18:56:31Z</updated>
<author>
<name>Jasdeep Dhillon</name>
<email>jdhillon@amd.com</email>
</author>
<published>2022-05-06T17:03:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=e4b0eac3e6242abf5f5ebcffdeb852e7ffa1c3d0'/>
<id>urn:sha1:e4b0eac3e6242abf5f5ebcffdeb852e7ffa1c3d0</id>
<content type='text'>
[why &amp; how]
As part of the FPU isolation work documented in
https://patchwork.freedesktop.org/series/93042/, isolate
code that uses FPU in DCN30 to DML, where all FPU code
should locate.

Reviewed-by: Rodrigo Siqueira &lt;Rodrigo.Siqueira@amd.com&gt;
Acked-by: Qingqing Zhuo &lt;qingqing.zhuo@amd.com&gt;
Signed-off-by: Jasdeep Dhillon &lt;jdhillon@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>Revert "drm/amd/display: Fix DCN3 B0 DP Alt Mapping"</title>
<updated>2022-05-10T21:53:13Z</updated>
<author>
<name>Stylon Wang</name>
<email>stylon.wang@amd.com</email>
</author>
<published>2022-05-04T10:09:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=1039188806d4cfdf9c412bb4ddb51b4d8cd15478'/>
<id>urn:sha1:1039188806d4cfdf9c412bb4ddb51b4d8cd15478</id>
<content type='text'>
This reverts commit 4b7786d87fb3adf3e534c4f1e4f824d8700b786b.

Commit 4b7786d87fb3 ("drm/amd/display: Fix DCN3 B0 DP Alt Mapping")
is causing 2nd USB-C display not lighting up.
Phy id remapping is done differently than is assumed in this
patch.

Signed-off-by: Stylon Wang &lt;stylon.wang@amd.com&gt;
Reviewed-by: Nicholas Kazlauskas &lt;Nicholas.Kazlauskas@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: protect remaining FPU-code calls on dcn3.1.x</title>
<updated>2022-04-28T21:44:02Z</updated>
<author>
<name>Melissa Wen</name>
<email>mwen@igalia.com</email>
</author>
<published>2022-03-30T23:02:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=7324d02a6545414fff3bcd2c6e95b9e1041a327e'/>
<id>urn:sha1:7324d02a6545414fff3bcd2c6e95b9e1041a327e</id>
<content type='text'>
From [1], I realized two other calls to dcn30 code are associated with
FPU operations and are not protected by DC_FP_* macros:
* dcn30_populate_dml_writeback_from_context()
* dcn30_set_mcif_arb_params()

So, since FPU-associated code is not fully isolated in dcn30, and
dcn3.1.x reuses them, let's wrap their calls properly.

Note: this patch complements the fix from [1].

[1] https://lore.kernel.org/amd-gfx/20220329082957.1662655-1-chandan.vurdigerenataraj@amd.com/

Reviewed-by: Rodrigo Siqueira &lt;Rodrigo.Siqueira@amd.com&gt;
Signed-off-by: Melissa Wen &lt;mwen@igalia.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amd/display: Don't pass HostVM by default on DCN3.1</title>
<updated>2022-04-25T21:10:36Z</updated>
<author>
<name>Michael Strauss</name>
<email>michael.strauss@amd.com</email>
</author>
<published>2022-04-05T19:56:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=4a0caac06a4c587e56d89bd2fabfc0d33eb4fcb9'/>
<id>urn:sha1:4a0caac06a4c587e56d89bd2fabfc0d33eb4fcb9</id>
<content type='text'>
[WHY]
Roll back previous change to stop passing this value by default, instead
add a debug flag to override to previous behaviour (or force HostVM calcs)

Reviewed-by: Nicholas Kazlauskas &lt;Nicholas.Kazlauskas@amd.com&gt;
Acked-by: Tom Chung &lt;chiahsuan.chung@amd.com&gt;
Signed-off-by: Michael Strauss &lt;michael.strauss@amd.com&gt;
Tested-by: Daniel Wheeler &lt;daniel.wheeler@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu/display: make hubp31_program_extended_blank static</title>
<updated>2022-04-21T19:59:57Z</updated>
<author>
<name>Alex Deucher</name>
<email>alexander.deucher@amd.com</email>
</author>
<published>2022-04-21T14:09:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=72f05e3b96b25ebbc572938b9fd8a1e930834eb2'/>
<id>urn:sha1:72f05e3b96b25ebbc572938b9fd8a1e930834eb2</id>
<content type='text'>
It's not used outside of dcn31_hubp.c.

Reviewed-by: Harry Wentland &lt;harry.wentland@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>Revert "drm/amd/display: Pass HostVM enable flag into DCN3.1 DML"</title>
<updated>2022-04-14T19:27:15Z</updated>
<author>
<name>Rodrigo Siqueira</name>
<email>Rodrigo.Siqueira@amd.com</email>
</author>
<published>2022-04-12T18:32:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/linux-dev/commit/?id=9e12b5947bbaa74db32e24d77ebf3bd71015970c'/>
<id>urn:sha1:9e12b5947bbaa74db32e24d77ebf3bd71015970c</id>
<content type='text'>
This reverts commit 863fa85e6a01c8b239009825dd9de1f64d7d020a.

While we were testing DCN3.1 with a hub, we noticed that only one of 2
connected displays lights up when using some specific display
resolution. In summary, this was the setup:

1. Displays:
 * Sharp LQ156M1JW26 (eDP): 1080@240
 * BENQ SW320 (DP): 4k@60
 * BENQ EX3203R (DP): 4k@60
2. Hub: Club3D CSV-7300
3. ASIC: DCN3.1

After bisecting this issue, we figured out the commit mentioned above
introduced this issue. We are investigating why this patch introduced
this regression, but we need to revert it for now.

Cc: Harry Wentland &lt;harry.wentland@amd.com&gt;
Cc: Mark Broadworth &lt;Mark.Broadworth@amd.com&gt;
Cc: Michael Strauss &lt;michael.strauss@amd.com&gt;
Acked-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Rodrigo Siqueira &lt;Rodrigo.Siqueira@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
</feed>
