1. Field of the Invention
The present invention relates to high speed data communication (e.g., 1 G-bit/second or higher). In particular, the present invention relates to a bidirectional data communication protocol for communicating between a serializer and a deserializer.
2. Discussion of the Related Art
Transmitting a multi-bit data word in parallel over a number of conductors is costly because each transmitted bit requires a transmitter and a receiver circuit, in addition to the many conductors in a parallel cable. In addition, the bits of the data word may arrive at the receiver skewed or delayed in time relative to each other. The data rate is therefore limited by any margin of error that must be provided to compensate for such skews. One method in the prior art to avoid the high cost of parallel data transmission serializes the parallel data at the transmitter into a single data stream and deserializes the data stream back into parallel data at the receiver. In many applications, a small amount of control information (relative to the data transmitted) may still be required from the receiver. The cost savings of serialization is partly offset by providing a separate channel for sending such control information in the opposite direction.
According to one embodiment of the present invention, a method for providing a bidirectional communication protocol between a first device and a second device includes: during a first time interval, transmitting data from the first device to the second device; and during a second time interval, (a) after the occurrence of a first event, (i) suspending data transmission from the first device to the second device; and (ii) transmitting control data from the second device to the first device; and (b) after the occurrence of a second event, transmitting control data from the first device to the second device.
According to one embodiment of the present invention, the method for providing the bidirectional communication protocol is implemented between a data source and a data sink. In one implementation, the data source may be a video data source, such as a DVD player, and the data sink may be a video display.
The present invention is better understood upon consideration of the detailed description below and the accompanying drawings.
The present invention provides a bidirectional communication protocol between a serializer and a deserializer, sending data and control information in both directions over the same serial communication channel.
One application of the present application may be data transmission between a video decoder (e.g., a DVD player) and a video display system (e.g., an LCD monitor).
As shown in
Serializer/deserializer circuit 100 includes a receiver circuit for receiving data in the reverse direction from the communication channel. The receiver circuit includes equalizer 107, which further compensates for distortion in the communication channel. Clock recovery circuit 108 recovers the 30× system clock signal, which is used to provide the 1×, 3× and 30× clock signals used in the receiver circuit. The received serial data stream is deserialized in deserializer 109 into a 10-bit data stream, which is decoded by 8/10b decoder 110 according to the coding scheme back to an 8-bit data stream. From this decoded 8-bit data stream (at three times data rate), demultiplexer 111 recovers the 3× 8-bit data stream and the control data stream. The video data control signals (i.e., V_SYNC, H_SYNC and DE) are also recovered from special characters in the 10-bit encoded data stream by receiver controller 114. The individual input 8-bit data streams are recovered in 3-1 deserializer 112 from the 3× 8-bit data stream. Clock randomizer circuit 115 modulates the individual data signals and the 1× clock signal to reduce electromagnetic interference (EMI). The control data to be transmitted and the control data received are stored respectively in registers 113a and 113b respectively. The control data may originate from or be directed to devices attached to an I2C interface bus.
In the above description, serializer/deserializer circuit 100 operates in a 24-to-1 mode (i.e., serializing three 8-bit data streams). Serializer/deserializer circuit 100 may also operate in a 16-to-1 data mode. Data may be grouped under either mode in units of “pixel”. Under 24-to-1 mode, each pixel consists of three 8-bit bytes encoded to three 10-bit characters, and under 16-to-1 mode, each pixel consists of two 8-bit bytes encoded to two 10-bit characters.
According to one embodiment of the present invention, control data are exchanged between the serializer and the deserializer during the time when V_SYNC is active. V_SYNC is normally active for at least two H_SYNC intervals—each interval being the time between H_SYNC pulses. The first H_SYNC interval during a V_SYNC active period is provided for sending control data from the deserializer to the serializer (i.e., in the reversed direction from the main traffic) and the second H_SYNC interval in the V_SYNC period is provided for sending control data from the serializer to the deserializer (i.e., in the direction of the main traffic).
In the event of a premature termination of the V_SYNC active period (i.e., the V_SYNC active period lasting less than 2H_SYNC intervals), the control information is still exchanged as if the V_SYNC active period lasts two H_SYNC intervals. In this situation, some data in the main traffic may be lost. In this instance, the deserializer maintains V_SYNC high for the two H_SYNC intervals, providing substitute values (e.g., zero) for the data in the main traffic.
As shown in
In the second H_SYNC interval during the active V_SYNC period, control data from the serializer is sent to the deserializer. This control data consists of a data packet which is preceded by eight preamble symbols and followed by as many preamble symbols as required until the end of the second H_SYNC interval, as indicated by the arrival of the next H_SYNC pulse. The control data flow during this second H_SYNC interval is shown in Table 5 of
As shown in
In this embodiment, the preamble symbol, the end of transmission symbol, and the data packet use a number of special characters defined in Table 2 of
The detailed description above is provided to illustrate the specific embodiments of the present invention and is not intended to be limiting. Numerous variations and modifications within the scope of the present invention are possible. The present invention is set forth in the following claims.
The present application is related to and claims priority to (a) copending U.S. provisional patent application, entitled “Bidirectional Communication Protocol Between a Serializer and a Deserializer,” Ser. No. 60/822,287, filed on Aug. 14, 2006; and (b) copending U.S. provisional patent application, entitled “Bidirectional Communication Protocol Between a Serializer and a Deserializer,” Ser. No. 60/862,001, filed on Oct. 18, 2006. The disclosures of the copending provisional applications are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
6020901 | Lavelle et al. | Feb 2000 | A |
6914637 | Wolf et al. | Jul 2005 | B1 |
7440702 | Imai | Oct 2008 | B2 |
7548675 | Tatum et al. | Jun 2009 | B2 |
7742438 | Xu et al. | Jun 2010 | B1 |
8000350 | Riedel et al. | Aug 2011 | B2 |
20030043142 | Ishibashi | Mar 2003 | A1 |
20030169831 | Neugebauer et al. | Sep 2003 | A1 |
20040080523 | Myers | Apr 2004 | A1 |
20040174466 | Kwon | Sep 2004 | A1 |
20050219083 | Boomer et al. | Oct 2005 | A1 |
20060067690 | Tatum | Mar 2006 | A1 |
20060179201 | Riedel et al. | Aug 2006 | A1 |
20060200585 | Weigert | Sep 2006 | A1 |
20060227809 | Miller | Oct 2006 | A1 |
20070009060 | Lavelle et al. | Jan 2007 | A1 |
20070011552 | Altmann | Jan 2007 | A1 |
20080317181 | Suzuki et al. | Dec 2008 | A1 |
Number | Date | Country |
---|---|---|
1540913 | Oct 2004 | CN |
1 416 687 | May 2004 | EP |
1 471 434 | Oct 2004 | EP |
WO2005091543 | Sep 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20080040765 A1 | Feb 2008 | US |
Number | Date | Country | |
---|---|---|---|
60822287 | Aug 2006 | US | |
60862001 | Oct 2006 | US |