From: Val Packett <val@packett.cool>
To: 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>,
Stefan Schmidt <stefan.schmidt@linaro.org>,
Vedang Nagar <quic_vnagar@quicinc.com>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: iris: set default size when S_FMT is called with zero size
Date: Thu, 25 Dec 2025 19:53:26 -0300 [thread overview]
Message-ID: <e13015c9-29b8-46e9-9290-d1d71eb73e51@packett.cool> (raw)
In-Reply-To: <c0dbc541-d321-4ce1-9d2d-0c4189ef752f@kernel.org>
On 10/28/25 10:19 AM, Bryan O'Donoghue wrote:
> On 13/10/2025 00:50, Val Packett wrote:
>> drivers/media/platform/qcom/iris/iris_vdec.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/media/platform/qcom/iris/iris_vdec.c
>> b/drivers/media/platform/qcom/iris/iris_vdec.c
>> index ae13c3e1b426..6be09d82e24d 100644
>> --- a/drivers/media/platform/qcom/iris/iris_vdec.c
>> +++ b/drivers/media/platform/qcom/iris/iris_vdec.c
>> @@ -196,6 +196,11 @@ int iris_vdec_s_fmt(struct iris_inst *inst,
>> struct v4l2_format *f)
>> if (vb2_is_busy(q))
>> return -EBUSY;
>>
>> + if (f->fmt.pix_mp.width == 0 && f->fmt.pix_mp.height == 0) {
>> + f->fmt.pix_mp.width = DEFAULT_WIDTH;
>> + f->fmt.pix_mp.height = DEFAULT_HEIGHT;
>> + }
>> +
>> iris_vdec_try_fmt(inst, f);
>>
>> switch (f->type) {
>> --
>
> Doesn't venus do
>
> orig_pixmap = *pixmap;
>
> try_fmt();
>
> format.fmt.pix_mp.width = orig_pixmp.width;
> format.fmt.pix_mp.height = orig_pixmp.height;
>
> should you fall back to DEFAULT_WIDTH/HEIGHT or to
> orig_pixmp.width/height ?
Hi– sorry for the late reply and happy holidays :)
The patch does the fallback *before* try_fmt().
I have just retested everything, even with yesterday's new "misc fixes"
patchset
(https://lore.kernel.org/all/20251224-iris-fixes-v1-0-5f79861700ec@oss.qualcomm.com/).
The issue is still present, the 0x0 size is what iris_vdec_s_fmt gets
before try_fmt().
What the rpi-ffmpeg developer said
(https://github.com/jc-kynesim/rpi-ffmpeg/issues/103) is:
- V4L2 very clearly says that you should be able to pass anything into
S_FMT and it should set the returned values to something valid
- S_FMT should not only not complain, it should return valid values in
the structure passed to it which will then be used in the REQBUFS
- the buffers being allocated are for the coded bitstream (remember in
V4L2 speak OUTPUT=source, CAPTURE=destination); width/height doesn't
really mean a lot here but buffer size does
-
https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/dev-decoder.html
4.5.1.5 states "width, height: coded resolution of the stream; required
only if it cannot be parsed from the stream for the given coded format;
otherwise the decoder will use this resolution as a placeholder
resolution that will likely change as soon as it can parse the actual
coded resolution from the stream"
So since this is a deliberate zero request, and V4L2 requires returning
a valid placeholder resolution, it should be DEFAULT indeed.
I'll resend with a comment as requested by Dikshita.
~val
prev parent reply other threads:[~2025-12-25 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PAqEcmCHEfU40aJzxWzZEpPQfxYCXUAQ9a9lLgcqz47gzKU5z_bOvdOBleE7B3AIZ13bFrkW2ndB0eMgy2TQdw==@protonmail.internalid>
2025-10-12 23:50 ` Val Packett
2025-10-28 11:57 ` Dikshita Agarwal
2025-10-28 13:19 ` Bryan O'Donoghue
2025-12-25 22:53 ` Val Packett [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=e13015c9-29b8-46e9-9290-d1d71eb73e51@packett.cool \
--to=val@packett.cool \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=hverkuil@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vnagar@quicinc.com \
--cc=stefan.schmidt@linaro.org \
--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®