From: Xilin Wu <sophon@radxa.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>,
Bryan O'Donoghue <bod@kernel.org>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
dragon@radxa.com, Chris Obbard <chris.obbard@oss.qualcomm.com>,
Deepak Sikri <sikrid@qti.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Loic Minier <loic.minier@oss.qualcomm.com>,
Jason Pettit <jason.pettit@oss.qualcomm.com>
Subject: Re: [PATCH 0/5] media: iris: HFI gen2 features and fixes for VA-API
Date: Wed, 4 Nov 2026 10:40:03 +0800 [thread overview]
Message-ID: <3B240D36F79259E9+d729c8d8-9eaa-4941-9516-401fec7970fb@radxa.com> (raw)
In-Reply-To: <6d16d639267c69344623f80ea91817308ef4f7d0.camel@ndufresne.ca>
On 11/4/2026 6:29 AM, Nicolas Dufresne wrote:
> Le mardi 03 novembre 2026 à 23:00 +0100, Bryan O'Donoghue a écrit :
>> On 29/10/2026 04:58, Xilin Wu wrote:
>>> This series adds features and fixes to Iris HFI gen2 to support
>>> qcom-va-driver [1], a userspace VA-API backend for the V4L2 stateful codec
>>> interface.
>>>
>>> It enables decode-order output and larger CAPTURE buffer pools for VA-API
>>> clients, and exposes encoder deblocking controls. It also fixes
>>> error-buffer timestamps and handling of non-display AV1 and VP9 pictures,
>>> which affect both VA-API and direct V4L2 clients.
>>>
>>> [1]https://github.com/radxa-pkg/qcom-va-driver
>>
>> Is this code based on https://github.com/intel/libva and is there a
>> route to getting it into the upstream of that repository ?
>
> libva is the runtime, qcom-va-driver is a driver, so that won't happen. Also,
> qcom-va-drivers does all sort of guessing heuristic, bitstream crafting and the
> readme show that it cost as much as 15% in throuput performance. Let's be
> honest, this is a bit of hack, not really a solution. A proper stateless
> firmware and driver would do a way better job and reduce complexity instead of
> increasing it. The provided patches though seems to all have merit, matching
> feature with venus, fixing bugs. A bit of spec work would not hurt though.
>
> Nicolas
Hi Nicolas,
The userspace software ecosystem around stateful V4L2 has long been a
challenge. With qcom-va-driver, we're trying to provide users with an
optional, as-out-of-the-box-as-possible solution that works with
existing VA-API applications.
I'm not sure whether the Qualcomm Iris hardware is capable of supporting
a stateless interface.
As far as I know, some folks at Qualcomm are also working on getting
qcom-va-driver into Debian:
https://tracker.debian.org/pkg/qcom-va-driver
Thanks for reviewing the patches!
--
Best regards,
Xilin Wu <sophon@radxa.com>
prev parent reply other threads:[~2026-11-04 2:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2a2gB7bYZ9q2UTG-mF855lyJvWdn3Ba6jqrFTEVO1EAjAIXMh7_-65v4XlrZmljww-5ozkNYL2-lWKTIH4oqOw==@protonmail.internalid>
2026-10-29 3:58 ` Xilin Wu
2026-10-29 3:58 ` [PATCH 1/5] media: iris: support decode-order output on HFI gen2 Xilin Wu
2026-11-03 22:18 ` Nicolas Dufresne
2026-10-29 3:58 ` [PATCH 2/5] media: iris: allow larger capture buffer pools " Xilin Wu
2026-11-03 22:20 ` Nicolas Dufresne
2026-10-29 3:58 ` [PATCH 3/5] media: iris: Add deblocking filter controls for " Xilin Wu
2026-10-29 3:58 ` [PATCH 4/5] media: iris: Preserve timestamps on error buffers Xilin Wu
2026-11-03 21:57 ` Bryan O'Donoghue
2026-11-03 22:14 ` Nicolas Dufresne
2026-10-29 3:58 ` [PATCH 5/5] media: iris: Recycle decoder buffers for non-display pictures Xilin Wu
2026-11-03 22:25 ` Nicolas Dufresne
2026-11-03 22:00 ` [PATCH 0/5] media: iris: HFI gen2 features and fixes for VA-API Bryan O'Donoghue
2026-11-03 22:29 ` Nicolas Dufresne
2026-11-04 2:40 ` Xilin Wu [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=3B240D36F79259E9+d729c8d8-9eaa-4941-9516-401fec7970fb@radxa.com \
--to=sophon@radxa.com \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=chris.obbard@oss.qualcomm.com \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dragon@radxa.com \
--cc=hverkuil@kernel.org \
--cc=jason.pettit@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.minier@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=sikrid@qti.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
all inboxes | Powered by JetHome®