From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: linux-media@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
laurent.pinchart@ideasonboard.com
Subject: [PATCHv2 00/11] media: omap3isp: v4l2-compliance fixes
Date: Tue, 2 Dec 2025 08:48:01 +0100 [thread overview]
Message-ID: <cover.1764661692.git.hverkuil+cisco@kernel.org> (raw)
When I worked on the patch series to remove the vb2 wait_prepare/finish
callbacks, I had to test that series on my Beagle xM board with a
Leopard Imaging li5m03 camera.
Since I wanted to use v4l2-compliance to test the vb2 change, I first had
to fix a bunch of other compliance problems in this driver so it would
actually be able to run the streaming tests.
This series contains the fixes I made to get to that point.
It depends on one sensor driver fix (posted separately):
https://patchwork.linuxtv.org/project/linux-media/patch/554fb9d7-374b-4868-b91b-959b8fd69b4d@kernel.org/
This series doesn't fix all compliance problems, but at least it is
a lot better now.
Regards,
Hans
Changes since v1:
- Simplify isp_video_enum_format by checking for duplicate pixelformats
- Drop -ENOTTY to -EINVAL change in isp_video_try_format.
Hans Verkuil (11):
media: omap3isp: add V4L2_CAP_IO_MC and don't set bus_info
media: omap3isp: isp_video_mbus_to_pix/pix_to_mbus fixes
media: omap3isp: implement enum_fmt_vid_cap/out
media: omap3isp: use V4L2_COLORSPACE_SRGB instead of _JPEG
media: omap3isp: set initial format
media: omap3isp: rework isp_video_try/set_format
media: omap3isp: implement create/prepare_bufs
media: omap3isp: better VIDIOC_G/S_PARM handling
media: omap3isp: support ctrl events for isppreview
media: omap3isp: ispccp2: always clamp in ccp2_try_format()
media: omap3isp: isppreview: always clamp in preview_try_format()
drivers/media/platform/ti/omap3isp/ispccp2.c | 2 +-
.../media/platform/ti/omap3isp/isppreview.c | 25 +--
.../media/platform/ti/omap3isp/ispresizer.c | 2 +-
drivers/media/platform/ti/omap3isp/ispvideo.c | 178 +++++++++++++-----
4 files changed, 146 insertions(+), 61 deletions(-)
--
2.51.0
next reply other threads:[~2025-12-02 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 7:48 Hans Verkuil [this message]
2025-12-02 7:48 ` [PATCHv2 01/11] media: omap3isp: add V4L2_CAP_IO_MC and don't set bus_info Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 02/11] media: omap3isp: isp_video_mbus_to_pix/pix_to_mbus fixes Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 03/11] media: omap3isp: implement enum_fmt_vid_cap/out Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 04/11] media: omap3isp: use V4L2_COLORSPACE_SRGB instead of _JPEG Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 05/11] media: omap3isp: set initial format Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 06/11] media: omap3isp: rework isp_video_try/set_format Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 07/11] media: omap3isp: implement create/prepare_bufs Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 08/11] media: omap3isp: better VIDIOC_G/S_PARM handling Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 09/11] media: omap3isp: support ctrl events for isppreview Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 10/11] media: omap3isp: ispccp2: always clamp in ccp2_try_format() Hans Verkuil
2025-12-02 7:48 ` [PATCHv2 11/11] media: omap3isp: isppreview: always clamp in preview_try_format() Hans Verkuil
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=cover.1764661692.git.hverkuil+cisco@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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