From: Mario Limonciello <mario.limonciello@amd.com>
To: David McFarland <corngood@gmail.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/amd: Don't init MEC2 firmware when it fails to load
Date: Mon, 29 Jan 2024 15:15:20 -0600 [thread overview]
Message-ID: <8bda643f-314d-4947-83a4-8ad536dfdc41@amd.com> (raw)
In-Reply-To: <bd7b16fb-987f-416c-a454-c424b95ed07a@amd.com>
On 1/29/2024 14:46, Mario Limonciello wrote:
> On 1/28/2024 10:18, David McFarland wrote:
>> The same calls are made directly above, but conditional on the firmware
>> loading and validating successfully.
>>
>> Fixes: 9931b67690cf ("drm/amd: Load GFX10 microcode during early_init")
>
> This is a great find, thank you for the fix. I'll apply it to our tree
> and Alex should send it in a future fixes PR.
>
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
Sorry to be pedantic; but I realized after I tried to apply this is
missing a S-o-b. Can you please add one?
>
>> ---
>> drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
>> b/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
>> index d63cab294883..b0ba68016a02 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c
>> @@ -4022,18 +4022,16 @@ static int gfx_v10_0_init_microcode(struct
>> amdgpu_device *adev)
>> err = amdgpu_ucode_request(adev, &adev->gfx.mec2_fw, fw_name);
>> if (!err) {
>> amdgpu_gfx_cp_init_microcode(adev, AMDGPU_UCODE_ID_CP_MEC2);
>> amdgpu_gfx_cp_init_microcode(adev, AMDGPU_UCODE_ID_CP_MEC2_JT);
>> } else {
>> err = 0;
>> adev->gfx.mec2_fw = NULL;
>> }
>> - amdgpu_gfx_cp_init_microcode(adev, AMDGPU_UCODE_ID_CP_MEC2);
>> - amdgpu_gfx_cp_init_microcode(adev, AMDGPU_UCODE_ID_CP_MEC2_JT);
>> gfx_v10_0_check_fw_write_wait(adev);
>> out:
>> if (err) {
>> amdgpu_ucode_release(&adev->gfx.pfp_fw);
>> amdgpu_ucode_release(&adev->gfx.me_fw);
>> amdgpu_ucode_release(&adev->gfx.ce_fw);
>> amdgpu_ucode_release(&adev->gfx.rlc_fw);
>
next prev parent reply other threads:[~2024-01-29 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 16:18 [PATCH 0/1] amdgpu: Fix crash when MEC2 firmware fails to load David McFarland
2024-01-28 16:18 ` [PATCH 1/1] drm/amd: Don't init MEC2 firmware when it " David McFarland
2024-01-29 20:46 ` Mario Limonciello
2024-01-29 21:15 ` Mario Limonciello [this message]
2024-01-29 22:18 ` [PATCH v2 0/1] " David McFarland
2024-01-29 22:18 ` [PATCH v2 1/1] " David McFarland
2024-01-29 22:21 ` Mario Limonciello
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=8bda643f-314d-4947-83a4-8ad536dfdc41@amd.com \
--to=mario.limonciello@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=corngood@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).