drm/amdgpu: Use unique doorbell range per xcc

Browse source

Program different ranges in each XCC with MEC_DOORBELL_RANGE_LOWER/HIGHER.
Keeping the same range causes CPF in other XCCs also to be busy when an IB
packet is submitted to KCQ. Only the XCC which processes the packet
comes back to idle afterwards and this causes other CPs not be idle.
This in turn affects clockgating behavior as RLC doesn't get idle
interrupt.

LOWER/HIGHER covers only KIQ/KCQs which are per XCC queues. Assigning
different ranges doesn't seem to have any side effect as user queue ranges
are outside of this range. User queue tests - PM4 through KFD and AQL
through rocr - have the same results after this change.

Signed-off-by: Lijo Lazar <lijo.lazar@amd.com>
Reviewed-by: Hawking Zhang <Hawking.Zhang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Lijo Lazar 2023-01-19 14:47:22 +05:30 • committed by Alex Deucher

parent 7389c75114

commit 233bb3733b

4 changed files with 47 additions and 25 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

35

drivers/gpu/drm/amd/amdgpu/amdgpu_doorbell.h

View file

5

drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c

View file

1

drivers/gpu/drm/amd/amdgpu/aqua_vanjaram_reg_init.c

View file

31

drivers/gpu/drm/amd/amdgpu/gfx_v9_4_3.c

View file