linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Paul Kocialkowski <paulk@sys-base.io>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 4/4] Documentation: media: Document V4L2_H264_DECODE_PARAM_FLAG_PFRAME/BFRAME
Date: Sat, 30 Aug 2025 14:29:48 +0300	[thread overview]
Message-ID: <11ea89d2-e4f1-4c3a-a2c7-f99170781fba@gmail.com> (raw)
In-Reply-To: <aLG19wzWBBECU6Cs@shepard>

29.08.2025 17:15, Paul Kocialkowski пишет:
>>> +      - All submitted slices for the frame are P slices. This is a compability
>>> +        flag required for decoders that only support decoding such frames, but
>>> +        should not be required for slice-based decoders.
>> Seems to match the comment in Tegra driver, and related to a hardware
>> limitation. Shall we also recommend not to use this unless similar limitation
>> exists ?
> I think the flag should only be allowed for frame-based decode mode and indeed
> it would be good to say that drivers should only check this flag if they have
> such limitations.
> 
> Userspace on the other hand cannot really know if it will be used or not so it
> should set the flags when applicable.

IIRC, Tegra dec driver doesn't support decoding frames consisting of
multiple slices, it can only decode frames consisting of a single slice.
Tegra dec can handle multi-slice frames using a "macroblock by
macroblock" decoding mode with a lot of CPU processing, like classic old
hw decoders did it, this is not supported by upstream driver.


  reply	other threads:[~2025-08-30 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 18:07 [PATCH v2 0/4] Minor V4L2 Headers and Codec Doc Cleanups Paul Kocialkowski
2025-08-24 18:07 ` [PATCH v2 1/4] media: uapi: Move colorimetry controls at the end of the file Paul Kocialkowski
2025-08-28 18:45   ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 2/4] media: uapi: Cleanup tab after define in headers Paul Kocialkowski
2025-08-28 18:46   ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 3/4] media: uapi: v4l2-controls: Cleanup codec definitions Paul Kocialkowski
2025-08-28 18:46   ` Nicolas Dufresne
2025-08-24 18:07 ` [PATCH v2 4/4] Documentation: media: Document V4L2_H264_DECODE_PARAM_FLAG_PFRAME/BFRAME Paul Kocialkowski
2025-08-28 20:42   ` Nicolas Dufresne
2025-08-29 14:15     ` Paul Kocialkowski
2025-08-30 11:29       ` Dmitry Osipenko [this message]
2025-08-29 20:40 ` [PATCH v2 0/4] Minor V4L2 Headers and Codec Doc Cleanups Nicolas Dufresne

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=11ea89d2-e4f1-4c3a-a2c7-f99170781fba@gmail.com \
    --to=digetx@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=paulk@sys-base.io \
    /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).