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.

SN65DSI83: SN65DSI83: MIPI DSI 1 to RGB getting started

Part Number: SN65DSI83
Other Parts Discussed in Thread: SN65LVDS822,

Hello Team,

as MIPI DSI 1 to RGB solution we do have the SN65DSI83 + SN65LVDS822

  • Both parts have the evaluation board, do we have any reference design that use the two parts together?

   This would help to better understand what is needed to make them work, and the required space.

I2C bus requirements

  • The start up configuration for the PHY needs necessarily a configuration with the I2C or the start up values are ready to be used?
  • Are there any bootstrap configurations available without the need of I2C?
  • In short, can we avoid using the I2C or is it a must to control it before using the PHY?
  • Do we have the Linux driver for the I2C PHY control?

Thanks for the follow up,

SunSet

  • Hi SunSet,

    We don't have a reference design using these two parts. You can combine the SN65DSI83 with just about any LVDS deseriailzer. In the past I have connected the EVMs together for customer debug purpose (needed to see the HSYNC/VSYNC signals coming out of the DSI83 so I needed a deserializer) and I could see the output signals from the LVDS822 fine on an oscilloscope.

    The DSI83 requires I2C control to configure the registers. The device will not be operational without I2C. We don't have reference Linux driver code.

    Regards,

    I.K. 

  • Thanks for the feedback.

    For the Linux driver they may probably use the standard Linux I2C driver and build on top a simple code to access the specific registers.

    Thanks,

    SunSet