linux-toradex.git/drivers/media/platform/Makefile, branch master

media: rppx1: Add framework to support Dreamchip RPPX1 ISP

2026-07-30T17:51:35+00:00

Add a framework driver for Dreamchip RPPX1 ISP. The driver aims to
provide a framework for other V4L2 based drivers to drive the RPPX1
functionality. The reason for this split is that the RPPX1 IP itself do
not provide any DMA engines to drive data to/from the device, instead it
depends on other IP blocks to implement these features.

While the peripherals around the RPPX1 ISP used in different designs and
by different vendors are different the RPPX1 core itself is the same.
For this reason the framework solution to be able to split the Dreamchip
RPPX1 driver from vendors usage of it have been picked in hope to reduce
duplication of the common parts.

The design is to try and keep the surface of this framework as small as
possible. The intention of this change is to be able to fill all needs
of this.

  * Two functions to create and destroy a RPPX1 instance, rppx1_create()
    and rppx1_destory(). These are intended to be called in the users
    probe and remove code paths.

  * Two functions to start and stop the RPPX1 processing, rppx1_start()
    and rppx1_stop(). These are intended to be called in the users
    stream on and stream off code paths.

  * One function to ask the RPPX1 to process parameters buffer prepared
    by user space, rppx1_params(). The intention is to call this
    function when the parameter buffer is queued to the V4L2 driver and
    the result stored by the driver until the time it needs to be
    written to the RPPX1. It's the users responsibility to write it
    either using MMIO or other means.

  * One function to fill in a statistic buffer based on the current
    status of the RPPX1, rppx1_stats_fill_isr(). The intention is that
    the user call's this in its interrupt handler when it knows the
    RPPX1 is done processing a frame.

  * One function to ack and retrieve the interrupts generated by the
    RPPX1, rppx1_interrupt(). The intention is to call this function
    when the users interrupt handler detects the RPPX1 have raised and
    interrupt. There is no need for the user to understand, or act, on
    the actual RPPX1 interrupt, but it can if it wants too.

The initial support in the framework is limited and do not implement any
ISP processing algorithms other then configuring the RPPX1 to process
any Bayer (8-, 10, or 12-bit) image and produce either a RGB or YUYV
output. It do however probe all function blocks of the RPPX1 and provide
an interface to interact with both parameter and statistic bufferers.
The user of the framework will not change as algorithms for the
different function blocks of the ISP are being added.

Signed-off-by: Niklas Söderlund 
Co-developed-by: Jai Luthra 
Signed-off-by: Jai Luthra 
Co-developed-by: Jacopo Mondi 
Signed-off-by: Jacopo Mondi 
Reviewed-by: Jacopo Mondi 
Signed-off-by: Sakari Ailus

media: platform: amd: Introduce amd isp4 capture driver

2026-05-06T10:48:09+00:00

AMD isp4 capture is a v4l2 media device which implements media controller
interface. It has one sub-device (AMD ISP4 sub-device) endpoint which can
be connected to a remote CSI2 TX endpoint. It supports only one physical
interface for now. Also add ISP4 driver related entry info into the
MAINTAINERS file

Co-developed-by: Sultan Alsawaf 
Signed-off-by: Sultan Alsawaf 
Co-developed-by: Svetoslav Stoilov 
Signed-off-by: Svetoslav Stoilov 
Signed-off-by: Bin Du 
Reviewed-by: Mario Limonciello (AMD) 
Reviewed-by: Sultan Alsawaf 
Tested-by: Alexey Zagorodnikov 
Tested-by: Kate Hsuan 
Signed-off-by: Sakari Ailus

media: mali-c55: Add Mali-C55 ISP driver

2025-11-14T14:48:49+00:00

Add a driver for Arm's Mali-C55 Image Signal Processor. The driver is
V4L2 and Media Controller compliant and creates subdevices to manage
the ISP itself, its internal test pattern generator as well as the
crop, scaler and output format functionality for each of its two
output devices.

Tested-by: Lad Prabhakar 
Acked-by: Nayden Kanchev 
Co-developed-by: Jacopo Mondi 
Signed-off-by: Jacopo Mondi 
Signed-off-by: Daniel Scally 
Signed-off-by: Hans Verkuil 
[hverkuil: remove deprecated vb2_ops_wait_prepare/finish callbacks]

media: platform: synopsys: Add support for HDMI input driver

2025-03-05T16:40:18+00:00

Add initial support for the Synopsys DesignWare HDMI RX
Controller Driver used by Rockchip RK3588. The driver
supports:
 - HDMI 1.4b and 2.0 modes (HDMI 4k@60Hz)
 - RGB888, YUV422, YUV444 and YCC420 pixel formats
 - CEC
 - EDID configuration

The hardware also has Audio and HDCP capabilities, but these are
not yet supported by the driver.

Co-developed-by: Dingxian Wen 
Signed-off-by: Dingxian Wen 
Signed-off-by: Shreeya Patel 
Signed-off-by: Dmitry Osipenko 
Signed-off-by: Hans Verkuil

media: raspberrypi: Add support for PiSP BE

2024-06-27T11:06:47+00:00

Add support for the Raspberry Pi PiSP Back End.

The driver has been upported from the Raspberry Pi kernel at revision
f74893f8a0c2 ("drivers: media: pisp_be: Update seqeuence numbers of the
buffers").

The ISP documentation is available at:
https://datasheets.raspberrypi.com/camera/raspberry-pi-image-signal-processor-specification.pdf

Signed-off-by: David Plowman 
Signed-off-by: Naushir Patuck 
Signed-off-by: Nick Hollinghurst 
Signed-off-by: Jacopo Mondi 
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil 
[hverkuil: drop dev_err after platform_get_irq to fix a coccinelle check]

media: imagination: Add E5010 JPEG Encoder driver

2024-06-24T09:05:06+00:00

This adds support for stateful V4L2 M2M based driver for Imagination E5010
JPEG Encoder [1] which supports baseline encoding with two different
quantization tables and compression ratio as demanded.

Support for both contiguous and non-contiguous YUV420 and YUV422 semiplanar
formats is added along with alignment restrictions as required by the
hardware.

System and runtime PM hooks are added in the driver along with v4l2 crop
and selection API support.
Minimum resolution supported is 64x64 and
Maximum resolution supported is 8192x8192.

All v4l2-compliance tests are passing [2] :
v4l2-compliance -s -f -a  -d /dev/video0 -e /dev/video1

Total for e5010 device /dev/video0: 79, Succeeded: 79, Failed: 0,
Warnings: 0

NOTE: video1 here is VIVID test pattern generator

Also tests [3] were run manually to verify below driver features:
 - Runtime Power Management
 - Multi-instance JPEG Encoding
 - DMABUF import, export support
 - NV12, NV21, NV16, NV61 video format support
 - Compression quality S_CTRL
 - Cropping support using S_SELECTION

Existing V4L2 M2M based JPEG drivers namely s5p-jpeg, imx-jpeg and rcar_jpu
were referred while making this.

TODO:
Add MMU and memory tiling support

[1]:  AM62A TRM (Section 7.6 is for JPEG Encoder) :
Link: https://www.ti.com/lit/pdf/spruj16

[2]: v4l2-compliance test :
Link: https://gist.github.com/devarsht/1f039c631ca953a57f405cfce1b69e49

[3]: E5010 JPEG Encoder Manual tests :

Performance:
Link: https://gist.github.com/devarsht/c40672944fd71c9a53ab55adbfd9e28b

Functionality:
Link: https://gist.github.com/devarsht/8e88fcaabff016bb2bac83d89c9d23ce

Compression Quality:
Link: https://gist.github.com/devarsht/cbcc7cd97e8c48ba1486caa2b7884655

Multi Instance:
Link: https://gist.github.com/devarsht/22c2fca08cd3441fb40f2c7a4cebc95a

Crop support:
Link: https://gist.github.com/devarsht/de6f5142f678bb1a5338abfd9f814abd

Runtime PM:
Link: https://gist.github.com/devarsht/70cd95d4440ddc678489d93885ddd4dd

Co-developed-by: David Huang 
Signed-off-by: David Huang 
Signed-off-by: Devarsh Thakkar 
Reviewed-by: Benjamin Gaignard 
Signed-off-by: Sebastian Fricke 
Signed-off-by: Hans Verkuil

media: bcm2835-unicam: Add support for CCP2/CSI2 camera interface

2024-04-29T12:56:37+00:00

Add a driver for the Unicam camera receiver block on BCM283x processors.
It is represented as two video device nodes: unicam-image and
unicam-embedded which are connected to an internal subdev (named
unicam-subdev) in order to manage streams routing.

Signed-off-by: Dave Stevenson 
Co-developed-by: Naushir Patuck 
Signed-off-by: Naushir Patuck 
Co-developed-by: Jean-Michel Hautbois 
Signed-off-by: Jean-Michel Hautbois 
Co-developed-by: Laurent Pinchart 
Signed-off-by: Laurent Pinchart 
[Sakari Ailus: Squash fixes by Laurent.]
Signed-off-by: Sakari Ailus 
Signed-off-by: Hans Verkuil

media: nuvoton: Add driver for NPCM video capture and encoding engine

2023-09-27T07:40:02+00:00

Add driver for Video Capture/Differentiation Engine (VCD) and Encoding
Compression Engine (ECE) present on Nuvoton NPCM SoCs. As described in
the datasheet NPCM750D_DS_Rev_1.0, the VCD can capture frames from
digital video input and compare two frames in memory, and then the ECE
can compress the frame data into HEXTILE format. This driver implements
V4L2 interfaces and provides user controls to support KVM feature, also
tested with VNC Viewer ver.6.22.826 and openbmc/obmc-ikvm.

Signed-off-by: Marvin Lin 
Signed-off-by: Hans Verkuil

media: atmel: move microchip_csi2dc to dedicated microchip platform

2022-11-25T07:43:17+00:00

The Atmel ISC will be moved to staging thus the atmel platform will only
have the ISI driver.
The new media-controller converted ISC driver will be placed inside a
dedicated microchip platform directory.
It is then natural to have the microchip-csi2dc moved to this new platform
directory.
The next step is to add the Microchip ISC driver to the new platform
directory and reside together with the Microchip CSI2DC driver.

Signed-off-by: Eugen Hristev 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

media: destage Hantro VPU driver

2022-08-31T08:23:50+00:00

The Hantro mainline driver has been used in production
since several years and was only kept as a staging driver
due the stateless CODEC controls.

Now that all the stateless CODEC controls have been moved
out of staging, graduate the driver as well.

Signed-off-by: Ezequiel Garcia 
Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab