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.

DS90LV011AQ-Q1: If the the ds90lv011a can drive the logic to tri-state with reciever ds90lv012a?

Part Number: DS90LV011AQ-Q1
Other Parts Discussed in Thread: PCMD3140, DS90LV012A, DS90LV011A, SN65LVDS390, SN65LVDS180, DS10CP152

Tool/software:

Hello TI,

I was designing an audio project with PDM DMIC that needs long wires transmission, it's about 2 meters length distance. For the purpose of long distance transmission, I submitted a propose as below block shows, four DMICs with a PDM interface are connected to TI's PCMD3140 through the TTL2LVDS and LDVS2TTL, which are  ds90lv011a and ds90lv012a respectively. The problem is that when a PDM data line, the red or blue line in the diagram, is shared by two drivers output, the bus logic conflict would happen. The original PDM DMIC can share a data line, because the the driver can put the data line to tri-state after a period of time, until the other driver output a vlue to the line. My question is that if the ds90lv011a and ds90lv012a could drive the output to tri-state at the sharing data line? If not, is there a appropriate LVDS solution to be used in this application?

B/R

Zou

  • Zou,

    An engineer has been notified of this post and will respond by end of business 01/22/2025.

    Regards,

    Eric Hackett 

  • Hi Zou,

    The DS90LV012A does not have the ability to tri-state its output. We do have some multichannel LVDS receivers such as the SN65LVDS390 with output enables to tri-state the output. We also have LVDS transceivers with driver/receiver enables such as the SN65LVDS180.

    We also offer LVDS crosspoint switches which can be used to multiplex two LVDS buses such as the DS10CP152.

    Another solution could be to move to multipoint LVDS (M-LVDS) and have a configuration where multiple drivers sit on the same M-LVDS bus. There is no bus arbitration at the M-LVDS level, so control over driver enables must still be handled externally to avoid bus contention. M-LVDS can be read about in this App Note.

    Regards,

    Jack