From: "Yang, Philip" <Philip.Yang-5C7GfCeVMHo@public.gmane.org>
To: "Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH 3/3] drm/amdgpu: enable paging queue based on FW version
Date: Mon, 19 Nov 2018 21:16:31 +0000 [thread overview]
Message-ID: <f9918fbe-7cab-e8ce-0ecb-a53d1ba5f0c0@amd.com> (raw)
In-Reply-To: <BN6PR12MB18091E4BBC1BB24609AF383EF7D80-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
On 2018-11-19 3:57 p.m., Deucher, Alexander wrote:
>> -----Original Message-----
>> From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> On Behalf Of
>> Yang, Philip
>> Sent: Monday, November 19, 2018 3:20 PM
>> To: amd-gfx@lists.freedesktop.org
>> Cc: Yang, Philip <Philip.Yang@amd.com>
>> Subject: [PATCH 3/3] drm/amdgpu: enable paging queue based on FW
>> version
>>
>> Based SDMA fw version to enable has_page_queue support. Have to move
>> sdma_v4_0_init_microcode from sw_init to early_init, to load firmware and
>> init fw_version before set_ring/buffer/vm_pte_funcs use it.
>>
>> Change-Id: Ife5d4659d28bc2a7012b48947b27e929749d87c1
>> Signed-off-by: Philip Yang <Philip.Yang@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 46 +++++++++++++++++----
>> -----
>> 1 file changed, 30 insertions(+), 16 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
>> b/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
>> index 4d873fd3242c..0a3b68dd49a0 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
>> @@ -1447,23 +1447,44 @@ static void
>> sdma_v4_0_ring_emit_reg_wait(struct amdgpu_ring *ring, uint32_t reg,
>> sdma_v4_0_wait_reg_mem(ring, 0, 0, reg, 0, val, mask, 10); }
>>
>> +static bool sdma_v4_0_fw_support_paging_queue(struct amdgpu_device
>> +*adev) {
>> + uint fw_version = adev->sdma.instance[0].fw_version;
>> +
>> + switch (adev->asic_type) {
>> + case CHIP_VEGA10:
>> + return fw_version >= 430;
>> + case CHIP_VEGA12:
>> + return fw_version >= 31;
>> + case CHIP_VEGA20:
>> + return fw_version >= 115;
>> + default:
>> + return false;
>> + }
>> +}
>> +
>> static int sdma_v4_0_early_init(void *handle) {
>> struct amdgpu_device *adev = (struct amdgpu_device *)handle;
>> + int r;
>>
>> - if (adev->asic_type == CHIP_RAVEN) {
>> + if (adev->asic_type == CHIP_RAVEN)
>> adev->sdma.num_instances = 1;
>> - adev->sdma.has_page_queue = false;
>> - } else {
>> + else
>> adev->sdma.num_instances = 2;
>> - /* TODO: Page queue breaks driver reload under SRIOV */
>> - if ((adev->asic_type == CHIP_VEGA10) &&
>> amdgpu_sriov_vf((adev)))
>> - adev->sdma.has_page_queue = false;
>> - else if (adev->asic_type != CHIP_VEGA20 &&
>> - adev->asic_type != CHIP_VEGA12)
>> - adev->sdma.has_page_queue = true;
>> +
>> + r = sdma_v4_0_init_microcode(adev);
>> + if (r) {
>> + DRM_ERROR("Failed to load sdma firmware!\n");
>> + return r;
> I think this should be ok. As long as you've verified that sdam_v4_0_init_microcode() doesn't depend on any other init from another module like psp. I took a quick look at the code and it seems like we should be ok.
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
sdma_v4_0_init_microcode() reads fw binary file and setup fw version etc
data structure. It doesn't depend on other init so it is fine to move it
from sw_init() to early_init(). sdma_v4_0_load_microcode() will start fw
from sdma_v4_0_start() which depends on psp, gmc etc. This happens after
early_init()->sw_init()->hw_init().
Philip
>
>> }
>>
>> + /* TODO: Page queue breaks driver reload under SRIOV */
>> + if ((adev->asic_type == CHIP_VEGA10) &&
>> amdgpu_sriov_vf((adev)))
>> + adev->sdma.has_page_queue = false;
>> + else if (sdma_v4_0_fw_support_paging_queue(adev))
>> + adev->sdma.has_page_queue = true;
>> +
>> sdma_v4_0_set_ring_funcs(adev);
>> sdma_v4_0_set_buffer_funcs(adev);
>> sdma_v4_0_set_vm_pte_funcs(adev);
>> @@ -1472,7 +1493,6 @@ static int sdma_v4_0_early_init(void *handle)
>> return 0;
>> }
>>
>> -
>> static int sdma_v4_0_sw_init(void *handle) {
>> struct amdgpu_ring *ring;
>> @@ -1491,12 +1511,6 @@ static int sdma_v4_0_sw_init(void *handle)
>> if (r)
>> return r;
>>
>> - r = sdma_v4_0_init_microcode(adev);
>> - if (r) {
>> - DRM_ERROR("Failed to load sdma firmware!\n");
>> - return r;
>> - }
>> -
>> for (i = 0; i < adev->sdma.num_instances; i++) {
>> ring = &adev->sdma.instance[i].ring;
>> ring->ring_obj = NULL;
>> --
>> 2.17.1
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-11-19 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 20:20 [PATCH 1/3] drm/amdgpu: fix typo in function sdma_v4_0_page_resume Yang, Philip
[not found] ` <20181119201946.5354-1-Philip.Yang-5C7GfCeVMHo@public.gmane.org>
2018-11-19 20:20 ` [PATCH 2/3] drm/amdgpu: enable paging queue doorbell support v4 Yang, Philip
[not found] ` <20181119201946.5354-2-Philip.Yang-5C7GfCeVMHo@public.gmane.org>
2018-11-19 20:49 ` Deucher, Alexander
2018-11-19 20:20 ` [PATCH 3/3] drm/amdgpu: enable paging queue based on FW version Yang, Philip
[not found] ` <20181119201946.5354-3-Philip.Yang-5C7GfCeVMHo@public.gmane.org>
2018-11-19 20:57 ` Deucher, Alexander
[not found] ` <BN6PR12MB18091E4BBC1BB24609AF383EF7D80-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-11-19 21:16 ` Yang, Philip [this message]
[not found] ` <f9918fbe-7cab-e8ce-0ecb-a53d1ba5f0c0-5C7GfCeVMHo@public.gmane.org>
2018-11-20 9:58 ` Christian König
2018-11-19 20:49 ` [PATCH 1/3] drm/amdgpu: fix typo in function sdma_v4_0_page_resume Deucher, Alexander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9918fbe-7cab-e8ce-0ecb-a53d1ba5f0c0@amd.com \
--to=philip.yang-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox