V4L2 drivers available for Jetson SoCs

Warning

You can find the full list of drivers, in the List of Tested Camera Sensors section of our RidgeRun Linux Camera Drivers wiki. Visit this wiki for more details on related driver services.

V4L2 drivers for the capture chips

Please note, if the driver that you are looking for is not in the list, we can create it for you. It is how all the drivers mentioned below started. Just contact us with the details about the driver that you need or send an email to support@ridgerun.com

This list includes some of the chips that have been tested already on NVIDIA Jetson TX1, Jetson TX2, and Xavier using RidgeRun V4L2 drivers. See also Jetson ISP Tuning

Thermal Cameras

Typically used with the TC358746 (parallel to MIPI CSI) RidgeRun has experience creating V4L2 Drivers for:

FLIR Tau640
FLIR Tau320

Color & Monochrome

AR0820
MAX96709/MAX96706 - GMSL1
MAX96705/MAX9286 - GMSL1
GMSL2
OV10640 and OV490
OV10635
OmniVision OV5647
OmniVision OV5647 (Jetson TX2+Auvidea J120)
OmniVision OV5647 (Jetson Nano)
OV5670
TC358840
TC358743
TC358746
V4L2 FPGA driver (Xilinx compatible)
Galileo2 TCM8647MD
IMX219
IMX230
IMX390
IMX258
IMX264
IMX274
IMX283
IMX290
IMX296
IMX298
IMX327
IMX334
IMX377
IMX385
IMX477
MT9M021 + Toshiba TC358746
IMX568
ON Semi AR0144
TW6869
OS08A10
ON Semi AR1335
MAX98357A-ASoC Driver in Jetson TX1 and TX2
AR0231 (Sekonix Camera)
ON Semi AP1302
ON Semi AR1335
ON Semi AR1820
ON Semi ARX3A0
IMX344
GMSL MAX9288
OV24A10
MT9V024
IMX397
OV7251
OmniVision OVM6211
OmniVision OV24A1B
OmniVision OV4689
TC358748
IMX214
AR0234
AR0820
OV4689
GeoSemi GW5300
AMS Mira130 : 1.3MP GS CMOS image sensor with NIR-enhanced performance
Lontium LT9211
Intersil TW6869

Radars

AWR2243

V4L2 drivers for the display chips

ADV7535

If the driver I am looking for is not on the list?

RidgeRun has wide experience in the development of kernel drivers, if the driver you are looking for is not on the list, it is most likely because we haven't received a request for it yet, but we can develop the new driver for you.

RidgeRun contact details are provided in the Contact Us section at the end of this wiki for requesting a new driver development.

Hardware availability

If you are planning on acquiring an existent driver and extending it with additional functionalities or if you are interested in requesting the creation of a totally new driver, please take into account that it might be necessary to send the required hardware to our offices to make sure our engineering team can test, debug and validate the driver.

ISP calibration

RidgeRun will use the default ISP calibration. Please notice that once the driver is in place you might need to create a custom ISP calibration file for your sensor if you need to use the built-in ISP. NVIDIA gives access to the ISP calibration tools only to ODMs, so companies like D3engineering and Leopard Imaging can create this file for you if the default settings don't produce the expected image quality.

How to port a driver to JetPack 6.0

In the JetPack 5 era, drivers were directly integrated into NVIDIA’s downstream kernel either built directly into the kernel image or built as in-tree module, but NVIDIA wants to align with the upstream kernel so users can choose the kernel version on their own. This means that on JetPack 6.0 a lot of drivers are being pulled out from the kernel source, which must be compiled separately as out-of-tree modules.

The Out of Tree modules scheme made significant modifications on how a driver is included to the kernel sources, feel free to read the following wiki if you wish to find out further details and instructions

How to port a driver to JetPack6.0

If you need assistance or you wish to port your driver to any JetPack version check the Contact Us section in order for you to hire our services. We provide support as T&M and also as an Engineering Subscription.