Hi NXP Team,
We are testing an OX05B1S GMSL2 camera on an i.MX95 19x19 EVK running Linux.
Setup:
OX05B1S camera - MAX96717 - GMSL2 - MX95MBDESER01 MAX96724 - i.MX95
The OX03C10 camera supplied with the MX95MBDES10001 kit works with the same deserializer board and is visible using cam -l.
However, the OX05B1S camera with MAX96717 is not listed by cam -l.
The BSP contains ox05b1s.ko, max96724.ko, max96717_lib.ko, and OX05B1S DTB files.
The OX05B1S DTB appears to describe a direct MIPI connection, while the OX03C10 DTB contains the MAX96724 topology.
Does NXP provide a reference device tree configuration for this setup?
OX05B1S - MAX96717 - MAX96724 - i.MX95
If not, could you please advise what changes are required to use this OX05B1S GMSL2 camera with the MX95MBDESER01 board?
Thank you.
Best regards,
Tharun
Thank you for the clarification. We understand that the current BSP officially supports OX05B1S through the direct MIPI-CSI interface, while MAX96717/MAX96724 SerDes support is provided for OX03C10.
We are using an OX05B1S camera module with a MAX96717 serializer connected to the i.MX95 through the MAX96724 deserializer. The GMSL2 link locks successfully, and the MAX96717 is accessible over the remote I2C channel.
Is OX05B1S + MAX96717 + MAX96724 currently unsupported by the BSP, meaning that a custom driver/device-tree integration is required? Or is there any reference implementation or patch available for this combination?
current bsp supports OX05B1S with MIPI_CSI miniSAS connector to connect imx95 board directly, The Omnivision OX03C10 sensor is supported on i.MX 95 using serializer/deserializer solutions from the following vendors:
• Analog Devices: MAX96717/MAX96724
• Texas Instruments: DS0UB953/DS0UV960
for more detailed information, pls refer to the chapter 6.1.3 Cameras of reference manual
yes, refer to the driver mx95mbcam.c which uses OX03C10, if you need change the camera, you should change this driver totally,
https://github.com/nxp-imx/linux-imx/blob/lf-6.18.y/drivers/media/i2c/mx95mbcam.c