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.

DS90UB947-Q1: Solution required for usage of serializer/deserializer chip in LVDS display and touch interface with IMX8QM

Part Number: DS90UB947-Q1
Other Parts Discussed in Thread: DS90UB948-Q1

Hello Team TI,

We (Teksun Inc) currently working on an automotive infotainment display. Our current setup is nxp imx8qm processor (with AOSP) and LVDS display, which is working fine. Our next milestone is to make the display work with the long distance setup between processor and display. We found a similar solution on TI, where the processor gives signals to serialize chip, and it forwards the signals to deserialize chip with display data and I2C data.

We took reference from DS90UB947-Q1 Serializer and DS90UB948-Q1 Deserializer datasheet.

Our end application is to work with LVDS display with touch - I2C with a long distance from the processor. I am attaching the flow of solution, What we required from you is to check the solution and tell us if it is OK to fit in our requirements.

If your answer is yes, then please provide as AOSP patch/solution and document for how to proceed with the above solution.

Looking forward to your quick and positive response.

Regards,

  • Hi Vedant,

    The DS90UB947-Q1 and the DS90UB948-Q1 are compatible and both respectively input/output with an OpenLDI interface. I am not sure what other requirements you are asking about, only your block diagram was attached.

    Regards,

    Ben

  • Hi Ben,

    Thank you for the quick response.

    I hope you are understanding our solution from the diagram.

    My query is,

    1) What changes needs to be done for adding Linux device driver (of Serializer and Deserializer) in kernel driver and device tree.

    2) What changes/patches needs to be added for our LVDS touch driver, in current flow our touch driver is added in kernel driver and device tree but if we are using SerDes solution, touch ic is not in direct connection with processor as the Serializer's I2C is handling the touch response, So how to configure the touch driver (which is on Deserializer side) and how to make it work it in runtime with reference to Serializer's I2C is handling it.

    I hope you understand my question. Let me know if you still have doubt.

  • Hello Ben,

    It will be batter if you can provide us Linux device driver of DS90UB947-Q1 Serializer for Linux kernel version 5.4 which can full fill our requirement mention in the diagram.

  • Hi Vedant,

    Unfortunately we do not provide Linux drivers for these devices. As for the touch support capabilities, usually the interrupt pins are used for this function. This will have to be set up via registers. See this section from the 948 datasheet:

    Regards,

    Ben