Issue Configuring Routes and Port Switching for DS90UB960 Integration

[althaf]

Hello,

We are working on integrating the DS90UB960, as outlined in section "6.1.3.2.3.2 Texas Instruments SerDes" of the i.MX Linux Reference Manual (Rev. LF6.6.36_2.1.0 — 30 September 2024). We have successfully configured the device tree for four image sensors and have been able to load all the subdevices. Using the media-ctl tool, we can establish the links and set the formats.

However, we are unable to configure the routes as described on section 6.1.3.2(page 111) of the manual. While trying to set the routes , its giving an error as follows:
# media-ctl -R '"crossbar" [0/0 -> 2/0 [1]]'
media-ctl: unrecognized option: R
Invalid option -?

It seems that the -R option is not recognized by media-ctl as it does not appear in the option list. [Media controller API version 6.9.3]

Additionally, we are able to capture images from port 0, but we are unable to switch to ports 1, 2, or 3 for image capture. It appears that only a single route is registered under the available routes.

Could you please help us understand what we are missing here?

[althaf]

Hi, just wanted to check in and see if there are any updates on this? Thanks!

[JosephAtNXP]

Hi,

It's the same issue that the switch is detected and you can capture images on port 0 but the other ports are unavailable.

Regards,

[althaf]

Hi Joseph,

Thank you for the update.

Could you please clarify the exact issue you're encountering? We would like to confirm if we are facing the same problem. Additionally, could you provide an estimated release date for the version that includes this fix?

If possible, could you share any details about the fix? This would help us create a patch on our side, as we are currently blocked due to this issue.

I appreciate your help and await your reply.

regards,

[JosephAtNXP]

Hi,

Thank you for your interest in NXP Semiconductor products,

This issue was already replicated by the validation team. The SW team is working on this and in the next release this could be fixed, the current driver is alright working with the hub port 0.

Regards