From: Jiaqi Shi <shijiaqi_develop@163.com>
To: linux-media@vger.kernel.org, imx@lists.linux.dev,
linux-staging@lists.linux.dev
Cc: slongerbeam@gmail.com, p.zabel@pengutronix.de,
mchehab@kernel.org, gregkh@linuxfoundation.org, Frank.Li@nxp.com,
kernel@pengutronix.de, festevam@gmail.com,
Jiaqi Shi <shijiaqi_develop@163.com>
Subject: [PATCH v4 0/2] media: imx: staging cleanup and FIM export to v4l2-core
Date: Sun, 22 Nov 2026 02:40:31 +0800 [thread overview]
Message-ID: <20261121184033.429680-1-shijiaqi_develop@163.com> (raw)
Changes in v4:
- Keep the user-visible format field unchanged at stream start. Resolve
the actual field order into a separate stream_field so source order
changes are revalidated on each stream start.
- Simplify the FIM external_timestamp callback to a single use_val flag.
- Document FIM allocation ownership, callback context, and locking rules.
The legacy_api mode remains enabled for the STD and frame-interval ioctls;
removing those interfaces is outside the scope of this cleanup.
This series continues the i.MX staging media driver cleanup by removing
legacy control inheritance and source-dependent format handling from
capture video nodes, and exports the generic Frame Interval Monitor to
v4l2-core while retaining the i.MX input capture controls locally.
Validation:
- allmodconfig build and sparse
- local FIM KUnit tests, not included in this series: 13/13 passed
- local white-box i.MX capture format tests, not included: 20/20 passed
- QEMU vivid: v4l2-compliance 125/125, 30-frame streaming passed
- QEMU vim2m: v4l2-compliance 49/49, 10-frame streaming passed
- i.MX register-level and hardware DMA paths remain untested
Jiaqi Shi (2):
media: imx: remove legacy video node control and format handling
media: v4l2-core: add frame interval monitor helper
Documentation/admin-guide/media/imx.rst | 20 +-
drivers/media/v4l2-core/Kconfig | 4 +
drivers/media/v4l2-core/Makefile | 1 +
drivers/media/v4l2-core/v4l2-fim.c | 331 ++++++++++++++++
drivers/staging/media/imx/Kconfig | 1 +
drivers/staging/media/imx/TODO | 13 -
drivers/staging/media/imx/imx-ic-prpencvf.c | 10 +-
drivers/staging/media/imx/imx-media-capture.c | 335 +++++++---------
drivers/staging/media/imx/imx-media-csi.c | 10 +-
.../staging/media/imx/imx-media-dev-common.c | 113 +-----
drivers/staging/media/imx/imx-media-fim.c | 361 +++---------------
drivers/staging/media/imx/imx-media-utils.c | 9 +-
drivers/staging/media/imx/imx-media.h | 11 +-
include/media/v4l2-fim.h | 49 +++
14 files changed, 599 insertions(+), 669 deletions(-)
create mode 100644 drivers/media/v4l2-core/v4l2-fim.c
delete mode 100644 drivers/staging/media/imx/TODO
create mode 100644 include/media/v4l2-fim.h
--
2.53.0
next reply other threads:[~2026-11-21 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 18:40 Jiaqi Shi [this message]
2026-11-21 18:40 ` [PATCH v4 1/2] media: imx: remove legacy video node control and format handling Jiaqi Shi
2026-11-21 18:40 ` [PATCH v4 2/2] media: v4l2-core: add frame interval monitor helper Jiaqi Shi
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=20261121184033.429680-1-shijiaqi_develop@163.com \
--to=shijiaqi_develop@163.com \
--cc=Frank.Li@nxp.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=slongerbeam@gmail.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