From: "Jackson.lee" <jackson.lee@chipsnmedia.com>
To: mchehab@kernel.org, nicolas@ndufresne.ca, sebastian.fricke@collabora.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
hverkuil@xs4all.nl, nas.chung@chipsnmedia.com,
lafley.kim@chipsnmedia.com, b-brnich@ti.com,
jackson.lee@chipsnmedia.com
Subject: [PATCH v1 0/4] Add encoder features
Date: Tue, 24 Mar 2026 14:03:56 +0900 [thread overview]
Message-ID: <20260324050400.218-1-jackson.lee@chipsnmedia.com> (raw)
From: Jackson Lee <jackson.lee@chipsnmedia.com>
This series adds several encoder-side enhancements for the Wave5 driver.
The following features are introduced:
- Background detection support via V4L2 controls
- CBP profile support
- Support for packed YUV422 formats
Background detection allows the encoder to differentiate between
foreground and background regions, potentially improving compression
efficiency depending on the use case.
CBP profile support extends compatibility with additional encoding
profiles.
Support for packed YUV422 formats enables handling of commonly used
input formats such as YUYV and YVYU.
The changes include updates to control definitions, documentation,
and driver implementation.
Tested on Wave5 encoder pipeline with GStreamer.
Change since v0:
* For [PATCH v1 1/4] media: v4l2-controls: Add control
for background detection
- Added spaces around '+' in CID macro definition per CI suggestion
* For [PATCH v1 2/4] media: chips-media: wave5: Add support
for background detection
- Split into two patches: API addition and driver implementation
* For [PATCH v1 3/4] media: chips-media: wave5: Support CBP profile
- Added Fixed tag
- Added braces to all branches in the else-if/else block
* For [PATCH v1 4/4] media: chips-media: wave5: Add Support
for Packed YUV422 Formats
- Added Reviewed-by tag
Jackson Lee (4):
media: v4l2-controls: Add control for background detection
media: chips-media: wave5: Add support for background detection
media: chips-media: wave5: Support CBP profile
media: chips-media: wave5: Add Support for Packed YUV422 Formats
.../media/v4l/ext-ctrls-codec.rst | 6 +++
.../platform/chips-media/wave5/wave5-helper.h | 2 +-
.../platform/chips-media/wave5/wave5-hw.c | 7 ++-
.../chips-media/wave5/wave5-vpu-enc.c | 45 ++++++++++++++++++-
.../platform/chips-media/wave5/wave5-vpuapi.h | 2 +
drivers/media/v4l2-core/v4l2-ctrls-defs.c | 2 +
include/uapi/linux/v4l2-controls.h | 2 +
7 files changed, 63 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-24 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 5:03 Jackson.lee [this message]
2026-03-24 5:03 ` [PATCH v1 1/4] media: v4l2-controls: Add control for background detection Jackson.lee
2026-03-24 5:03 ` [PATCH v1 2/4] media: chips-media: wave5: Add support " Jackson.lee
2026-03-24 5:03 ` [PATCH v1 3/4] media: chips-media: wave5: Support CBP profile Jackson.lee
2026-03-24 20:18 ` Brandon Brnich
2026-03-24 5:04 ` [PATCH v1 4/4] media: chips-media: wave5: Add Support for Packed YUV422 Formats Jackson.lee
2026-03-24 20:24 ` Brandon Brnich
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=20260324050400.218-1-jackson.lee@chipsnmedia.com \
--to=jackson.lee@chipsnmedia.com \
--cc=b-brnich@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=lafley.kim@chipsnmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=nicolas@ndufresne.ca \
--cc=sebastian.fricke@collabora.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