From: Pavan Bobba <opensource206@gmail.com>
To: skhan@linuxfoundation.org, kieran.bingham@ideasonboard.com,
mchehab@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Pavan Bobba <opensource206@gmail.com>
Subject: [PATCH 0/5] media: vimc: add RGB/YUV input entity and improve pipeline support
Date: Thu, 20 Nov 2025 14:19:21 +0530 [thread overview]
Message-ID: <20251120084926.18620-1-opensource206@gmail.com> (raw)
This series extends the vimc test driver with a new RGB/YUV input entity,
pipeline enhancements, and documentation updates.
Patch 1 adds an RGB/YUV input entity that can be used to simulate pipelines
starting after a real debayer stage.
Patch 2 adds V4L2_FIELD_ALTERNATE support to vimc-sensor, allowing it to
simulate interlaced sources.
Patch 3 extends the debayer to support multiple RGB output formats.
Patch 4 allows vimc-capture to accept custom bytesperline values so users can
exercise padded strides when testing the RGB/YUV path.
Patch 5 updates the vimc documentation with the RGB/YUV input entity and
revised media-ctl/v4l2-ctl examples.
Tested with:
- vimc.0 on x86_64 using media-ctl and v4l2-ctl pipelines
Pavan Bobba (5):
media: vimc: add RGB/YUV input entity implementation
media: vimc: add support for V4L2_FIELD_ALTERNATE in vimc-sensor
media: vimc: debayer: add support for multiple RGB formats
media: vimc: capture: support custom bytesperline values
docs: media: vimc: document RGB/YUV input entity
Documentation/admin-guide/media/vimc.rst | 39 +++-
drivers/media/test-drivers/vimc/Makefile | 3 +-
.../media/test-drivers/vimc/vimc-capture.c | 15 +-
drivers/media/test-drivers/vimc/vimc-common.h | 1 +
drivers/media/test-drivers/vimc/vimc-core.c | 3 +-
.../media/test-drivers/vimc/vimc-debayer.c | 113 ++++++++--
drivers/media/test-drivers/vimc/vimc-input.c | 210 ++++++++++++++++++
drivers/media/test-drivers/vimc/vimc-sensor.c | 9 +-
8 files changed, 352 insertions(+), 41 deletions(-)
create mode 100644 drivers/media/test-drivers/vimc/vimc-input.c
--
2.43.0
next reply other threads:[~2025-11-20 8:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 8:49 Pavan Bobba [this message]
2025-11-20 8:49 ` [PATCH 1/5] media: vimc: add RGB/YUV input entity implementation Pavan Bobba
2025-11-20 8:49 ` [PATCH 2/5] media: vimc: add support for V4L2_FIELD_ALTERNATE in vimc-sensor Pavan Bobba
2025-11-20 8:49 ` [PATCH 3/5] media: vimc: debayer: add support for multiple RGB formats Pavan Bobba
2025-11-20 8:49 ` [PATCH 4/5] media: vimc: capture: support custom bytesperline values Pavan Bobba
2025-11-20 8:49 ` [PATCH 5/5] docs: media: vimc: document RGB/YUV input entity Pavan Bobba
2025-11-20 16:38 ` [PATCH 0/5] media: vimc: add RGB/YUV input entity and improve pipeline support Shuah Khan
2025-11-28 3:11 ` opensource india
2025-12-09 5:04 ` opensource india
2025-12-15 19:10 ` Shuah Khan
2025-12-15 19:45 ` Shuah Khan
2025-12-16 2:57 ` opensource india
2025-12-29 16:04 ` opensource india
2025-12-31 20:43 ` Shuah Khan
2026-01-01 1:11 ` opensource india
2026-02-18 4:16 ` opensource india
2026-02-19 20:22 ` Shuah Khan
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=20251120084926.18620-1-opensource206@gmail.com \
--to=opensource206@gmail.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.org \
/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