Documentation/admin-guide/media/c3-isp.rst
Source file repositories/reference/linux-study-clean/Documentation/admin-guide/media/c3-isp.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/admin-guide/media/c3-isp.rst- Extension
.rst- Size
- 4122 bytes
- Lines
- 102
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
.. SPDX-License-Identifier: (GPL-2.0-only OR MIT)
.. include:: <isonum.txt>
=================================================
Amlogic C3 Image Signal Processing (C3ISP) driver
=================================================
Introduction
============
This file documents the Amlogic C3ISP driver located under
drivers/media/platform/amlogic/c3/isp.
The current version of the driver supports the C3ISP found on
Amlogic C308L processor.
The driver implements V4L2, Media controller and V4L2 subdev interfaces.
Camera sensor using V4L2 subdev interface in the kernel is supported.
The driver has been tested on AW419-C308L-Socket platform.
Amlogic C3 ISP
==============
The Camera hardware found on C308L processors and supported by
the driver consists of:
- 1 MIPI-CSI-2 module: handles the physical layer of the MIPI CSI-2 receiver and
receives data from the connected camera sensor.
- 1 MIPI-ADAPTER module: organizes MIPI data to meet ISP input requirements and
send MIPI data to ISP.
- 1 ISP (Image Signal Processing) module: contains a pipeline of image processing
hardware blocks. The ISP pipeline contains three resizers at the end each of
them connected to a DMA interface which writes the output data to memory.
A high-level functional view of the C3 ISP is presented below.::
+----------+ +-------+
| Resizer |--->| WRMIF |
+---------+ +------------+ +--------------+ +-------+ |----------+ +-------+
| Sensor |--->| MIPI CSI-2 |--->| MIPI ADAPTER |--->| ISP |---|----------+ +-------+
+---------+ +------------+ +--------------+ +-------+ | Resizer |--->| WRMIF |
+----------+ +-------+
|----------+ +-------+
| Resizer |--->| WRMIF |
+----------+ +-------+
Driver architecture and design
==============================
With the goal to model the hardware links between the modules and to expose a
clean, logical and usable interface, the driver registers the following V4L2
sub-devices:
- 1 `c3-mipi-csi2` sub-device - the MIPI CSI-2 receiver
- 1 `c3-mipi-adapter` sub-device - the MIPI adapter
- 1 `c3-isp-core` sub-device - the ISP core
- 3 `c3-isp-resizer` sub-devices - the ISP resizers
The `c3-isp-core` sub-device is linked to 2 video device nodes for statistics
capture and parameters programming:
- the `c3-isp-stats` capture video device node for statistics capture
- the `c3-isp-params` output video device for parameters programming
Each `c3-isp-resizer` sub-device is linked to a capture video device node where
frames are captured from:
- `c3-isp-resizer0` is linked to the `c3-isp-cap0` capture video device
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.