dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Lizhi Hou <lizhi.hou@amd.com>, dri-devel@lists.freedesktop.org
Cc: jeff.hugo@oss.qualcomm.com, stable@vger.kernel.org
Subject: Re: [PATCH] accel/ivpu: Use firmware names from upstream repo
Date: Wed, 7 May 2025 08:59:01 +0200	[thread overview]
Message-ID: <35f0d2b1-e958-44db-b4d2-978cd741c3ab@linux.intel.com> (raw)
In-Reply-To: <abf77771-ca6a-3b29-f5e7-fbb11c53844a@amd.com>

Hi,

On 5/6/2025 5:41 PM, Lizhi Hou wrote:
> 
> On 5/6/25 02:20, Jacek Lawrynowicz wrote:
>> Use FW names from linux-firmware repo instead of deprecated ones.
>>
>> Fixes: c140244f0cfb ("accel/ivpu: Add initial Panther Lake support")
>> Cc: <stable@vger.kernel.org> # v6.13+
>> Signed-off-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
>> ---
>>   drivers/accel/ivpu/ivpu_fw.c | 12 ++++++------
>>   1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/accel/ivpu/ivpu_fw.c b/drivers/accel/ivpu/ivpu_fw.c
>> index ccaaf6c100c02..9db741695401e 100644
>> --- a/drivers/accel/ivpu/ivpu_fw.c
>> +++ b/drivers/accel/ivpu/ivpu_fw.c
>> @@ -55,18 +55,18 @@ static struct {
>>       int gen;
>>       const char *name;
>>   } fw_names[] = {
>> -    { IVPU_HW_IP_37XX, "vpu_37xx.bin" },
>> +    { IVPU_HW_IP_37XX, "intel/vpu/vpu_37xx_v1.bin" },
> 
> What if old only vpu_37xx.bin is installed but not intel/vpu/vpu_37xx_v1?
> 
> Maybe just put *_v1 line in front without removing { ..., "vpu_37xx.bin"} ?
> 

The vpu_37xx.bin style names were never released. This was only for developer convenience but it turns out that developers don't use this anymore, so it is safe to remove. Maybe it make sense to mention this in commit message :)

> 
>>       { IVPU_HW_IP_37XX, "intel/vpu/vpu_37xx_v0.0.bin" },
>> -    { IVPU_HW_IP_40XX, "vpu_40xx.bin" },
>> +    { IVPU_HW_IP_40XX, "intel/vpu/vpu_40xx_v1.bin" },
>>       { IVPU_HW_IP_40XX, "intel/vpu/vpu_40xx_v0.0.bin" },
>> -    { IVPU_HW_IP_50XX, "vpu_50xx.bin" },
>> +    { IVPU_HW_IP_50XX, "intel/vpu/vpu_50xx_v1.bin" },
>>       { IVPU_HW_IP_50XX, "intel/vpu/vpu_50xx_v0.0.bin" },
>>   };
>>     /* Production fw_names from the table above */
>> -MODULE_FIRMWARE("intel/vpu/vpu_37xx_v0.0.bin");
>> -MODULE_FIRMWARE("intel/vpu/vpu_40xx_v0.0.bin");
>> -MODULE_FIRMWARE("intel/vpu/vpu_50xx_v0.0.bin");
>> +MODULE_FIRMWARE("intel/vpu/vpu_37xx_v1.bin");
>> +MODULE_FIRMWARE("intel/vpu/vpu_40xx_v1.bin");
>> +MODULE_FIRMWARE("intel/vpu/vpu_50xx_v1.bin");
>>     static int ivpu_fw_request(struct ivpu_device *vdev)
>>   {


  reply	other threads:[~2025-05-07  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06  9:20 [PATCH] accel/ivpu: Use firmware names from upstream repo Jacek Lawrynowicz
2025-05-06 15:41 ` Lizhi Hou
2025-05-07  6:59   ` Jacek Lawrynowicz [this message]
2025-05-07 15:24     ` Lizhi Hou
2025-05-12 18:36       ` Jeff Hugo
2025-05-28  9:52 ` Jacek Lawrynowicz

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=35f0d2b1-e958-44db-b4d2-978cd741c3ab@linux.intel.com \
    --to=jacek.lawrynowicz@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=lizhi.hou@amd.com \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).