- 24 May, 2019 40 commits
-
-
Evan Quan authored
smu_get_clk_info_from_vbios() was called repeatedly. It seems a merge error. Signed-off-by:
Evan Quan <evan.quan@amd.com> Reviewed-by:
Alex Deucher <alexander.deucher@amd.com> Reviewed-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
-
Evan Quan authored
There is already sw smu check on IP block adding. Signed-off-by:
-
Harry Wentland authored
[WHY] These were only needed for bringup. They're not needed anymore. Signed-off-by:
Harry Wentland <harry.wentland@amd.com> Reviewed-by:
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Signed-off-by:
-
Harry Wentland authored
[WHY] Some early Raven boards had a bad SBIOS that doesn't play nicely with the DMCU FW. We thought the issues were fixed by ignoring errors on DMCU load but that doesn't seem to be the case. We've still seen reports of users unable to boot their systems at all. [HOW] Disable DMCU load on Raven 1. Only load it for Raven 2 and Picasso. v2: Fix ifdef (Alex) Signed-off-by:
-
Harry Wentland authored
[WHY] We only want to load DMCU FW on Picasso and Raven 2, not on Raven 1. Signed-off-by:
-
Ori Messinger authored
Firmware versions can be found as separate sysfs files at: /sys/class/drm/cardX/device/fw_version (where X is the card number) The firmware versions are displayed in hexadecimal. v2: Moved sysfs files to subfolder Signed-off-by:
Ori Messinger <ori.messinger@amd.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
-
Leo Liu authored
It should be attached to VCN 1.0 Signed-off-by:
Leo Liu <leo.liu@amd.com> Reviewed-by:
-
Leo Liu authored
Since this is VCN specific and only used by VCN Signed-off-by:
-
Tiecheng Zhou authored
it requires to initialize HDP_NONSURFACE_BASE, so as to avoid using the value left by a previous VM under sriov scenario. v2: it should not hurt baremetal, generalize it for both sriov and baremetal Signed-off-by:
Emily Deng <Emily.Deng@amd.com> Signed-off-by:
Tiecheng Zhou <Tiecheng.Zhou@amd.com> Reviewed-by:
-
Monk Liu authored
only report once per TMO job and the timer would be restarted upon the job finished if it's just slow. Suggested-by:
Monk Liu <Monk.Liu@amd.com> Reviewed-by:
-
Christian König authored
As far as we know this was never used by userspace and so should be removed. Signed-off-by:
Marek Olšák <marek.olsak@amd.com> Signed-off-by:
-
Evan Quan authored
Update Vega10 ACG Avfs GB parameters. Signed-off-by:
-
Evan Quan authored
On OD reset, the clock tables in SMU need to be reset to default. Signed-off-by:
-
Evan Quan authored
Update Vega10 top performance level power state accordingly on OD. Signed-off-by:
-
Evan Quan authored
No need to enable or disable AVFS if it's already in wanted state. Signed-off-by:
-
Evan Quan authored
With user specified voltage(DPMTABLE_OD_UPDATE_VDDC), the AVFS will be disabled. However, the buggy code makes this actually not working as expected. - V2: clear all OD flags excpet DPMTABLE_OD_UPDATE_VDDC Signed-off-by:
-
Evan Quan authored
This may affects the Vega10 MCLK OD functionality. Signed-off-by:
-
Leo Liu authored
To replace checking ring type and make them generic Signed-off-by:
-
Leo Liu authored
There is no user fence support for VCN Signed-off-by:
-
Leo Liu authored
There is no user fence support for VCE Signed-off-by:
-
Leo Liu authored
There is no user fence support for UVD Signed-off-by:
-
Leo Liu authored
So we can generalize the no user fence supported engine Signed-off-by:
-
xinhui pan authored
During S3/S4 bootloader will re-init ras state behind us. Resume might fail or raise a gpu reset. Signed-off-by:
xinhui pan <xinhui.pan@amd.com> Reviewed-by:
James Zhu <James.Zhu@amd.com> Tested-by:
-
xinhui pan authored
During S3/S4 bootloader will re-init ras state behind us. Resume might fail or raise a gpu reset. Signed-off-by:
-
xinhui pan authored
During S3/S4 bootloader will re-init ras state behind us. Resume might fail or raise a gpu reset. Signed-off-by:
-
xinhui pan authored
suspend/resume will change ras state behind us. Let driver get notified. Signed-off-by:
-
xinhui pan authored
add ras suspend function. rename ras_post_init to amdgpu_ras_resume. Signed-off-by:
-
xinhui pan authored
add badpages node. it will output badpages list in format gpu pfn : gpu page size : flags example 0x00000000 : 0x00001000 : R 0x00000001 : 0x00001000 : R 0x00000002 : 0x00001000 : R 0x00000003 : 0x00001000 : R 0x00000004 : 0x00001000 : R 0x00000005 : 0x00001000 : R 0x00000006 : 0x00001000 : R 0x00000007 : 0x00001000 : P 0x00000008 : 0x00001000 : P 0x00000009 : 0x00001000 : P flags can be one of below characters R: reserved. P: pending for reserve. F: failed to reserve for some reasons. Signed-off-by:
-
James Zhu authored
During S3 test, when system wake up and resume, ras interface is already allocated. Move workaround before ras jumps to resume step in gfx_v9_0_ecc_late_init, and make sure workaround applied during resume. Also remove unused mmGB_EDC_MODE clearing. Signed-off-by:
-
Wang Hai authored
Fix the following sparse warnings: drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_resource.c:483:21: warning: symbol 'dce120_clock_source_create' was not declared. Should it be static? drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_resource.c:506:6: warning: symbol 'dce120_clock_source_destroy' was not declared. Should it be static? drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_resource.c:513:6: warning: symbol 'dce120_hw_sequencer_create' was not declared. Should it be static? Fixes: b8fdfcc6 ("drm/amd/display: Add DCE12 core support") Reported-by:
Hulk Robot <hulkci@huawei.com> Signed-off-by:
Wang Hai <wanghai26@huawei.com> Signed-off-by:
-
Trigger Huang authored
Under Vega10 SR-IOV, with new RLC's new feature, VF should call RLC to program some registers if supported Signed-off-by:
Trigger Huang <Trigger.Huang@amd.com> Reviewed-by:
-
Trigger Huang authored
New feature for RLC, some registers can be programmed by RLC interface under SR-IOV VF: WREG32_SOC15_RLC_SHADOW: 1, for GRBM_GFX_CNTL, firstly the new register value should be be programmed to SCRATCH_REG2 1, for GRBM_GFX_INDEX, firstly the new register value should be be programmed to SCRATCH_REG3 WREG32_RLC: for registers supported to be programmed by RLC interface, the following sequence should be used: 1, write the value to SCRATCH_REG0 2, write reg | 0x80000000 to SCRATCH_REG1 3, write 0x1 to RLC_SPARE_INT to notify RLC 4, polling SCRATCH_REG1 to check if finished Signed-off-by:
-
Trigger Huang authored
For Vega10 SR-IOV VF, skip setting some regs due to: 1, host will program them 2, avoid VF register programming violations Signed-off-by:
-
Trigger Huang authored
Add VMR ring support for Vega10 SR-IOV VF if PSP supported Signed-off-by:
-
Trigger Huang authored
call psp to program ih cntl in SR-IOV if supported Signed-off-by:
-
Trigger Huang authored
Add implementation to program regs by PSP, currently the following IH registers are supported: IH_RB_CNTL IH_RB_CNTL_RING1 IH_RB_CNTL_RING2 Signed-off-by:
-
Trigger Huang authored
Add new PSP command GFX_CMD_ID_PROG_REG definition Signed-off-by:
-
Trigger Huang authored
In order to support new PSP feature that PSP may provide interface to program IH CNTL register, initialize PSP before IH under Vega10 SR-IOV VF Signed-off-by:
-
Trigger Huang authored
Set different register access mode according to the features provided by firmware Signed-off-by:
-
xinhui pan authored
ras need initialize proper state after late init Signed-off-by:
-
