From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: jeff.hugo@oss.qualcomm.com, lizhi.hou@amd.com, stable@vger.kernel.org
Subject: Re: [PATCH] accel/ivpu: Use firmware names from upstream repo
Date: Wed, 28 May 2025 11:52:29 +0200 [thread overview]
Message-ID: <a56c10eb-30d3-4e8e-83b7-7984e75c8d89@linux.intel.com> (raw)
In-Reply-To: <20250506092030.280276-1-jacek.lawrynowicz@linux.intel.com>
Applied to drm-misc-fixes
On 5/6/2025 11:20 AM, 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" },
> { 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)
> {
prev parent reply other threads:[~2025-05-28 9:52 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
2025-05-07 15:24 ` Lizhi Hou
2025-05-12 18:36 ` Jeff Hugo
2025-05-28 9:52 ` Jacek Lawrynowicz [this message]
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=a56c10eb-30d3-4e8e-83b7-7984e75c8d89@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).