From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Rob Clark <rob.clark@oss.qualcomm.com>
Cc: Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 10/11] media: qcom: iris: use new firmware name for SM8250
Date: Sat, 21 Mar 2026 19:13:21 +0200 [thread overview]
Message-ID: <23y6nehk5z6z6lyclrmtllirzz47igbav3lep47xyomfnuqdo5@77nfhlqeyph3> (raw)
In-Reply-To: <CACSVV00Es3dGirfe9aHKwvaZog=DtEx9-ZPz1YeuStKobcpT7A@mail.gmail.com>
On Sat, Mar 21, 2026 at 07:56:47AM -0700, Rob Clark wrote:
> On Sat, Mar 21, 2026 at 7:45 AM Dmitry Baryshkov
> <dmitry.baryshkov@oss.qualcomm.com> wrote:
> >
> > The linux-firmware is providing the vpuNN_pM.mbn firmware for SM8250
> > since August of 2024. Stop using the legacy firmware name
> > (vpu-1.0/venus.mbn) and switch to the standard firmware name schema
> > (vpu/vpu20_p4.mbn).
>
> drive-by... how useful is it at all to list signed fw name in the
> driver, when it's going to have to be overridden by dts for basically
> everyone that isnt' a qc employee? On the GPU side, we stopped
> listing zap fw names for this reason.
True, that would be a good idea for the next platforms. Fot the existing
ones we have to support existing DTs, which don't list the firmware
name.
>
> BR,
> -R
>
> > Reviewed-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> > ---
> > drivers/media/platform/qcom/iris/iris_platform_vpu2.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/platform/qcom/iris/iris_platform_vpu2.c b/drivers/media/platform/qcom/iris/iris_platform_vpu2.c
> > index ab2a19aa9c36..692fbc2aab56 100644
> > --- a/drivers/media/platform/qcom/iris/iris_platform_vpu2.c
> > +++ b/drivers/media/platform/qcom/iris/iris_platform_vpu2.c
> > @@ -111,7 +111,7 @@ const struct iris_platform_data sm8250_data = {
> > .opp_clk_tbl = sm8250_opp_clk_table,
> > /* Upper bound of DMA address range */
> > .dma_mask = 0xe0000000 - 1,
> > - .fwname = "qcom/vpu-1.0/venus.mbn",
> > + .fwname = "qcom/vpu/vpu20_p4.mbn",
> > .inst_iris_fmts = iris_fmts_vpu2_dec,
> > .inst_iris_fmts_size = ARRAY_SIZE(iris_fmts_vpu2_dec),
> > .inst_caps = &platform_inst_cap_vpu2,
> >
> > --
> > 2.47.3
> >
> >
--
With best wishes
Dmitry
next prev parent reply other threads:[~2026-03-21 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 1:54 [PATCH v9 00/11] media: qcom: iris: rework platform data handling Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 01/11] media: qcom: iris: drop pas_id from the iris_platform_data struct Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 02/11] media: qcom: iris: use common set_preset_registers function Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 03/11] media: qcom: iris: don't use function indirection in gen2-specific code Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 04/11] media: qcom: iris: split HFI session ops from core ops Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 05/11] media: qcom: iris: merge hfi_response_ops and hfi_command_ops Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 06/11] media: qcom: iris: move get_instance to iris_hfi_sys_ops Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 07/11] media: qcom: iris: drop hw_response_timeout_val from platform data Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 08/11] media: qcom: iris: split firmware_data from raw " Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 09/11] media: qcom: iris: split platform data from firmware data Dmitry Baryshkov
2026-03-20 1:54 ` [PATCH v9 10/11] media: qcom: iris: use new firmware name for SM8250 Dmitry Baryshkov
2026-03-21 14:56 ` Rob Clark
2026-03-21 17:13 ` Dmitry Baryshkov [this message]
2026-03-20 1:54 ` [PATCH v9 11/11] media: qcom: iris: extract firmware description data Dmitry Baryshkov
2026-03-26 4:38 ` [PATCH v9 00/11] media: qcom: iris: rework platform data handling Dikshita Agarwal
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=23y6nehk5z6z6lyclrmtllirzz47igbav3lep47xyomfnuqdo5@77nfhlqeyph3 \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rob.clark@oss.qualcomm.com \
--cc=vikash.garodia@oss.qualcomm.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