From: Philipp Zabel <p.zabel@pengutronix.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-tegra@vger.kernel.org,
imx@lists.linux.dev, linux-rockchip@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-sunxi@lists.linux.dev, linux-staging@lists.linux.dev
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Bin Liu <bin.liu@mediatek.com>, Chen-Yu Tsai <wens@csie.org>,
Daniel Almeida <daniel.almeida@collabora.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
Devarsh Thakkar <devarsht@ti.com>,
Dmitry Osipenko <digetx@gmail.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Hans Verkuil <hverkuil@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Jacob Chen <jacob-chen@iotwrt.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Maxime Ripard <mripard@kernel.org>,
Michael Tretter <m.tretter@pengutronix.de>,
Ming Qian <ming.qian@nxp.com>,
Mirela Rabulea <mirela.rabulea@nxp.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Paul Kocialkowski <paulk@sys-base.io>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Steve Longerbeam <slongerbeam@gmail.com>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Xavier Roumegue <xavier.roumegue@oss.nxp.com>,
Yunfei Dong <yunfei.dong@mediatek.com>,
Zhou Peng <eagle.zhou@nxp.com>
Subject: Re: [PATCH v2] media: v4l2-mem2mem: Don't copy frame flags in v4l2_m2m_buf_copy_metadata()
Date: Wed, 15 Oct 2025 12:11:43 +0200 [thread overview]
Message-ID: <14f49cddfcb1c86598105ee394cd43a2bdf7fa89.camel@pengutronix.de> (raw)
In-Reply-To: <20251015100118.8755-1-laurent.pinchart@ideasonboard.com>
On Mi, 2025-10-15 at 13:01 +0300, Laurent Pinchart wrote:
> The v4l2_m2m_buf_copy_metadata() function takes a boolean
> copy_frame_flags argument. When true, it causes the function to copy the
> V4L2_BUF_FLAG_KEYFRAME, V4L2_BUF_FLAG_BFRAME and V4L2_BUF_FLAG_PFRAME
> flags from the output buffer to the capture buffer.
>
> There is no use cases in any upstream driver for copying the flags.
> KEY/P/B frames are properties of the bitstream buffer in some formats.
> Once decoded, this is no longer a property of the video frame and should
> be discarded.
>
> It was considered useful to know if an uncompressed frame was decoded
> from a KEY/P/B compressed frame, and to preserve that information if
> that same uncompressed frame was passed through another M2M device (e.g.
> a scaler). However, the V4L2 documentation makes it clear that the flags
> are meant for compressed frames only.
>
> Drop the copy_frame_flags argument from v4l2_m2m_buf_copy_metadata().
> The change to drivers was performed with the following Coccinelle
> semantic patch:
>
> @@
> expression src;
> expression dst;
> expression flag;
> @@
> - v4l2_m2m_buf_copy_metadata(src, dst, flag);
> + v4l2_m2m_buf_copy_metadata(src, dst);
>
> include/media/v4l2-mem2mem.h and drivers/media/v4l2-core/v4l2-mem2mem.c
> have been updated manually.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2025-10-15 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 10:01 [PATCH v2] media: v4l2-mem2mem: Don't copy frame flags in v4l2_m2m_buf_copy_metadata() Laurent Pinchart
2025-10-15 10:11 ` Philipp Zabel [this message]
2025-10-15 10:38 ` Benjamin Gaignard
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=14f49cddfcb1c86598105ee394cd43a2bdf7fa89.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=benjamin.gaignard@collabora.com \
--cc=bin.liu@mediatek.com \
--cc=daniel.almeida@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devarsht@ti.com \
--cc=digetx@gmail.com \
--cc=eagle.zhou@nxp.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=heiko@sntech.de \
--cc=hverkuil@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jacob-chen@iotwrt.com \
--cc=jernej.skrabec@gmail.com \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=ming.qian@nxp.com \
--cc=mirela.rabulea@nxp.com \
--cc=mripard@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=paulk@sys-base.io \
--cc=slongerbeam@gmail.com \
--cc=tiffany.lin@mediatek.com \
--cc=wens@csie.org \
--cc=xavier.roumegue@oss.nxp.com \
--cc=yunfei.dong@mediatek.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