<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/amd/powerplay, branch linux-5.3.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.3.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.3.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2019-12-04T21:33:54Z</updated>
<entry>
<title>drm/amd/swSMU: fix smu workload bit map error</title>
<updated>2019-12-04T21:33:54Z</updated>
<author>
<name>Kevin Wang</name>
</author>
<published>2019-11-05T10:16:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=583dafc2d91b6f17931595824aa397536fccec5d'/>
<id>urn:sha1:583dafc2d91b6f17931595824aa397536fccec5d</id>
<content type='text'>
[ Upstream commit 38264de0dce80d223f358ce47512378fae0de586 ]

fix workload bit (WORKLOAD_PPLIB_COMPUTE_BIT) map error
on vega20 and navi asic.

fix commit:
drm/amd/powerplay: add function get_workload_type_map for swsmu

Signed-off-by: Kevin Wang &lt;kevin1.wang@amd.com&gt;
Reviewed-by: Kenneth Feng &lt;kenneth.feng@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>drm/amd/powerplay: issue no PPSMC_MSG_GetCurrPkgPwr on unsupported ASICs</title>
<updated>2019-11-29T09:07:49Z</updated>
<author>
<name>Evan Quan</name>
</author>
<published>2019-11-14T07:30:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d20b461956c8422e2ac5e4b7f4ffbdff7ac457fd'/>
<id>urn:sha1:d20b461956c8422e2ac5e4b7f4ffbdff7ac457fd</id>
<content type='text'>
commit 355d991cb6ff6ae76b5e28b8edae144124c730e4 upstream.

Otherwise, the error message prompted will confuse user.

Signed-off-by: Evan Quan &lt;evan.quan@amd.com&gt;
Acked-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/amdgpu/powerplay/vega10: allow undervolting in p7</title>
<updated>2019-11-06T12:09:23Z</updated>
<author>
<name>Pelle van Gils</name>
</author>
<published>2019-10-24T14:04:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=99c996d426dc9905af1f3af7f03b5a70abd9d83f'/>
<id>urn:sha1:99c996d426dc9905af1f3af7f03b5a70abd9d83f</id>
<content type='text'>
commit e6f4e274c1e52d1f0bfe293fb44ddf59de6c0374 upstream.

The vega10_odn_update_soc_table() function does not allow the SCLK
dependent voltage to be set for power-state 7 to a value below the default
in pptable. Change the for-loop condition to allow undervolting in the
highest state.

Bug: https://bugzilla.kernel.org/show_bug.cgi?id=205277
Signed-off-by: Pelle van Gils &lt;pelle@vangils.xyz&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/amd/powerplay: change metrics update period from 1ms to 100ms</title>
<updated>2019-10-11T16:36:15Z</updated>
<author>
<name>Kevin Wang</name>
</author>
<published>2019-09-26T08:16:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6d86d2561272ef276c46723d12adf679dd934352'/>
<id>urn:sha1:6d86d2561272ef276c46723d12adf679dd934352</id>
<content type='text'>
commit e0e4a2ce7a059d051c66cd7c94314fef3cd91aea upstream.

v2:
change period from 10ms to 100ms (typo error)

too high frequence to update mertrics table will cause smu firmware
error,so change mertrics table update period from 1ms to 100ms
(navi10, 12, 14)

Signed-off-by: Kevin Wang &lt;kevin1.wang@amd.com&gt;
Reviewed-by: Kenneth Feng &lt;kenneth.feng@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: stable@vger.kernel.org # 5.3.x
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/amd/powerpaly: fix navi series custom peak level value error</title>
<updated>2019-10-07T17:01:19Z</updated>
<author>
<name>Kevin Wang</name>
</author>
<published>2019-08-21T02:58:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=adaf6a48e85f91ab4b2da7848fb781fd91268f79'/>
<id>urn:sha1:adaf6a48e85f91ab4b2da7848fb781fd91268f79</id>
<content type='text'>
[ Upstream commit 706feb26f890e1b8297b5d14975160de361edf4f ]

fix other navi asic set peak performance level error.
because the navi10_ppt.c will handle navi12 14 asic,
it will use navi10 peak value to set other asic, it is not correct.

after patch:
only navi10 use custom peak value, other asic will used default value.

Signed-off-by: Kevin Wang &lt;kevin1.wang@amd.com&gt;
Reviewed-by: Evan Quan &lt;evan.quan@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>drm/amd/powerplay/smu7: enforce minimal VBITimeout (v2)</title>
<updated>2019-10-05T13:12:09Z</updated>
<author>
<name>Ahzo</name>
</author>
<published>2019-08-05T19:14:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c748297e8576cce33a9ddb9e3b9ccf4b2f11e290'/>
<id>urn:sha1:c748297e8576cce33a9ddb9e3b9ccf4b2f11e290</id>
<content type='text'>
[ Upstream commit f659bb6dae58c113805f92822e4c16ddd3156b79 ]

This fixes screen corruption/flickering on 75 Hz displays.

v2: make print statement debug only (Alex)

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=102646
Reviewed-by: Evan Quan &lt;evan.quan@amd.com&gt;
Signed-off-by: Ahzo &lt;Ahzo@tutanota.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>drm/amd/powerplay: correct Vega20 dpm level related settings</title>
<updated>2019-08-27T17:23:40Z</updated>
<author>
<name>Evan Quan</name>
</author>
<published>2019-08-19T05:17:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=83e09d5bddbee749fc83063890244397896a1971'/>
<id>urn:sha1:83e09d5bddbee749fc83063890244397896a1971</id>
<content type='text'>
Correct the settings for auto mode and skip the unnecessary
settings for dcefclk and fclk.

Signed-off-by: Evan Quan &lt;evan.quan@amd.com&gt;
Acked-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/powerplay: Fix Vega20 power reading again</title>
<updated>2019-08-26T21:20:32Z</updated>
<author>
<name>Kent Russell</name>
</author>
<published>2019-08-23T13:13:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=23b7f6c41d4717b1638eca47e09d7e99fc7b9fd9'/>
<id>urn:sha1:23b7f6c41d4717b1638eca47e09d7e99fc7b9fd9</id>
<content type='text'>
For the 40.46 SMU release, they changed CurrSocketPower to
AverageSocketPower, but this was changed back in 40.47 so just check if
it's 40.46 and make the appropriate change

Tested with 40.45, 40.46 and 40.47 successfully

Signed-off-by: Kent Russell &lt;kent.russell@amd.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/powerplay: Fix Vega20 Average Power value v4</title>
<updated>2019-08-26T21:20:02Z</updated>
<author>
<name>Kent Russell</name>
</author>
<published>2019-08-22T12:17:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=21649c0b6b7899f4fa3099c46d3d027f60b107ec'/>
<id>urn:sha1:21649c0b6b7899f4fa3099c46d3d027f60b107ec</id>
<content type='text'>
The SMU changed reading from CurrSocketPower to AverageSocketPower, so
reflect this accordingly. This fixes the issue where Average Power
Consumption was being reported as 0 from SMU 40.46-onward

v2: Fixed headline prefix
v3: Add check for SMU version for proper compatibility
v4: Style fix

Signed-off-by: Kent Russell &lt;kent.russell@amd.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
</content>
</entry>
<entry>
<title>drm/amdgpu/powerplay: silence a warning in smu_v11_0_setup_pptable</title>
<updated>2019-08-23T01:46:32Z</updated>
<author>
<name>Alex Deucher</name>
</author>
<published>2019-08-22T03:25:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=75710f08ea7e41b2f7010da3f6deab061f7a853b'/>
<id>urn:sha1:75710f08ea7e41b2f7010da3f6deab061f7a853b</id>
<content type='text'>
I think gcc is confused as I don't see how size could be used
unitialized, but go ahead and silence the warning.

Signed-off-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Reviewed-by: Evan Quan &lt;evan.quan@amd.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20190822032527.1376-1-alexander.deucher@amd.com
</content>
</entry>
</feed>
