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.

SN65DPHY440SS: Is Suitable considering low MIPI clock and lengthy cable:

Part Number: SN65DPHY440SS

Hi TI Team,

In my new project , i have a length cable of 35cm which will carry MIPI DSI signals. and roughly 6 inch of other trace will be there in PCB between DSI source to DSI sink.

Here we will be driving an LCD of 320x480 resolution, so roughly will have lower clock speed <100MHz. But to be at safer side i am planning to put this MIPI DSI retimer part# SN65DPHY440SS 

Below are my queries for the same:

1) Is it suitable to my application considering above requirements?

2) Is it ok to use MIPI clock below 100MHz, As per datasheet it mentions Min clock of 100Mhz so?

3) Is this solution possible to have standalone? Or I2C interface is must required to be interfaced ?

4) What should be the configuration setting considering below length details.

MIPI DSI Source-->4Inch Trace in PCB: -- - - >35cm cable length-- - ->3Inch Trace in PCB--> MIPI DSI Sink (LCD) 

Awaiting your quick and valuable support on this.

  • Will be placing the SN65DPHY440SS after 35cm cable length and Near to MIPI DSI sink (LCD).

  • Hi,

    The DPHY440 can not support clock frequency below 100MHz and its functional behavior at below 100MHz can not guaranteed.

    If using the DPHY440, I would agree with your response that the DPHY440 needs to be placed after the 35cm cable so the DPHY440 can compensate for the 35cm cable loss.

    The DPHY440 can be operated stand-alone. If needed, it can also be operated in I2C mode.

    Thanks

    David

  • Thanks for the details,

    Here just a quick question, as per 320x480 LCD resolution (262k color depth, Will be using single Data Lane only) configuration we done rough calculation, which was less than 100MHz.

    Here MIPI clock (100MHz) has to be Bit clock as per calculation or Byte clock?

    1) Is it ok if we drive that LCD with higher clock = 250MHz, (which is supported by LCD controller)?

    2) Do you have any calculation reference for MIPI clock frequency? So that we can confirm our required operating freq.

    3) Instead of this is it possible to use an LVDS differential buffer IC for this MIPI signals?

  • Hi,

    What is the refresh rate for this resolution?

    So the calculation is

    Pixel Clock Frequency = Total Horizontal Samples * Total Vertical Lines * Refresh Rate

    Total Data Rate (Bandwidth) = Pixel Clock Frequency * Pixel Size (in bits). Pixel Size is 18-bits for 262k color depth.

    Data Rate per Lane = Total Data Rate (Bandwidth) / Number of Data Lane

    MIPI Bit Clock Frequency = Data Rate per Lane / 2

    Thanks

    David

  • OK Thanks for the details calculation referecne.

    David,

    1) Can you also help me to derive the Total Pixel freq considering the following LCD configuration. 

    - Pixel pitch: 0.0286x0.0286mm

    - Active Area: 27.456 x 41.184mm

    - Resolution: 320 x RGB x 480

    - Size: 1.95inch

    - MIPI Data Lane: 1

    2) What is the minimum freq used for this DPHY440?

  • Hi,

    Do you know what is the refresh or frame rate for this LCD? 

    Assume frame rate is 60Hz

    Pixel frequency = 320 x 480 x 60 = 9.216MHz

    Total data rate = 9.216 * 18 = 165.888Mbps

    Data rate = 165.888Mbps

    MIPI clock frequency = data rate / 2 = 82.944MHz

    So it appears that with 60Hz frame rate, the MIPI clock frequency is below the DPHY440 minimum clock frequency requirement.

    Thanks

    David

  • Yes, David. LCD frame rate is 60Hz.

    But as per processor driver calculation. It doesn't mention to divide the data rate /2 considering DDR.

    So, overall calculation was as below:

    Total pixel clock= (Hz active+Hz front porch+ Hz back porch+ Hz Sync length) x (Vt active+Vt front porch+ Vt back porch+ Vt Sync length) x 60

    Hz= Horizontal and Vt = Vertical.

    Total Pixel clock= (320+38+100+4) x (480+8+8+4) x60

    Total Pixel Clock= 13.86MHz

    Total data lane=1 and bit per pixel =18 so.

    Total Data rate = 13.86 x 18 = 249.48Mbps,

    MIPI clock= 249.48MHz (considering not deviding by 2 for DDR)

    Or else MIPI clock= 124.74MHz (If devided by 2)

    Which comes above 100MHz, So we are considering the DPHY440 solution. Do you see any issue in above calculation?

  • Hi,

    The calculation is correct.

    Thanks

    David

  • HI DAVID,

    Thanks for your support,

    As we have only 1 data lane in MIPI DSI, Can we use DATA lane 02 of DPHY440? or is it must to use Data lane 0 only.

  • Hi,

    The DPHY440 supports up to 4 DSI DPHY lanes and a clock lane. One of the four lanes is used for back channel communications between GPU and DSI panel. DPHY440’s lane 0 is the only lane that supports the back channel. For this reason, DPHY440 lane 0 must always be connected to lane 0 of GPU and panel.

    The DPHY440’s LP TX is expecting to connect to an unterminated LP RX.  With Lane 0 path (DA0P/N and DB0P/N) supporting bi-directional LP signaling, please make sure that LP TX is connected to an unterminated LP RX.  If LP TX is connected to a HS RX, then LP signaling will not be able to reach the LP11 levels and which will cause the DPHY440 to not enable HS data path on Lane0.

    You can use I2C to force the lane into HS path

    Try following for enabling lane0 HS path:

    Enable HS path for Lane 0 only:

    Write Register 0x50 with 8’h01 //Override enable for HS TX path

    Write Register 0x51 with 8’h01 //HS TX path enabled.

    Write Register 0x61 with 8’h00  // Disable LP path.

    Write Register 0x70 with 8’h01  //Override enable for HS RX path

    Write Register 0x71 with 8’h01  // HS RX path enabled.

    Thanks

    David