From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>
Subject: [GIT PULL FOR 6.10] Ov4689 sensor patches, IVSC fixes and V4L2 async improvements
Date: Fri, 26 Apr 2024 06:45:28 +0000 [thread overview]
Message-ID: <ZitNiLquDWkye4Qg@valkosipuli.retiisi.eu> (raw)
Hi Hans, Mauro,
Here are a bunch of patches for the ov4689 and imx219 sensor drivers, as
well as link frequency control improvements for the IVSC driver as well as
moving some of the work from drivers to v4l2-async.
Please pull.
The following changes since commit faa4364bef2ec0060de381ff028d1d836600a381:
media: stk1160: fix bounds checking in stk1160_copy_video() (2024-04-24 13:49:56 +0200)
are available in the Git repository at:
git://linuxtv.org/sailus/media_tree.git tags/for-6.10-3-signed
for you to fetch changes up to 17da36cbdb10ee1f66761948314f664ca4aa4201:
media: v4l: async: Set owner for async sub-devices (2024-04-26 08:43:20 +0300)
----------------------------------------------------------------
V4L2 patches for 6.10
----------------------------------------------------------------
Mikhail Rudenko (16):
media: i2c: ov4689: Clean up and annotate the register table
media: i2c: ov4689: Sort register definitions by address
media: i2c: ov4689: Fix typo in a comment
media: i2c: ov4689: CCI conversion
media: i2c: ov4689: Remove i2c_client from ov4689 struct
media: i2c: ov4689: Refactor ov4689_set_ctrl
media: i2c: ov4689: Use sub-device active state
media: i2c: ov4689: Enable runtime PM before registering sub-device
media: i2c: ov4689: Use runtime PM autosuspend
media: i2c: ov4689: Remove max_fps field from struct ov4689_mode
media: i2c: ov4689: Make horizontal blanking configurable
media: i2c: ov4689: Implement vflip/hflip controls
media: i2c: ov4689: Implement digital gain control
media: i2c: ov4689: Implement manual color balance controls
media: i2c: ov4689: Move pixel array size out of struct ov4689_mode
media: i2c: ov4689: Set timing registers programmatically
Sakari Ailus (5):
media: v4l: Support obtaining link frequency from INTEGER64 controls
media: Documentation: v4l: LINK_FREQ can be an INTEGER64 control
media: ivsc: csi: Fix link frequency control behaviour
media: v4l: Set sub-device's owner field to the caller's module
media: v4l: async: Set owner for async sub-devices
Umang Jain (1):
media: i2c: imx219: Use dev_err_probe on probe
.../media/v4l/ext-ctrls-image-process.rst | 2 +-
drivers/media/i2c/Kconfig | 1 +
drivers/media/i2c/imx219.c | 77 ++-
drivers/media/i2c/ov4689.c | 671 +++++++++++----------
drivers/media/pci/intel/ivsc/mei_csi.c | 30 +-
drivers/media/v4l2-core/v4l2-async.c | 10 +-
drivers/media/v4l2-core/v4l2-common.c | 3 +
drivers/media/v4l2-core/v4l2-device.c | 12 +-
drivers/media/v4l2-core/v4l2-i2c.c | 2 +-
drivers/media/v4l2-core/v4l2-spi.c | 2 +-
include/media/v4l2-async.h | 4 +-
include/media/v4l2-device.h | 7 +-
12 files changed, 436 insertions(+), 385 deletions(-)
--
Sakari Ailus
next reply other threads:[~2024-04-26 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 6:45 Sakari Ailus [this message]
2024-04-26 7:56 ` [GIT PULL FOR 6.10] Ov4689 sensor patches, IVSC fixes and V4L2 async (#101222) Jenkins
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=ZitNiLquDWkye4Qg@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).