This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DS90UB960-Q1: Configuring Deserializer Pattern without Connecting Serializer and Camera sensors.

Part Number: DS90UB960-Q1

Tool/software:

Hello,

We are currently working with the mainline driver version 10.6 and deserializer - ti,ds90ub960-q1, where media0(media-ctl) successfully enumerates when the serializer and camera sensors  are connected. However, if the serializer and cameras are not connected, the driver fails to enumerate media0.

Our requirement is to generate the deserializer pattern without needing to connect the serializer and camera sensors. 

Any help or suggestions would be greatly appreciated!

Thank you.

  • Hello,

    Thanks for reaching out. Please note that we can only support FPD-Link devices on this forum and not any detailed driver specific development or debugging. With that being said, it is possible to output the deserializer pattern generator without a serializer connection. Is the media0 enumeration failure blocking the pattern generation programming from occurring? To write to the registers and enable the pattern only I2C access is needed. Does the driver have the ability to perform these I2C writes independent of the media0 enumeration?

  • Hello,

    Please find the details below:

    - Is the media0 enumeration failure blocking the pattern generation programming from occurring?

    Yes, the deserializer and CSI driver are linked using the command media-ctl -d /dev/media0 --link "xxxx". Without this link, attempting to capture the pattern results in a broken pipe error.

    - Does the driver have the ability to perform these I2C writes independent of the media0 enumeration? 

    Yes, the driver can perform I2C writes independently of the media0 enumeration. However, in order to execute the V4L2 capture command, the link between the deserializer, CSI, serializer, and sensor must be established. This requires manually enabling the CSI-deserializer link using the command media-ctl -d /dev/media0 --link 'deserializer -> csis'. Currently, we are unable to set up the links due to the media0 enumeration failure.

    -Other observation:

        Media0 fails to enumerate if one of the serializers is not connected.

  • Hello,

    If the driver is gated by not having lock between the deserializer and serializer, and manual I2C is gated as well, there are not many options to generate the pattern (outside of a secondary connection on the I2C port that would work separate from the driver). To achieve lock, the deserializer must be connected to a serializer. It seems that either the driver will need to be updated to remove the lock dependency, or a serializer will need to be added to the system.