linux-toradex.git/drivers/media/i2c/Kconfig, branch master

media: i2c: cvs: Add driver of Intel Computer Vision Sensing Controller(CVS)

2026-05-28T18:17:52+00:00

Add driver for Intel Computer Vision Sensing (CVS) devices found on
Intel Luna Lake (LNL), Panther Lake (PTL), and Arrow Lake (ARL)
platforms.

The CVS device acts as a V4L2 sub-device bridge that manages CSI-2
link ownership between the host (Linux) and firmware for camera
sensors. It provides:

- Query the device status via sysfs interface
- CSI-2 link ownership arbitration between host and CVS firmware
- MIPI CSI-2 configuration management
- Privacy LED control coordination
- Power management integration with runtime PM

The driver consists of two main components:
  core.c: Core driver with probe, command transport, and power management
  v4l2.c: V4L2 sub-device and media framework integration

Hardware Interface:
- I2C for command/control communication with device firmware
- GPIO signals for ownership handshaking (request/response)
- Optional reset and wake interrupt for full-capability variants
- Integration with Intel IPU via ipu_bridge

The driver supports two hardware capability levels:
- Light capability: Basic GPIO-based ownership (2 GPIOs)
- Full capability: Enhanced with reset control and wake IRQ (4 GPIOs)

Device-specific quirks are handled via a quirk table to accommodate
variations across different CVS implementations (Lattice, Synaptics).

In addition to I2C-based operation, the driver supports platform
device instantiation for systems where CVS is exposed without I2C
transport, falling back to GPIO-only ownership control.

The CVS driver integrates with the IPU bridge for automatic device
discovery via ACPI on supported platforms.

PCI device IDs for Intel IPU7 (0x645d, shared by MTL and LNL) and
IPU7.5 (0xb05d, shared by ARL and PTL) are included in the
driver-local icvs_pci_tbl lookup table, enabling CVS to locate these
IPU variants without modifying the shared ipu6-pci-table header.

A PM runtime device link is established between IPU (consumer) and CVS
(supplier) so that the PM framework automatically resumes CVS before
IPU begins streaming, triggering cvs_runtime_resume() to claim CSI-2
link ownership. Ownership is released via cvs_runtime_suspend() after
the autosuspend delay.

Signed-off-by: Miguel Vadillo 
Tested-by: Mehdi Djait  # Dell XPS 13 9350 + IPU7
Reviewed-by: Mehdi Djait 
Signed-off-by: Sakari Ailus

media: i2c: drop unneeded dependencies on OF_GPIO

2026-05-05T14:57:03+00:00

OF_GPIO is selected automatically on all OF systems. Any symbols it
controls also provide stubs so there's really no reason to select it
explicitly. For Kconfig entries that have no other dependencies: convert
it to requiring OF to avoid new symbols popping up for everyone in make
config, for others just drop it altogether.

Signed-off-by: Bartosz Golaszewski 
Signed-off-by: Hans Verkuil

media: Add t4ka3 camera sensor driver

2026-03-26T11:16:25+00:00

Add the t4ka3 driver from:
https://github.com/kitakar5525/surface3-atomisp-cameras.git

With many cleanups / changes (almost a full rewrite) to make it suitable
for upstream:

* Remove the VCM and VCM-OTP support, the mainline kernel models VCMs and
  calibration data eeproms as separate v4l2-subdev-s.

* Remove the integration-factor t4ka3_get_intg_factor() support and IOCTL,
  this provided info to userspace through an atomisp private IOCTL.

* Turn atomisp specific exposure/gain IOCTL into standard v4l2 controls.

* Use normal ACPI power-management in combination with runtime-pm support
  instead of atomisp specific GMIN power-management code.

* Turn into a standard V4L2 sensor driver using
  v4l2_async_register_subdev_sensor().

* Add vblank, hblank, and link-freq controls; drop get_frame_interval().

* Use CCI register helpers.

* Calculate values for modes instead of using fixed register-value lists,
  allowing arbritrary modes.

* Add get_selection() and set_selection() support

* Add a CSI2 bus configuration check

This was tested on a Xiaomi Mipad2 tablet which has a T4KA3 sensor with
DW9761 VCM as back sensor.

Reviewed-by: Hans de Goede 
Co-developed-by: Hans de Goede 
Signed-off-by: Hans de Goede 
Signed-off-by: Kate Hsuan 
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil

media: i2c: Add ov2732 image sensor driver

2026-03-26T11:16:25+00:00

Add a V4L2 subdevice driver for the Omnivision OV2732 sensor.

The OV2732 is a 1/4" color CMOS 1080p (1920x1080) HD image sensor with
programmable controls like: gain, exposure, frame rate, image and windowing
size, horizontal mirror, vertical flip, cropping.

Signed-off-by: Walter Werner Schneider 
Reviewed-by: Jacopo Mondi 
[Sakari Ailus: Squashed Walter's fixup.]
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil

media: i2c: og01a1b: Change I2C interface controls to V4L2 CCI

2026-03-11T00:05:36+00:00

Switch the sensor driver to utilize V4L2 CCI helper interfaces instead
of driver specific wrappers over I2C read/write functions.

The conversion change is intended to be non-function, Group Access
register macros were removed as unused ones.

Signed-off-by: Vladimir Zapolskiy 
Signed-off-by: Sakari Ailus 
Signed-off-by: Mauro Carvalho Chehab

media: i2c: ov9282: Convert to CCI register access helpers

2026-03-11T00:05:33+00:00

Use the new common CCI register access helpers to replace the private
register access helpers in the ov9282 driver. This simplifies the driver
by reducing the amount of code.

Signed-off-by: Xiaolei Wang 
Reviewed-by: Tarang Raval 
Reviewed-by: Dave Stevenson 
[Sakari Ailus: Declare ret_hold earlier to make old GCC happy.]
Signed-off-by: Sakari Ailus 
Signed-off-by: Mauro Carvalho Chehab

media: i2c: ds90ub960: Add support for DS90UB954-Q1

2026-03-11T00:05:30+00:00

DS90UB954-Q1 is an FPDLink-III deserializer that is mostly register
compatible with DS90UB960-Q1. The main difference is that it supports half
of the RX and TX ports, i.e. 2x FPDLink RX ports and 1x CSI TX port.

A couple of differences are between the status registers and the
strobe setting registers. Hence accommodate these differences in
the UB960 driver so that we can reuse a large part of the existing code.

Link: https://www.ti.com/lit/gpn/ds90ub954-q1
Reviewed-by: Jai Luthra 
Reviewed-by: Tomi Valkeinen 
Signed-off-by: Yemike Abhilash Chandra 
Signed-off-by: Sakari Ailus 
Signed-off-by: Mauro Carvalho Chehab

media: i2c: ov5647: Convert to CCI register access helpers

2026-01-16T13:08:52+00:00

Use the new common CCI register access helpers to replace the private
register access helpers in the ov5647 driver. This simplifies the driver
by reducing the amount of code.

Signed-off-by: Xiaolei Wang 
Reviewed-by: Tarang Raval 
Reviewed-by: Hans de Goede 
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil

media: mt9m114: Use aptina-PLL helper to get PLL values

2026-01-14T22:33:04+00:00

Before this change the driver used hardcoded PLL m, n and p values to
achieve a 48MHz pixclock when used with an external clock with a frequency
of 24 MHz.

Use aptina_pll_calculate() to allow the driver to work with different
external clock frequencies. The m, n, and p values will be unchanged
with a 24 MHz extclk and this has also been tested with a 19.2 MHz
clock where m gets increased from 32 to 40.

Suggested-by: Laurent Pinchart 
Reviewed-by: Laurent Pinchart 
Signed-off-by: Hans de Goede 
[Sakari Ailus: Fix capitalisation of "MHz".]
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil

media: i2c: ov01a10: Convert to new CCI register access helpers

2026-01-13T11:28:48+00:00

Use the new comon CCI register access helpers to replace the private
register access helpers in the ov01a10 driver.

Signed-off-by: Hans de Goede 
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil