> ## Documentation Index
> Fetch the complete documentation index at: https://dragonwingdocs-staging.qualcomm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Camera sensor driver development

![Camera\_sensor\_driver\_development.png](https://dragonwingdocs-staging.qualcomm.com/_mintlify/image/qualcomm-staging/Addendum-docs/Camera/images/Camera_sensor_driver_development.png)

The camera sensor driver contains information related to sensor hardware functionality including power settings, resolution, initialization settings, and exposure settings. It contains the configuration parameters/functions needed to initialize and operate a particular sensor. Each sensor has its own sensor driver.

Sensor driver development involves creating a `<sensor_name>_sensor.xml` and corresponding build configuration modifications. Developers can have custom camera sensor drivers. The topics in this section describes the supported Plan of Record (POR) sensors, as well as the camera sensor bringup process and corresponding files.

**Supported camera sensors**

> [tab] RB3G2 (QCS6490) camera sensors
>
> Refer to [Peripherals](https://www.qualcomm.com/products/internet-of-things/industrial/building-enterprise/qcs6490/peripherals) for QCS6490 POR and PVL components.
>
> The following POR sensor’s drivers are part of the QLI build.
>
> | **Camera sensor** | **Camera type** |
> | :-: | :-: |
> | OV9282 | MIPI DPHY |
> | IMX577 | MIPI DPHY |
> | AR0231 | Bayer GMSL (DPHY) |

> [tab] RB8 (QCS9075) camera sensors
>
> Refer to [Peripherals](https://www.qualcomm.com/products/internet-of-things/industrial-processors/iq9-series/iq-9100/peripherals) for QCS9075 PVL components.
>
> The following POR sensor’s drivers are part of the QLI build.
>
> | **Camera sensor** | **Camera type** |
> | :-: | :-: |
> | OV9282 | MIPI DPHY |
> | IMX577 (Arducam) | MIPI DPHY |
> | OX03F10 | Bayer GMSL (DPHY and CPHY) |
> | OX03F10 | YUV GMSL (DPHY and CPHY) |

> [tab] RB4 (QCS8275) camera sensors
>
> Refer to [Peripherals](https://www.qualcomm.com/products/internet-of-things/industrial-processors/iq9-series/iq-9100/peripherals) for QCS8275 PVL components.
>
> The following POR sensor’s drivers are part of the QLI build.
>
> | **Camera sensor** | **Camera type** |
> | :-: | :-: |
> | OV9282 | MIPI DPHY |
> | IMX577 (Arducam) | MIPI DPHY |
> | OX03F10 | Bayer GMSL (DPHY and CPHY) |
> | OX03F10 | YUV GMSL CPHY |

> [tab] IQ6 (QCS615) camera sensor
>
> Refer to [Peripherals](https://www.qualcomm.com/internet-of-things/products/iq6-series/iq-615/hardware) for QCS615 PVL components.
>
> The following POR sensor’s drivers are part of the QLI build.
>
> | **Camera sensor** | **Camera type** |
> | :-: | :-: |
> | IMX577 (Arducam) | MIPI DPHY |

* [Develop camera sensor driver](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Develop-camera-sensor-driver.md)
  Developing a custom sensor driver on the Qualcomm Linux platform typically involves the following steps.
* [Develop MIPI camera sensor driver](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Develop-MIPI-camera-sensor-driver.md)
  Developing a custom sensor driver involves creating a sensor driver XML file for the new camera sensor, bringing up the camera, and generating the binary files.
* [Develop GMSL camera sensor driver](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Develop-GMSL-camera-sensor-driver.md)
  Gigabit Multimedia Serial Link (GMSL) is a serial link technology used for camera applications in vehicles and other use cases where cameras are located at a distance up to 15 meters. With this technology, the camera signal is transmitted digitally and compression free using a coaxial cable.
* [Bring up YUV camera sensor driver](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Bring-up-YUV-camera-sensor-driver.md)
  Running YUV cameras is supported using the IFE/IFE Lite raw data interface (RDI) path. In this path, the IFE/IFE Lite dumps sensor data into memory without any process.
* [Configure camera sensor software](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Configure-camera-sensor-software.md)
  The camera sensor requires both a sensor driver XML file and module configuration XML file.
* [Configure GMSL camera sensor software](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Configure-GMSL-camera-sensor-software.md)
* [Configure sensor hardware](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Configure-sensor-hardware.md)
  The hardware configuration of the camera sensor module is saved in the kernel DTSI files.
* [Bring up EEPROM](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Bring-up-EEPROM.md)
  Electrically erasable programmable read-only memory (EEPROM) is a non-volatile memory used to store module calibration information.
* [PVL sensor driver distribution workflow](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/PVL-sensor-driver-distribution-workflow.md)
  Sensor module partners develop and tune PVL sensor drivers, distributing the compiled binaries to public users who lack access to the CHI-CDK sources.
* [Evaluate camera modules and calibration data](https://dragonwingdocs-staging.qualcomm.com/Addendum-docs/Camera/addendum/Evaluate-camera-modules-and-calibration-data.md)
  Camera modules have production variations that may cause the response of the camera module to differ even when used in the same external conditions.
