Redriver with switchable linear and limited modes
Patent Information
- Application Number
- JP2023528380
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-06-30
- Filing Date
- 2021-11-12
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-11-12
AI Technical Summary
HDMI 2.1 source devices face reliability issues during link training when connected to HDMI 1.4 or 2.0 sink devices due to the use of restrictive redrivers, which are not transparent to link training procedures, leading to increased failure risks.
A redriver system with a snoop circuit that monitors channel capabilities and configures itself for either linear or limited modes based on the HDMI protocol version of connected devices, ensuring reliable link training by enabling or disabling appropriate transmitter drivers.
Ensures reliable link training and compatible data transmission between HDMI 2.1 source devices and devices of earlier versions by dynamically adjusting redriver modes, enhancing compatibility and reducing transmission errors.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Background technology]
[0001] In the context of a first device transmitting data (e.g., video and / or audio) to a second device, each device may conform to a given interface protocol. For example, the first device may be a video source (e.g., a cable box, an internet-connected streaming device, a computer, etc.), the second device may be a display monitor, and each device may implement a High Definition Multimedia Interface (HDMI). An HDMI-implemented source device transfers both high definition audio and video over a single cable to an HDMI-compliant sink device. The source device may also include a redriver, which is a circuit that implements equalization to reduce inter-symbol interference (ISI). Summary of the Invention
[0002] In one example, a redriver system is adapted to couple to a first device and a second device and includes first and second transmitter drivers and a snoop circuit. The first transmitter driver has a first enable input. The second transmitter driver has a second enable input. The snoop circuit is coupled to the first and second enable inputs. The snoop circuit determines whether the first device and the second device operate according to a first protocol. In response to the snoop circuit determining that the first and second devices operate according to the first protocol, the snoop circuit enables the first transmitter driver and disables the second transmitter driver. In response to the snoop circuit determining that the first and second devices do not operate according to the first protocol, the snoop circuit disables the first transmitter driver and enables the second transmitter driver.
[0003] In another example, a method includes determining whether a first device and a second device operate according to a first protocol. The method includes enabling a first transmitter driver and disabling a second transmitter in response to determining that the first and second devices operate according to the first protocol. The method includes disabling the first transmitter driver and enabling the second transmitter in response to determining that the first and second devices operate according to a protocol other than the first protocol. [Brief explanation of the drawings]
[0004] For a detailed description of various examples, reference is made to the accompanying drawings.
[0005] [Figure 1] 1 is a block diagram illustrating a source device coupled to a sink device and including a redriver system capable of either a linear or limited mode of operation, according to certain examples.
[0006] [Figure 2] FIG. 1 is a block diagram of a transmitter in a redriver system having both linear and limited transmitters, according to an example.
[0007] [Figure 3] 4 is a state diagram illustrating operational states of a snoop circuit in a redriver system, according to an example.
[0008] [Figure 4] 4 is a flowchart illustrating an exemplary method implemented by a snoop circuit.
[0009] The same reference numbers or other reference designators are used in the drawings to indicate the same or similar (functional and / or structural) features. DETAILED DESCRIPTION OF THE INVENTION
[0010] An HDMI driver can be either a "linear" redriver or a "nonlinear" redriver. A nonlinear redriver is also referred to as a limiting redriver. A linear redriver implements an approximately linear relationship between the input signal (e.g., voltage) to the redriver and its output signal, at least over the range of interest. However, a limiting redriver implements pre-emphasis and amplitude control so that its output signal is not a linear function of its input signal.
[0011] Several versions of the HDMI protocol have been established, including HDMI 1.4, HDMI 2.0, and HDMI 2.1. Each of these HDMI specifications is incorporated herein by reference in its entirety. The HDMI 1.4 protocol provides a maximum data rate of 10.2 gigabits per second (Gbps). HDMI 2.0 provides a maximum data rate of 18 gigabits per second (Gbps). Both HDMI 1.4 and 2.0 specify the Transition Minimized Differential Signaling (TMDS) encoding technique, in which a clock signal is transmitted along with video and audio signals on the conductors of an HDMI cable. The HDMI 2.1 protocol provides even faster data transfer rates (e.g., up to 48 Gbps). HDMI 2.1 does not include transmission of a clock signal between source and sink devices, reusing the clock pin used in HDMI 1.4 and 2.0 as an additional data channel.
[0012] When two HDMI-compliant devices are connected and powered on, the source device obtains device-related data from the sink device. The device-related data includes, for example, Extended Display Identification Data (EDID), an HDMI Forum Vendor-Specific Data Block (HF-VSDB), and a Status and Control Data Structure (SCDCS), which are stored in the sink device's non-volatile memory. The sink device's EDID specifies parameters such as the sink device's display dimensions, chromaticity values, and timing values. The HF-VSDB includes the sink device's maximum data rate capabilities and other device-specific data relevant to the sink device. The source device uses the sink's device-specific data to determine the capabilities of the sink device and then selects a display resolution, data rate, etc. that matches the capabilities of both the source device and the sink device. The source device then writes values to the sink's SCDCS to specify the common capabilities (resolution, data rate, etc.) determined by the source device to the sink device, thereby controlling the interaction between the source device and the sink device.
[0013] HDMI 2.1 also provides "link training" between source and sink devices. Link training was not implemented in previous versions of HDMI (e.g., HDMI 1.4 and 2.0). The purpose of link training is for the source device to configure itself for the appropriate level of pre-emphasis, voltage swing, etc., with the goal of reducing or eliminating errors. The link training procedure is initiated and controlled by the source device. During the link training procedure, the sink device recovers the source device's clock, which is embedded in the data channel. The source device also sends test patterns to the sink device. The test patterns cause the source device to adjust its transmitter swing, pre-shoot, and de-emphasis levels to values that may result in a more robust signal to the sink device, thereby reducing or eliminating errors observed by the sink device. Unfortunately, the link training procedure does not work reliably with source devices that use limiting redrivers. Using limiting redrivers during link training, when the graphics processing units (GPUs) of the sink and source devices are unaware of the presence of the limiting redriver, increases the risk of link training failure. A linear redriver is transparent to link training and therefore has little or no impact on link training, so the link training procedure is more reliable when a linear redriver is used in the source device instead of a limiting redriver.
[0014] The HDMI protocol is backward compatible, meaning that any pair of HDMI-compliant source and sink devices will work together, regardless of which version of HDMI they implement. For example, an HDMI 2.1 source device can be connected to an HDMI 1.4 sink device, an HDMI 2.0 sink device, or an HDMI 2.1 sink device. This means that when an HDMI 2.1 source device is connected to an HDMI 2.1 sink device, the source device can perform link training. However, when an HDMI 2.1 source device is connected to an HDMI 1.4 or 2.0 sink device (other versions of HDMI released before HDMI 2.1), the HDMI 2.1 source device cannot perform the link training protocol because pre-HDMI 2.1 sink devices lack this capability.
[0015] Embodiments described herein are directed to a redriver system having both linear and limited redriver modes of operation. The redriver system includes a snoop circuit that monitors a channel between a source device and a sink device, where the capabilities of the sink device are read by the source device, and the source device writes values back to the sink device as part of the process in which the source and sink devices negotiate a set of parameters related to display resolution, pre-emphasis, voltage swing, etc. In one embodiment, the snoop circuit of the redriver system snoops one or more values that the GPU of the source device writes to the sink device regarding the mutual capabilities that the source device has specified for operation of these devices. Based on the snooped information, the snoop circuit determines whether the source and sink devices should configure themselves to operate according to the HDMI 2.1 protocol or a protocol other than HDMI 2.1 (e.g., a protocol prior to HDMI 2.1, such as HDMI 1.4 or HDMI 2.0). If the snoop circuit determines that the source device and the sink device operate according to the HDMI 2.1 protocol, the snoop circuit configures the redriver system for a linear redriver mode. If the snoop circuit determines that the source device and the sink device do not operate according to the HDMI 2.1 protocol, the snoop circuit configures the redriver system for a restricted redriver mode.
[0016] FIG. 1 is a block diagram of a system 100 including a source device 110 coupled to a sink device 160 by a cable 150. In one example, the source device 110 contains or otherwise acquires audio and / or video data (referred to herein as “media” data) and provides the media data to the sink device via the cable 150. The source device 110 may be a computer, a set-top box, a cable box, a WiFi streaming device, etc. The sink device 160 may be a display monitor or other type of device that consumes / displays media data. The sink device 160 includes a memory 170 in which the sink device's EDID 165, SCDCS 167, and HF-VSDB 168 are stored. The memory 170 may be non-volatile memory. The SCDCS 167 may be stored in a memory that is both readable and writable. The EDID 165 and HF-VSDB 168 may be stored in read-only memory (e.g., read-only memory, “ROM”).
[0017] In the examples described herein, source device 110 and sink device 160 are HDMI compliant. Source device 110 is an HDMI 2.1 device and is therefore compatible with HDMI 2.1 sink devices and backward compatible with sink devices that comply with earlier versions of HDMI (e.g., HDMI 1.4 or HDMI 2.0). Source device 110 may be an HDMI 2.1 device, and sink device 160 may be an HDMI 2.1 device, or may comply with earlier versions of HDMI, such as HDMI 1.4 or 2.0. A device's HDMI version means that the device can operate either according to the specified version or according to earlier versions of HDMI. For example, an HDMI 2.0 device can operate according to the HDMI 2.0 or 1.4 protocol, but cannot operate according to the HDMI 2.1 protocol. During the discovery process, in which source device 110 reads the sink device's EDID 165, SCDCS 167, and HF-VSDB 168, source device 110 determines the parameters (e.g., data rate, resolution, etc.) under which both the source device and the sink device will operate. For example, if source device 110 is HDMI 2.1 compatible and the sink device is HDMI 2.0 compatible, the source device determines that both devices should configure themselves for HDMI 2.0 operation. Thus, while source device 110 is HDMI 2.1 compatible, the source device configures itself for HDMI 2.0 operation.
[0018] 1 includes a graphics processor unit (GPU) 112 coupled to a redriver system 130. Cable 150 is an HDMI-compliant cable and includes four twisted wire pairs 151, 152, 153, and 154. Each pair of twisted wires is for an individual channel. In HDMI 1.4 and 2.0, three of the channels are used for video and / or audio data, and the fourth channel is used for a clock. In HDMI 2.1, there is no separate clock signal transmitted over cable 150, so all four channels can be used for data. A serial communication link (e.g., Inter-Integrated Circuit (I2C)) via wire 156 is also provided over cable 150 between the sink device and the source device, through which GPU 112 can read the sink device's EDID 165, SCDCS 167, and HF-VSDB 168 and provide parameter values back to the sink device to be stored in HF-VSDB 168. Wire 156 may be a single wire or a pair of wires, such as a clock wire and a serial data wire. The communication link over wire 156 is sometimes referred to as a display data channel (DDC). Cable 150 also includes a hot plug detect (HPD) wire 155 that allows source device 110 to detect whether cable 150 is connected to a powered-on sink device 160.
[0019] 1, all signals provided over cable 150 between sink device 160 and GPU 112 (in source device 110) flow through redriver system 130. In other examples, one or more of these signals may bypass redriver system 130 (e.g., DDC information on wire 156 may not pass through redriver system 130).
[0020] 1 , GPU 112 includes four transmitters 115, 116, 117, and 118 corresponding to each of the four data channels (or three data channels and one clock) mentioned above. Sink device 160 has four corresponding receivers 161, 162, 163, and 164 coupled to logic 169. Logic 169 may include a processor, digital logic, an application specific integrated circuit (ASIC), memory, and / or any other type of circuit element that receives, processes, and consumes media data from source device 110. Logic 169 provides the media data to display 173. Display 173 may be coupled to sink device 160 or may be a component of the sink device. Display device 173 may include one or more speakers for playing audio.
[0021] Redriver system 130 includes four equalizer / transmitter pairs. Equalizer 131 is coupled to transmitter 141. The output of transmitter 115 is coupled to the input of equalizer 131, and the output of transmitter 141 is coupled to the input of receiver 161 in sink device 160 via wire 151 in cable 160. Equalizer 132 is coupled to transmitter 142. The output of transmitter 116 is coupled to the input of equalizer 132, and the output of transmitter 142 is coupled to the input of receiver 162 in sink device 160 via wire 152 in cable. Equalizer 133 is coupled to transmitter 143. The output of transmitter 117 is coupled to the input of equalizer 133, and the output of transmitter 143 is coupled to the input of receiver 163 in sink device 160 via wire 153 in cable. Equalizer 134 is coupled to transmitter 144. The output of transmitter 118 is coupled to the input of equalizer 134, and the output of transmitter 144 is coupled via wire 154 in the cable to the input of receiver 164 in sink device 160. In one example, wires 151, 152, 153, and 154 are each twisted wire pairs.
[0022] In one example, GPU logic 114 includes a processor, memory, and / or other digital circuitry configured to execute software. In another example, logic 114 is a discrete digital circuit. Logic 114 causes media data to be transmitted via transmitters 115-118, through corresponding equalizer / transmitter pairs in redriver system 130, and to receivers 161-164 in sink device 160. Source device 110 may have storage containing media data 119 that is provided to sink device 160 via one or more of transmitters 115-118. Media data 119 may be retrieved by logic 114 from a disc (e.g., a Blu-ray disc, a DVD disc, a CD-ROM, etc.), or the media data may be streamed from a network (e.g., from the Internet) to sink device 160 via GPU 112.
[0023] In one embodiment, GPU 112 is implemented as an integrated circuit (IC) that includes GPU 112 and redriver system 130 on the same semiconductor die. In another embodiment, redriver system 130 is implemented as a separate IC from the IC on which GPU 112 is implemented. Thus, GPU 112 may be on one IC and redriver system 130 may be a separate IC, with both ICs included as part of source device 110. For example, the ICs forming GPU 112 and redriver system 130 may be mounted on a printed circuit board (PCB) within source device 110.
[0024] The HDMI protocol implements a hot plug detect (HPD) capability that allows a source device and a sink device to be connected via cable 150 while both are powered on. On the source device 110 side of cable 150, source device 110 includes a pull-down resistor R1 that couples wire 155 to ground. In the embodiment of FIG. 1 , pull-down resistor R1 is included within redriver system 130. In another embodiment, pull-down resistor R1 is external to redriver system 130. The HPD signal (the voltage across resistor R1) is logic low when the cable is not connected or when the cable is connected but sink device 160 is not powered on. When cable 150 is connected and sink device 160 is powered on, the HPD signal is pulled high (above a threshold) because the HPD line within sink device 160 is appropriately tied to a high voltage source (not shown). A buffer 149 is provided within redriver 130 to drive the HPD signal to logic 114 within GPU 112. By monitoring the logic level of the HPD signal, logic 114 can determine whether a powered sink device 160 is cable-connected to source device 110 .
[0025] As described above, the HDMI protocol provides a DDC interface between a source device and a sink device. In one example, the DDC interface is a protocol implemented over a serial data link through wires 156 of cable 150. Over wires 156, EDID 165, SCDCS 167, and HF-VSDB 168 are provided from sink device 160 to GPU 112, which writes one or more parameter values back to the sink's SCDCS 167. Logic 114 of GPU 112 issues one or more read requests to sink device 160 to read EDID 165, SCDCS 167, and HF-VSDB 168 from memory 170 of the sink device. GPU logic 114 issues this read request, for example, in response to logic 114 detecting a logic low to logic high transition on the HPD input.
[0026] Redriver system 130 includes a DDC transceiver 147 that receives and decodes DDC bidirectional traffic communicated between source 112 and sink device 160. For example, requests from GPU logic 114 to read EDID 165, SCDCS 167, and HF-VSDB 168 are forwarded to sink device 160 via DDC transceiver 147, and the read data (EDID, SCDCS, and HF-VSDB) from sink device 160 is returned to logic 114 via DDC transceiver 147. Logic 114 also writes one or more parameters back to SCDCS 167 of sink device 160 via transceiver 147. Redriver system 130 also includes DDC snoop circuit 148 that monitors bidirectional traffic through DDC transceiver 147 for a set of predetermined packets that indicate whether source device 110 enables source device 110 and sink device 160 for the HDMI 2.1 protocol or for a protocol other than HDMI 2.1 (e.g., HDMI 1.4 or HDMI 2.0).
[0027] GPU 112 (e.g., logic 114) reads EDID 165, SCDCS 167, and HF-VSDB 168 from memory 170 of the sink device. HF-VSDB 168 includes a value called Max_TMDS_Character_Rate and a value called Max_FRL_Rate. Transition-Minimum Differential Signaling (TMDS) is a technique for transmitting high-speed digital data while reducing electromagnetic interference (EMI), enabling clock recovery over relatively long distances, for example, up to 100 feet. TMDS is implemented as part of HDMI 1.4 and 2.0, but not 2.1. Max_TMDS_Character_Rate is the maximum TMDS character rate supported by sink device 160. In one example, if sink device 160 does not support TMDS character rates greater than 340 Megacharacters per second (Mcsc), Max_TMDS_Character_Rate is set to 0; otherwise, this field is non-zero and indicates the maximum TMDS character rate supported by the sink device. The Max_TMDS_Character_Rate value is, for example, an 8-bit value in byte number 5 of HF_VSDB 168.
[0028] Fixed Rate Link (FRL) is a signaling protocol specified in HDMI 2.1, but not in earlier versions of HDMI (e.g., not in HDMI 1.4 or 2.0). The Max_TMDS_Character_Rate value is, for example, a 4-bit value in byte number 7 of HF_VSDB168. Max_FRL_Rate indicates the level of FRL possible at the sink device. A Max_FRL_Rate value of 0 means that Fixed Rate Link is not supported by the sink device. A non-zero Max_FRL_Rate indicates the data rate of the various lanes. Table 1 below contains the possible values of Max_FRL_Rate according to the HDMI specification. TIFF2023549501000002.tif6862
[0029] Among other values, the GPU 112 reads the Max_TMDS_Character_Rate and Max_FRL_Rate values from the sink device's HF-VSDB 168 to determine the capabilities of the sink device 160. Based on these values, the GPU 112 determines the capabilities shared by both the source and sink devices. Based on this determination, the GPU 112 writes values to the sink device's SCDCS 167. For example, the GPU 112 determines a bit called TMDS_Bit_Clock_Ratio and a 4-bit value called FRL_Rate, and writes these to the sink device's SCDCS 167. The TMDS_Bit_Clock_Ratio bit is, for example, bit number 1 of the TMDS configuration byte at offset 0x20 in the SCDCS 167. The TMDS_Bit_Clock_Ratio bit defaults to a value of 0, indicating that the ratio between the TMDS bit period and the TMDS clock period is 1 / 10. However, the GPU 112 may set the TMDS_Bit_Clock_Ratio bit to 1 to specify that the ratio of the TMDS bit period to the TMDS clock period is 1 / 40.
[0030] The FRL_Rate value is, for example, bits [3:0] of the sink configuration byte at offset 0x31 in SCDCS 167. The FRL_Rate field defaults to a value of 0, indicating that the sink device does not support FRL signaling. However, GPU 112 can write a non-zero value to the sink's FRL_Rate field that corresponds to a data rate that the source has determined is compatible with both the source and sink devices. Table 2 below is an example of possible values for FRL_Rate that GPU 112 may write to SCDCS 167 for a sink device. TIFF2023549501000003.tif2860
[0031] The DDC snoop circuit 148 monitors traffic on the DDC channel between the source device and the sink device. In one embodiment, the DDC snoop circuit 148 decodes writes from the source's GPU 112 to the sink device's SCDCS 167, which may include a TMDS_Bit_Clock_Ratio value and an FRL_Rate value. These values indicate whether the source and sink devices are configured to operate according to HDMI 2.1 or an earlier version of HDMI (e.g., HDMI 1.4 or 2.0). The TMDS_Bit_Clock_Ratio bit set equal to "1" by the GPU 112 indicates that the GPU 112 intends both the source and sink to operate according to HDMI 2.0. The TMDS_Bit_Clock_Ratio bit set equal to "0" and the FRL_Rate value equal to 0 indicate that the GPU 112 intends both the source and sink to operate according to HDMI 1.4. DDC snoop circuit 148 monitors traffic between source 112 and sink 160 for a write by source 112 to a predetermined address corresponding to an address containing the TMDS_Bit_Clock_Ratio and FRL_Rate values. This write may be a single write to one address containing both values, or it may be two separate writes to two different addresses (each containing one of these values). Upon detecting a write, DDC snoop circuit 148 examines the TMDS_Bit_Clock_Ratio bit. If DDC snoop circuit 148 determines that source device 110 and sink device 160 are operating according to a non-HDMI 2.1 mode (e.g., HDMI 1.4 or 2.0), DDC snoop circuit 148 configures transmitters 141-144 in redriver system 130 for restricted mode. DDC snoop circuit 148 configures the transmitters for restricted mode, for example, by asserting control signal 129 to the transmitters. FIG. 2 (described below) shows an example of how a transmitter may be configured for restricted mode.
[0032] However, sink device 160 may also be an HDMI 2.1 device. In this situation, when logic 114 within GPU 112 reads a non-zero Max_FRL_Rate value from the sink device's HF-VSDB 168, GPU 112 of the source device determines the data rate both devices can support and writes the FRL_Rate value to SCDCS 167 of the sink device. DDC snoop circuit 148 snoops the write by GPU 112 to the field containing FRL_Rate. A non-zero value for the snooped FRL_Rate indicates that source device 110 and sink device 160 are configured to implement HDMI 2.1. If DDC snoop circuit 148 determines that source device 110 and sink device 160 operate according to HDMI 2.1 mode, DDC snoop circuit 148 configures transmitters 141-144 for linear mode via control signals 129 within redriver system 130. FIG. 2 (described below) shows an example of how the transmitter in the redriver system 130 is configured for linear mode.
[0033] Additionally or alternatively, GPU 112 may read a sink version from the sink's SCDCS 167, which may indicate that the sink device is an HDMI 2.1 device. The sink version may be stored, for example, in a byte at offset 0x01 of SCDCS 167.
[0034] In another embodiment, DDC snoop circuit 148 configures transmitters 141-144 for linear mode in response to detecting a non-zero FRL rate and a TMDS_Bit_Clock_Ratio bit equal to '0'. The TMDS_Bit_Clock_Ratio bit defaults to a value of '0' upon a power-on reset event in GPU 112 of the source device and is not set to a value of '1' unless the sink device is determined to be HDMI 2.0 compliant. Thus, even if a non-zero FRL rate (indicating HDMI 2.1 operation) is detected by DDC snoop circuit 148, a TMDS_Bit_Clock_Ratio equal to '0' provides assurance to DDC snoop circuit 148 that HDMI 2.1 is indeed enabled for operation by the source and sink devices.
[0035] 2 shows an example of equalizer 134 and transmitter 144. The implementation shown for transmitter 144 applies equally to transmitters 141-143. Transmitter 144 includes a linear driver 210 and a limiting driver 220. For linear driver 210, the output signal is a linear function of the input signal, at least up to a certain input amplitude. For limiting driver 220, the output signal is not a linear function of the input signal. The limiting driver includes output swing control and / or output de- or pre-emphasis.
[0036] Linear driver 210 may be enabled or disabled by control signal 211 from DDC snoop circuit 148. Similarly, limiting driver 220 may be enabled or disabled by control signal 221 from DDC snoop circuit 148. In this example, control signals 211 and 221 comprise control signal 129 (FIG. 1). In one embodiment, control signals 211 and 221 are separately generated signals, each provided to one of the drivers, as shown in FIG. 2. In another embodiment, a single control signal is provided to both drivers 211 and 221, with a logic high on this single control signal enabling linear driver 210 and disabling limiting driver 220, for example, and a logic low on this control signal enabling limiting driver 220 and disabling linear driver 210.
[0037] In one example, DDC snoop circuit 148 is implemented as a finite state machine (e.g., a combination of logic gates, flip-flops, etc. configured to implement the functionality described herein). Figure 3 shows an example state diagram 300 that defines the operation of DDC snoop circuit 148. State diagram 300 in this example includes three states 301, 302, and 303. In state 301, the source and sink devices are configured for HDMI 1.4 operation. In state 302, the source and sink devices are configured for HDMI 2.0 operation. In state 303, the source and sink devices are configured for HDMI 2.1 operation.
[0038] Upon a power-on event (POR), the DDC snoop circuit defaults to state 301 (HDMI 1.4). A logic high HPD_IN signal indicates that sink device 160 is on and cabled to source device 110. If DDC snoop circuit 148 detects that FRL_Rate is not 0 and the TMDS_Bit_Clock_Ratio bit is 0, then DDC snoop circuit 148 transitions to state 303, where DDC snoop circuit 148 configures transmitters 141-144 in redriver system 130 for linear mode.
[0039] From state 301, if the DDC snoop circuit 148 detects that the FRL_Rate is 0 and the TMDS_Bit_Clock_Ratio bit is 1, the DDC snoop circuit 148 transitions to state 302 and configures the transmitters 141-144 for restricted mode. If the DDC snoop circuit 148 remains in its default state 301, the DDC snoop circuit 148 also configures the transmitters 141-144 for restricted mode.
[0040] From state 303, if cable 150 is disconnected or sink device 160 is powered down, the HPD_IN signal goes to a logic low. When the HPD_IN signal goes to a logic low or an updated FRL_Rate equal to 0 is detected by DDC snoop circuit 148 (e.g., GPU 112 sends a write to the sink device changing FRL_Rate to 0), the state of DDC snoop circuit 148 changes from state 303 to state 301. Upon entering state 301 from state 303, DDC snoop circuit 148 configures transmitters 141-144 for restricted mode.
[0041] From state 302, if the DHPD_IN signal is detected as a logic low or the DDC snoop circuit detects a change in the TMDS_Bit_Clock_Ratio value to 0, the state of the DDC snoop circuit 148 changes from state 302 to state 301. Upon entering state 301 from state 302, the DDC snoop circuit 148 maintains the configuration of the transmitters 141-144 in restricted mode.
[0042] 4 is a flowchart illustrating an example method 400 implemented by source device 110. Upon detecting a hot-plug event, in step 401, source device 110 (e.g., GPU 112) reads the sink device's EDID 165, SCDCS 167, and HF-VSDB 168. In 402, source device 110 (e.g., GPU 112) determines the capabilities (e.g., data rate, resolution, pre-emphasis, etc.) implemented by both the source and sink devices. In 403, source device 110 (e.g., GPU 112) writes parameters back to sink device 160 indicating the protocol by which the source and sink devices communicate with each other. The written parameters include, for example, the TMDS_Bit_Clock_Ratio bit, the FRL_Rate, and a source version identifier. In 404, the source and sink devices configure themselves according to the parameters determined by the source device.
[0043] During the parameter writing in step 403, the DDC snoop circuit 148 monitors traffic between the GPU 112 and the sink device 160, such as the TMDS_Bit_Clock_Ratio bits and FRL_Rate values written by the GPU 112 to the SCDCS 167 of the sink device. For example, based on the TMDS_Bit_Clock_Ratio bits and FRL_Rate values written by the GPU 112 to the sink device 160, the DDC snoop circuit determines in 406 whether the source device and the sink device are configured to operate in accordance with HDMI 2.1. If the source device and the sink device are configured to operate in accordance with HDMI 2.1 (branch "Yes"), in 407 the DDC snoop circuit 148 causes the transmitters 141-144 in the redriver system 130 to operate in linear mode. If the source device and the sink device are not configured to operate in accordance with HDMI 2.1 (the "No" branch), then at 408, the DDC snoop circuit 148 causes the transmitters 141-144 in the redriver system 130 to operate in restricted mode.
[0044] In this description, the term "couple" may encompass a connection, communication, or signal path that enables a functional relationship consistent with this description. For example, if device A generates a signal to control device B to perform an action, (a) in a first example, device A is coupled to device B by a direct connection, or (b) in a second example, device A is coupled to device B through an intervening component C if the intervening component C does not change the functional relationship between device A and device B, such that device B is controlled by device A via a control signal generated by device A.
[0045] A device that is "configured" to perform a task or function may be configured (e.g., programmed and / or hardwired) by a manufacturer at the time of manufacture to perform that function, and / or may be configurable (or reconfigurable) by a user after manufacture to perform that function and / or other additional or alternative functions. Such configuration may be achieved by firmware and / or software programming of the device, by the construction and / or layout of the hardware components and interconnections of the device, or by a combination thereof.
[0046] As used herein, the terms "terminal," "node," "interconnect," "pin," and "lead" are used interchangeably. Unless otherwise noted, these terms are used generally to refer to an interconnection between or a terminal of a device element, circuit element, integrated circuit, device, or other electronic or semiconductor component.
[0047] A circuit or device described herein as including certain components may instead be adapted to be coupled to such components to form the described circuit element or device. For example, a structure described as including one or more semiconductor elements (such as transistors), one or more passive elements (such as resistors, capacitors, and / or inductors), and / or one or more sources (such as voltage and / or current sources) may instead include only the semiconductor elements within a single physical device (e.g., a semiconductor die and / or integrated circuit (IC) package) and may be adapted to be coupled to at least some of the passive elements and / or sources to form the described structure, either during or after manufacture, e.g., by an end user and / or a third party.
[0048] Unless otherwise specified, "about," "approximately," or "substantially" before a value means + / - 10 percent of the stated value. Variations in the described examples are possible, and other examples are possible, within the scope of the claims.
[0049] Modifications in the described embodiments are possible, and other embodiments are possible, within the scope of the claims.
Claims
1. 1. A redriver system adapted to couple to a first device and a second device, comprising: a first transmitter driver having a first enable input, the first transmitter driver configured to operate as a linear driver; a second transmitter driver having a second enable input, the second transmitter driver configured to operate as a limited driver; a snoop circuit coupled to the first and second enable inputs, determining whether the first device and the second device operate according to a first protocol; in response to the snoop circuit determining that the first and second devices operate according to the first protocol, enabling the first transmitter driver and disabling the second transmitter driver; in response to the snoop circuit determining that the first and second devices operate according to a second protocol, disabling the first transmitter driver and enabling the second transmitter driver. The snoop circuit is configured as follows: The redriver system includes:
2. 2. The redriver system of claim 1, The redriver system, wherein the snoop circuitry determines that the first and second devices operate according to the first protocol by detecting a non-zero fixed rate link (FRL) value.
3. 2. The redriver system of claim 1, The redriver system, wherein the snoop circuit determines that the first and second devices operate according to a second protocol by detecting a fixed rate link (FRL) value equal to zero.
4. 2. The redriver system of claim 1, The redriver system, wherein the snoop circuit determines that the first and second devices operate according to a second protocol by detecting the absence of a fixed rate link (FRL) value.
5. 2. The redriver system of claim 1, The redriver system, wherein the first protocol is a High Definition Multimedia Interface (HDMI) 2.1 protocol and the second protocol is an HDMI protocol other than HDMI 2.
1.
6. 2. The redriver system of claim 1, further comprising third and fourth transmitter drivers; the first and second transmitter drivers are for a first data channel; The snoop circuit, in response to the snoop circuit determining that the first and second devices operate according to the first protocol, enabling the third transmitter driver and disabling the fourth transmitter driver; in response to the snoop circuit determining that the first and second devices do not operate according to the first protocol, disabling the third transmitter driver and disabling the second transmitter driver. The redriver system further configured as follows.
7. 2. The redriver system of claim 1, The redriver system, wherein the snoop circuitry is further configured to snoop write transactions by the first device to the second device.
8. 2. The redriver system of claim 1, The redriver system, wherein the snoop circuitry is further configured to snoop write transactions by the first device to the second device for the first device to configure the second device.
9. 1. A source device adapted to provide media data to a sink device, comprising: A graphics processor unit (GPU); A redriver system coupled to the GPU, comprising: a first transmitter driver having a first enable input, the first transmitter driver configured to operate as a linear driver; a second transmitter driver having a second enable input, the second transmitter driver configured to operate as a limited driver; a snoop circuit coupled to the first and second enable inputs, determining whether the source device and the sink device operate according to a first protocol; in response to the snoop circuit determining that the source and sink devices operate according to the first protocol, enabling the first transmitter driver and disabling the second transmitter driver; in response to the snoop circuit determining that the source and sink devices do not operate according to the first protocol, disabling the first transmitter driver and enabling the second transmitter driver. The snoop circuit is configured as follows: The redriver system includes: Including, the source device.
10. 10. A source device as claimed in claim 9, A source device, wherein the snoop circuitry determines that the source and sink devices operate according to the first protocol by detecting a non-zero fixed rate link (FRL) value.
11. 11. A source device according to claim 10, The source device, wherein the first protocol is a High Definition Multimedia Interface (HDMI) 2.1 protocol.
12. 10. A source device as claimed in claim 9, A source device, wherein the snoop circuitry determines that the source and sink devices operate according to a second protocol by detecting a fixed rate link (FRL) value equal to zero.
13. 13. A source device as claimed in claim 12, comprising: The source device, wherein the second protocol is a High Definition Multimedia Interface (HDMI) protocol other than HDMI 2.
1.
14. 13. A source device as claimed in claim 12, comprising: The source device, wherein the snoop circuitry determines that the source and sink devices operate according to a second protocol by detecting the absence of a fixed rate link (FRL) value.
15. 10. A source device as claimed in claim 9, The source system, wherein the snoop circuitry is further configured to snoop write transactions from the GPU to the sink device.
16. 10. A source device as claimed in claim 9, The source system, wherein the snoop circuitry is further configured to snoop write transactions by the source device to the sink device for the source device to configure the sink device.
17. 1. A method comprising: determining whether the first device and the second device operate according to a first protocol; in response to determining that the first and second devices operate according to the first protocol, enabling a linear driver and disabling a restricted driver; in response to determining that the first and second devices operate according to a second protocol, disabling the linear driver and enabling the restricted driver; A method comprising:
18. 20. The method of claim 17, The method, wherein determining that the first and second devices operate according to a first protocol includes detecting a non-zero Fixed Rate Link (FRL) value.
19. 20. The method of claim 17, 11. The method of claim 10, wherein determining that the first and second devices operate according to a second protocol includes detecting at least one of a fixed rate link (FRL) value equal to zero or the absence of a fixed rate link (FRL) value.
20. 20. The method of claim 17, 11. The method of claim 10, wherein the first protocol is a High Definition Multimedia Interface (HDMI) 2.1 protocol and the second protocol is an HDMI protocol other than the HDMI 2.1 protocol.
