linux/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c, branch v5.14

drm/amdgpu: handle VCN instances when harvesting (v2)

2021-08-10T14:38:10Z

There may be multiple instances and only one is harvested. v2: fix typo in commit message Fixes: 83a0b8639185 ("drm/amdgpu: add judgement when add ip blocks (v2)") Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1673 Reviewed-by: Guchun Chen Reviewed-by: James Zhu Signed-off-by: Alex Deucher Cc: stable@vger.kernel.org

drm/amd/amdgpu: Use IP discovery data to determine VCN enablement instead of MMSCH

2021-06-18T21:14:01Z

In the past, we use MMSCH to determine whether a VCN is enabled or not. This is not reliable since after a FLR, MMSCH may report junk data. It is better to use IP discovery data. Signed-off-by: Bokun Zhang Signed-off-by: Peng Ju Zhou Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher

drm/amd/amdgpu: add instance_number check in amdgpu_discovery_get_ip_version

2021-06-11T20:02:50Z

The original code returns IP version of instantce_0 for every IP. This implementation may be correct for most of IPs. However, for certain IP block (VCN for example), it may have 2 instances and both of them have the same hw_id, BUT they have different revision number (0 and 1). In this case, the original amdgpu_discovery_get_ip_version cannot correct reflects the result and returns false information Signed-off-by: Bokun Zhang Signed-off-by: Peng Ju Zhou Signed-off-by: Alex Deucher

drm/amdgpu: add judgement when add ip blocks (v2)

2021-05-13T14:46:58Z

Judgement whether to add an sw ip according to the harvest info. v2: fix indentation (Alex) Signed-off-by: Likun Gao Reviewed-by: Guchun Chen Signed-off-by: Alex Deucher

drm/amdgpu: add UMC to ip discovery map

2020-11-13T05:13:43Z

resolve issue with UMC base offset not being set correctly in ip discovery sequence Reviewed-by: Hawking Zhang Signed-off-by: John Clements Signed-off-by: Alex Deucher

drm/amdgpu: move IP discovery data to mman

2020-08-04T21:29:29Z

It's related to the memory manager so move it there. Reviewed-by: Christian König Signed-off-by: Alex Deucher

drm/amdgpu: reduce ip discovery data reading size

2020-07-02T16:02:51Z

Only read first 4K data instead of whole TMR block, so we can reduce the time in full access mode. Signed-off-by: Wenhui Sheng Reviewed-by: Hawking Zhang Signed-off-by: Alex Deucher

drm/amdgpu: label internally used symbols as static

2020-07-01T05:59:23Z

Used sparse(make C=1) to find these loose ends. v2: removed unwanted extra line Signed-off-by: Nirmoy Das Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher

drm/amdgpu: re-structue members for ip discovery

2020-05-01T19:19:07Z

This is to prepare for initializing discovery tmr size per ASIC type Signed-off-by: Hawking Zhang Reviewed-by: Likun Gao Signed-off-by: Alex Deucher

drm/amdgpu: adjust sequence of ip_discovery init and timeout_setting

2020-04-01T18:44:43Z

what: 1)move timtout setting before ip_early_init to reduce exclusive mode cost for SRIOV 2)move ip_discovery_init() to inside of amdgpu_discovery_reg_base_init() it is a prepare for the later upcoming patches. why: in later upcoming patches we would use a new mailbox event -- "req_gpu_init_data", which is a callback hooked in adev->virt.ops and this callback send a new event "REQ_GPU_INIT_DAT" to host to notify host to do some preparation like "IP discovery/vbios on the VF FB" and this callback must be: A) invoked after set_ip_block() because virt.ops is configured during set_ip_block() B) invoked before ip_discovery_init() becausen ip_discovery_init() need host side prepares everything in VF FB first. current place of ip_discovery_init() is before we can invoke callback of adev->virt.ops, thus we must move ip_discovery_init() to a place after the adev->virt.ops all settle done, and the perfect place is in amdgpu_discovery_reg_base_init() Signed-off-by: Monk Liu Reviewed-by: Emily Deng Signed-off-by: Alex Deucher