Switching driver capable of switching between linear mode and limited mode

By monitoring device capabilities through monitoring circuitry and configuring the adapter driver system to linear or limited mode, the unreliable link training issue when connecting HDMI 2.1 source devices to earlier versions of receiver devices was resolved, enabling robust high data rate transmission.

CN116762064BActive Publication Date: 2026-11-10TEXAS INSTRUMENTS INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202180076464.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-06-30
Filing Date
2021-11-12
Publication Date
2026-11-10
Estimated Expiration
2041-11-12

AI Technical Summary

Technical Problem

When existing HDMI 2.1 source devices are connected to earlier versions of receiver devices, the link training process is unreliable, leading to an increase in signal errors and making it impossible to reliably achieve high data rate transmission.

Method used

The monitoring circuitry monitors the capabilities of both the source and receiver devices, and the adapter driver system is configured to linear or restricted mode according to the HDMI protocol version to ensure the reliability of the link training process.

Benefits of technology

Improved link training reliability between HDMI 2.1 source devices and earlier version receiver devices, reduced signal errors, and enabled robust high data rate transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116762064B_ABST
    Figure CN116762064B_ABST
Patent Text Reader

Abstract

A switch driver system (130) adapted to be coupled to a first device and a second device includes a first transmitter driver and a second transmitter driver and a monitoring circuit (148). The first transmitter driver has a first enable input. The second transmitter driver has a second enable input. The monitoring circuit (148) is coupled to the first enable input and the second enable input. The monitoring circuit (148) is configured to determine whether the first device and the second device are to operate according to a first protocol. In response to the monitoring circuit (148) determining that the first device and the second device are to operate according to the first protocol, the monitoring circuit (148) enables the first transmitter driver and disables the second transmitter driver. In response to the monitoring circuit determining that the first device and the second device are not to operate according to the first protocol, the monitoring circuit disables the first transmitter driver and enables the second transmitter driver.
Need to check novelty before this filing date? Find Prior Art

Description

Background Technology

[0001] In a scenario where a first device sends data (e.g., video and / or audio) to a second device, each device can adhere to a given interface protocol. For example, the first device could be a video source (e.g., a cable TV box, an internet-connected streaming device, a computer, etc.), and the second device could be a display monitor, with each device implementing a High-Definition Multimedia Interface (HDMI). An HDMI-implemented source device transmits both high-definition audio and video to an HDMI-compatible receiver via a single cable. The source device may also include an adapter driver, which is circuitry that implements equalization to reduce inter-symbol interference (ISI). Summary of the Invention

[0002] In one example, a transfer driver system adapted to couple to a first device and a second device includes a first transmitter driver, a second transmitter driver, and monitoring circuitry. The first transmitter driver has a first enable input. The second transmitter driver has a second enable input. The monitoring circuitry is coupled to the first and second enable inputs. The monitoring circuitry is configured to determine whether the first device and the second device will operate according to a first protocol. In response to the monitoring circuitry determining that the first device and the second device will operate according to the first protocol, the monitoring circuitry enables the first transmitter driver and disables the second transmitter driver. In response to the monitoring circuitry determining that the first device and the second device will not operate according to the first protocol, the monitoring circuitry 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 will operate according to a first protocol. In response to determining that the first device and the second device will operate according to the first protocol, the method includes enabling a first transmitter driver and disabling a second transmitter. In response to a monitoring circuit determining that the first device and the second device will operate according to a protocol other than the first protocol, the method includes disabling the first transmitter driver and enabling the second transmitter. Attached Figure Description

[0004] To describe the various examples in detail, reference will now be made to the accompanying drawings, in which:

[0005] Figure 1 This is a block diagram illustrating a source device coupled to a receiver device according to an example, the source device including a transfer driver system capable of linear or restricted operation modes.

[0006] Figure 2 This is a block diagram illustrating the transmitter within a transfer driver system having both a linear transmitter and a limited transmitter, according to an example.

[0007] Figure 3This is a state diagram illustrating the operating status of the monitoring circuitry within an example adapter driver system.

[0008] Figure 4 This is a flowchart illustrating an example method implemented by a monitoring circuit.

[0009] The same reference numerals or other reference symbols are used in the accompanying drawings to indicate the same or similar (functional and / or structural) features. Detailed Implementation

[0010] HDMI drivers can be either “linear” or “non-linear” adapter drivers. Non-linear adapter drivers are also known as restricted adapter drivers. A linear adapter driver implements a near-linear relationship between the driver’s input signal (e.g., voltage) and its output signal, at least within the range of interest. However, a restricted adapter driver implements pre-emphasis and amplitude control, resulting in its output signal not being a linear function of its input signal.

[0011] Several versions of the HDMI protocol have been established, including, for example, 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 Gbps. Both HDMI 1.4 and 2.0 specify Transition Minimum Differential Signaling (TMDS) encoding, in which the clock signal is transmitted along with the video and audio signals in the conductors of the HDMI cable. The HDMI 2.1 protocol provides even higher data transfer rates (e.g., up to 48 Gbps). HDMI 2.1 does not include the transmission of the clock signal between the source and receiver devices and reuses the clock pin used in HDMI 1.4 and 2.0 as an additional data channel.

[0012] When two HDMI-compatible devices are connected and powered on, the source device obtains device-specific data from the receiving device. This device-specific data includes, for example, Extended Data Identifier (EDID), HDMI Forum Vendor-Specific Data Blocks (HF-VSDB), and Status and Control Data Structures (SCDCS), which are stored in non-volatile memory on the receiving device. The receiving device's EDID specifies parameters such as the size of the receiving device's display, chroma values, timing values, etc. The HF-VSDB contains the receiving device's maximum data rate capability, as well as other device-specific data related to the receiving device. The source device uses the receiving device-specific data to determine the receiving device's capabilities and then selects a display resolution, data rate, etc., consistent with the capabilities of both the source and receiving devices. The source device then writes values ​​to the receiving device's SCDCS to specify to the receiving device the common capabilities (e.g., resolution, data rate, etc.) that the source device has determined for controlling the interaction between the source and receiving devices.

[0013] HDMI 2.1 also provides "link training" between the source and receiver devices. Link training was not implemented in earlier versions of HDMI (such as HDMI 1.4 and 2.0). The purpose of link training is to allow the source device to configure appropriate levels of pre-emphasis, voltage swing, etc., to reduce or eliminate errors. The link training process is initiated and controlled by the source device. During the link training process, the receiver device restores the source device's clock embedded in the data channel. The source device also sends a test mode to the receiver device. The test mode allows the source device to adjust the swing, pre-emphasis, and de-emphasis levels of its transmitter to values ​​that provide a more robust signal for the receiver device, thereby reducing or eliminating errors observed by the receiver device. Unfortunately, the link training process cannot work reliably for source devices using restricted adapter drivers. Using a restricted adapter driver during link training, when neither the receiver nor the source device's graphics processing unit (GPU) is aware of its existence, increases the risk of link training failure. Linear adapter drivers are transparent to link training and therefore have little or no impact on it. Therefore, the link training process will be more reliable if a linear adapter driver is used instead of a restricted adapter driver in the source device.

[0014] The HDMI protocol is backward compatible, meaning that any pair of HDMI-compatible source and receiver devices will operate together, regardless of which version of HDMI they implement. For example, an HDMI 2.1 source device can connect to an HDMI 1.4 receiver, an HDMI 2.0 receiver, or an HDMI 2.1 receiver. This means that if the source device is connected to an HDMI 2.1 receiver, the HDMI 2.1 source device will be able to perform link training. However, if the HDMI 2.1 source device is connected to an HDMI 1.4 or 2.0 receiver (or another HDMI version released before HDMI 2.1), the HDMI 2.1 source device will not participate in the link training protocol because pre-HDMI 2.1 receiver devices do not have this capability.

[0015] The embodiments described herein pertain to an adapter driver system having both a linear adapter driver operation mode and a restricted adapter driver operation mode. The adapter driver system includes monitoring circuitry that monitors the channel between a source device and a receiver device, wherein the capabilities of the receiver device are read by the source device, and the source device writes values ​​to the receiver device as part of a process in which the source and receiver devices negotiate a set of parameters regarding display resolution, pre-emphasis, voltage swing, etc. In one embodiment, the monitoring circuitry of the adapter driver system monitors one or more values ​​written by the source device's GPU to the receiver device regarding their mutual capabilities, which the source device has specified for its operation. Based on the monitored information, the monitoring circuitry determines whether the source and receiver devices are configured to operate according to the HDMI 2.1 protocol or a non-HDMI 2.1 protocol (e.g., pre-HDMI 2.1 protocols such as HDMI 1.4 or HDMI 2.0). If the monitoring circuitry determines that the source and receiver devices will operate according to the HDMI 2.1 protocol, the monitoring circuitry configures the adapter driver system to linear adapter driver mode. If the monitoring circuitry determines that the source and receiver devices will not operate according to the HDMI 2.1 protocol, the monitoring circuitry configures the adapter driver system to restricted adapter driver mode.

[0016] Figure 1This is a block diagram of system 100, which includes a source device 110 coupled to a receiving device 160 via cable 150. In one example, the source device 110 includes or otherwise acquires audio and / or video data (referred to herein as "media" data) and provides the media data to the receiving device via cable 150. The source device 110 may be a computer, set-top box, cable TV box, WiFi streaming device, etc. The receiving device 160 may be a display monitor or any other type of device that utilizes / displays media data. The receiving device 160 includes a memory 170 in which the receiving device's EDID 165, SDCCS 167, and HF-VSDB 168 are stored. The memory 170 may be non-volatile memory. The SDCCS 167 may be stored in a memory that can be both read and written. The EDID 165 and HF-VSDB 168 may be stored in a read-only memory (e.g., read-only memory, "ROM").

[0017] In the example described herein, source device 110 and receiver device 160 are HDMI compatible. Source device 110 is an HDMI 2.1 device and is therefore compatible with HDMI 2.1 receiver devices and backward compatible with receiver devices conforming to earlier versions of HDMI (e.g., HDMI 1.4 or HDMI 2.0). While source device 110 is an HDMI 2.1 device, receiver device 160 may be an HDMI 2.1 device or may be compatible with earlier versions of HDMI such as HDMI 1.4 or 2.0. The HDMI version of a device means that the device can operate according to its specified version or according to any earlier version of HDMI. For example, an HDMI 2.0 device can operate according to the HDMI 2.0 or 1.4 protocol, but not according to the HDMI 2.1 protocol. During the discovery process where source device 110 reads the receiver device's EDI D 165, SDCCS 167, and HF-VSDB 168, source device 110 determines the parameters (e.g., data rate, resolution, etc.) upon which the source device and receiver device operate. For example, if the source device 110 is HDMI 2.1 compatible, and the receiving device is HDMI 2.0 compatible, the source device will determine that both devices should be configured for HDMI 2.0 operation. Even though the source device 110 is HDMI 2.1 compatible, it will therefore configure itself for HDMI 2.0 operation.

[0018] Figure 1In the example, source device 110 includes a graphics processing unit (GPU) 112 coupled to adapter driver system 130. Cable 150 is an HDMI-compatible cable and includes four twisted pairs 151, 152, 153, and 154. Each twisted pair is used for a separate 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 clock. In HDMI 2.1, no separate clock signal is transmitted across cable 150, and therefore all four channels can be used for data. A serial communication link (e.g., internal integrated circuit, "I2C") is also provided on conductor 156 via cable 150 between the receiving and source devices, through which GPU 112 can read the receiving device's EDID 165, SDCCS 167, and HF-VSDB 168 and provide parameter values ​​to the receiving device for storage in HF-VSDB 168. The conductor 156 can be a single conductor or a pair of conductors, such as a clock line and a serial data line. The communication link on the conductor 156 can be referred to as a Display Data Channel (DDC). The cable 150 also includes a hot-plug detection (HPD) conductor 155, which enables the source device 110 to detect whether the cable 150 is connected to the powered-on receiving device 160.

[0019] exist Figure 1 In one example, all signals provided via cable 150 between receiving device 160 and GPU 112 (within source device 110) flow through adapter driver system 130. In other examples, one or more of the signals may bypass adapter driver system 130 (e.g., DDC information on wire 156 may not pass through adapter driver system 130).

[0020] exist Figure 1 In the example, GPU 112 includes four transmitters 115, 116, 117, and 118, corresponding to each of the four data channels (or three data channels plus a clock) mentioned above. Receiver device 160 has four corresponding receivers 161, 162, 163, and 164 coupled to logic device 169. Logic device 169 may include a processor, digital logic, application-specific integrated circuit (ASIC), memory, and / or any other type of circuitry that receives, processes, and consumes media data from source device 110. Logic device 169 provides media data to display 173. Display 173 may be coupled to receiver device 160 or may be a component of receiver device 160. Display device 173 may include one or more speakers for playing audio.

[0021] The adapter driver 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 receiver 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 receiver 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 receiver 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 to the input of receiver 164 in receiver 160 via conductor 154 in the cable. In one example, each of conductors 151, 152, 153, and 154 is a twisted pair.

[0022] In one example, the logic unit 114 of the GPU includes a processor, memory, and / or other digital circuitry configured to execute software. In another example, the logic unit 114 is discrete digital circuitry. The logic unit 114 causes media data to be transmitted via transmitters 115-118, through corresponding equalizer / transmitter pairs of the adapter driver system 130, to receivers 161-164 within the receiving device 160. The source device 110 may have memory containing media data 119 to be provided to the receiving device 160 via one or more of the transmitters 115-118. The media data 119 may be obtained from a disk (e.g., Blu-ray disc, DVD, CD-ROM, etc.) by the logic unit 114, or the media data may be streamed from a network (e.g., from the Internet) to the receiving device 160 via the GPU 112.

[0023] In one embodiment, GPU 112 is implemented as an integrated circuit (IC) comprising GPU 112 and adapter driver system 130 on the same semiconductor die. In another embodiment, adapter driver system 130 is implemented as a separate IC from the IC on which GPU 112 is implemented. Thus, GPU 112 can be on one IC, and adapter driver system 130 can be another IC, and both ICs can be included as part of source device 110. For example, the IC forming GPU 112 and adapter driver system 130 can be mounted on a printed circuit board (PCB) within source device 110.

[0024] The HDMI protocol implements hot-plug detection (HPD) capability, where the source and receiver devices can be connected via cable 150 when both devices are powered on. On the source device 110 side of cable 150, source device 110 includes a pull-down resistor R1 that couples a conductor 155 to ground. Figure 1 In one embodiment, the pull-down resistor R1 is included within the adapter driver system 130. In another embodiment, the pull-down resistor R1 is external to the adapter driver system 130. When no cable is connected, or when the cable is connected but the receiving device 160 is de-energized, the HPD signal (the voltage across resistor R1) is logic low. When cable 150 is connected and the receiving device 160 is energized, the HPD signal is pulled high (above a threshold) because the HPD line within the receiving device 160 is coupled to a suitable high-voltage source (not shown). A buffer 149 is provided within the adapter driver 130 to drive the HPD signal to logic 114 within the GPU 112. By monitoring the logic level of the HPD signal, logic 114 can determine whether the energized receiving device 160 is connected to the source device 110 via a cable.

[0025] As described above, the HDMI protocol provides a DDC interface between the source and receiver devices. In one example, the DDC interface is a protocol implemented over a serial data link via wire 156 of cable 150, through which EDID 165, SDCCS 167, and HF-VSDB 168 from receiver device 160 are provided to GPU 112, and GPU 112 writes one or more parameter values ​​to receiver SDCCS 167 via this cable. Logic unit 114 in GPU 112 issues one or more read requests to receiver device 160 to read EDID 165, SDCCS 167, and HF-VSDB 168 from receiver device memory 170. Logic unit 114 in GPU issues the read request in response to, for example, detecting a logic low to logic high transition of the HPD input.

[0026] The adapter driver system 130 includes a DDC transceiver 147 that receives and decodes bidirectional DDC traffic transmitted between the source device 112 and the receiver device 160. For example, requests to read EDID 165, SDCCS 167, and HF-VSDB 168 from logic device 114 of the GPU are forwarded to receiver device 160 via DDC transceiver 147, and read data (EDID, SDCCS, and HF-VSDB) from receiver device 160 is returned to logic device 114 via DDC transceiver 147. Logic device 114 also writes one or more parameters back to SDCCS 167 in receiver device 160 via transceiver 147. The adapter drive system 130 also includes DDC monitoring circuitry 148, which monitors bidirectional traffic through the DDC transceiver 147 for a set of predetermined packets that instruct the source device 110 and the receiver device 160 to use either the HDMI 2.1 protocol or a non-HDMI 2.1 protocol (e.g., HDMI 1.4 or HDMI 2.0).

[0027] GPU 112 (e.g., logic device 114) reads EDID 165, SDCCS 167, and HF-VSDB 168 from the receiver device's memory 170. HF-VSDB 168 includes values ​​called MAX_TMDS_Character_Rate and Max_FRL_Rate. Transformation Minimized Differential Signaling (TMDS) is a technique used to transmit high-speed digital data while reducing electromagnetic interference (EMI) and enabling clock recovery over relatively large distances (e.g., up to 100 feet). TMDS is implemented as part of HDMI 1.4 and 2.0, but not as part of HDMI 2.1. MAX_TMDS_Character_Rate is the maximum TMDS character rate supported by receiver device 160. In one example, if receiver device 160 does not support a TMDS character rate greater than 340 megacharacters per second (Mcsc), then MAX_TMDS_Character_Rate is set to 0; otherwise, the field is non-zero and indicates the maximum TMDS character rate supported by the receiver device. The MAX_TMDS_Character_Rate value is, for example, an octet in byte number 5 of HF_VDSB 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_FRL_Rate value is, for example, a four-bit value in byte number 7 of HF_VDSB 168. Max_FRL_Rate indicates the FRL level that the receiving device can achieve. A Max_FRL_Rate value of 0 means that the receiving device does not support Fixed Rate Link. Non-zero Max_FRL_Rates indicate the data rate of individual channels. Table I below includes the possible values ​​of Max_FRL_Rate according to the HDMI specification.

[0029] Table I. MAX_FRL_RATE

[0030]

[0031]

[0032] Among other values, GPU 112 reads the Max_TMDS_Character_Rate and Max_FRL_Rate values ​​from the receiving device's HF-VSDB 168 to determine the capabilities of the receiving device 160. Based on these values, GPU 112 determines the shared capabilities between the source and receiving devices. Based on this determination, GPU 112 writes values ​​to the receiving device's SDCCS 167. For example, GPU 112 determines a bit called TMDS_Bit_Clock_Ratio and a four-bit value called FRL_Rate and writes them to the receiving device's SDCCS 167. The TMDS_Bit_Clock_Ratio bit is, for example, bit number 1 of the TMDS configuration byte at offset 0x20 within SDCCS 167. The TMDS_Bit_Clock_Ratio bit defaults to a value of 0, which indicates that the ratio between the TMDS bit period and the TMDS clock period is 1 / 10. However, the GPU 112 can set the TMDS_Bit_Clock_Ratio bit to 1 to specify a ratio of 1 / 40 between the TMDS bit period and the TMDS clock period.

[0033] For example, the FRL_Rate value is bits [3:0] of the receiving configuration byte at offset 0x31 within SCDCS 167. The FRL_Rate field defaults to a value of 0, indicating that the receiving device will not support FRL signaling. However, the GPU 112 can write a non-zero value to the receiving FRL_Rate field, corresponding to a data rate determined by the source that is compatible with both the source and receiving devices. Table II below shows examples of possible FRL_Rate values ​​that the GPU 112 writes to the receiving device's SCDCS 167.

[0034] Table II.FRL_RATE

[0035] FRL_RATE describe 0 Disable FRL 1 3Gbps FRL on channels 0, 1 and 2 2 6Gbps FRL on channels 0, 1 and 2 3 6Gbps FRL on all four channels 4 8Gbps FRL on all four channels 5 10Gbps FRL on all four channels 6 12Gbps FRL on all four channels 7:15 reserve

[0036] DDC monitoring circuitry 148 monitors traffic on the DDC channel between the source and receiver devices. In one embodiment, DDC monitoring circuitry 148 decodes writes from the source GPU 112 to the receiver device's SCDSC 167, which may contain TMDS_Bit_Clock_Ratio and FRL_Rate values. These values ​​indicate whether the source and receiver devices are configured to operate according to HDMI 2.1 or a previous version of HDMI (e.g., HDMI 1.4 or 2.0). A TMDS_Bit_Clock_Ratio bit set to "1" by GPU 112 indicates that GPU 112 intends for both the source and receiver to operate according to HDMI 2.0. A TMDS_Bit_Clock_Ratio bit set to "0" and an FRL_Rate value equal to 0 indicates that GPU 112 intends for both the source and receiver to operate according to HDMI 1.4. DDC monitoring circuit 148 monitors traffic between source device 112 and receiver 160 for writes made by source device 112 to one or more predetermined addresses corresponding to one or more addresses containing the values ​​of TMDS_Bit_Clock_Ratio and FRL_RATE. A write can be a single write to an address containing both values, or two separate writes to two different addresses (each containing one of the values). Upon detecting a write, DDC monitoring circuit 148 checks the TMDS_Bit_Clock_Ratio bit. If DDC monitoring circuit 148 determines that source device 110 and receiver device 160 are to operate according to a non-HDMI 2.1 mode (e.g., HDMI 1.4 or 2.0), DDC monitoring circuit 148 configures transmitters 141-144 within adapter driver system 130 to a restricted mode. DDC monitoring circuit 148 asserts control signal 129 to the transmitters to configure them to restricted mode, for example. Figure 2 An example of how to configure the transmitter to restricted mode is shown below.

[0037] However, the receiving device 160 can be an HDMI 2.1 device. In this case, after the logic unit 114 within the GPU 112 reads a non-zero Max_FRL_Rate value from the receiving device's HF-VSDB 168, the source device's GPU 112 determines the data rates that both devices can support and writes the FRL_Rate value to the receiving device's SDCCS 167. The DDC monitoring circuitry 148 monitors the writes to the field containing the FRL_Rate by the GPU 112. If the monitored FRL_Rate is a non-zero value, it indicates that the source device 110 and the receiving device 160 are configured to implement HDMI 2.1. If the DDC monitoring circuitry 148 determines that the source device 110 and the receiving device 160 are to operate according to HDMI 2.1 mode, the DDC monitoring circuitry 148 configures the transmitters 141-144 to linear mode via control signals 129 within the adapter driver system 130. Figure 2 An example of how to configure the transmitter within the adapter driver system 130 to linear mode is shown (as described below).

[0038] Alternatively or additionally, GPU 112 can read the receiver version from the receiver's SDCCS 167, and the receiver version can indicate that the receiver device is an HDMI 2.1 device. The receiver version is stored in a byte at, for example, offset 0x01 in SDCCS 167.

[0039] In another embodiment, in response to the detection of a non-zero FRL rate and the TMDS_Bit_Clock_Ratio bit being "0", the DDC monitoring circuit 148 configures transmitters 141-144 to linear mode. The TMDS_Bit_Clock_Ratio bit defaults to a value of "0" when a power-on reset event occurs within the source device's GPU 112 and will not be set to a value of "1" unless the receiving device is determined to be HDMI 2.0 compliant. Therefore, when the DDC monitoring circuit 148 detects a non-zero FRL rate (indicating HDMI 2.1 operation), a value of "0" for TMDS_Bit_Clock_Ratio provides the DDC monitoring circuit 148 with a guarantee that both the source and receiving devices are indeed operating with HDMI 2.1 enabled.

[0040] Figure 2 Examples of equalizer 134 and transmitter 144 are shown. The implementation shown for transmitter 144 is also applicable to transmitters 141-143. Transmitter 144 includes a linear driver 210 and a restricted driver 220. For the linear driver 210, the output signal is a linear function of the input signal, reaching at least a certain input amplitude. For the restricted driver 220, the output signal is not a linear function of the input signal. The restricted driver includes output oscillation control and / or output de-emphasis or pre-emphasis.

[0041] Linear driver 210 can be enabled or disabled by control signal 211 from DDC monitoring circuit 148. Similarly, restricted driver 220 can be enabled or disabled by control signal 221 from DDC monitoring circuit 148. In this example, control signals 211 and 221 include control signal 129 ( Figure 1 In one embodiment, control signals 211 and 221 are separately generated signals, each of which is provided to one of the drivers, such as... Figure 2 As shown. In another embodiment, a single control signal is provided to both drivers 211 and 221, wherein a logic high on the single control signal enables, for example, the linear driver 210 and disables the restricted driver 220, and a logic low on the control signal enables the restricted driver 220 and disables the linear driver 210.

[0042] In one example, the DDC monitoring circuit 148 is implemented as a finite state machine (e.g., a combination of logic gates, flip-flops, etc., configured to implement the functions described herein). Figure 3 An example state diagram 300 defining the operation of the DDC monitoring circuit 148 is shown. This example state diagram 300 includes three states: 301, 302, and 303. In state 301, the source and receiver devices are configured for HDMI 1.4 operation. In state 302, the source and receiver devices are configured for HDMI 2.0 operation. In state 303, the source and receiver devices are configured for HDMI 2.1 operation.

[0043] Following a Power-On Event (POR), the DDC monitoring circuit defaults to state 301 (HDMI 1.4). The HPD_IN signal is logic high, indicating that the receiving device 160 is powered on and connected to the source device 110 via cable. If the DDC monitoring circuit 148 detects that FRL_Rate is not 0 and the TMDS_Bit_Clock_Ratio bit is 0, the DDC monitoring circuit 148 transitions to state 303, in which the DDC monitoring circuit 148 configures the transmitters 141-144 within the adapter driver system 130 for linear mode.

[0044] If, from state 301, DDC monitoring circuit 148 detects that FRL_Rate is 0 and TMDS_Bit_Clock_Ratio is 1, then DDC monitoring circuit 148 transitions to state 302 and configures transmitters 141-144 for restricted mode. If DDC monitoring circuit 148 remains in its default state 301, then DDC monitoring circuit 148 also configures transmitters 141-144 for restricted mode.

[0045] From state 303, if cable 150 is disconnected or receiving device 160 is powered off, the HPD_IN signal will be logic low. If the HPD_IN signal goes low or DDC monitoring circuit 148 detects an updated FRL_Rate equal to 0 (e.g., GPU 112 issues a write to the receiving device to change FRL_Rate to 0), the state of the DDC monitoring circuit changes from state 303 to state 301. After transitioning from state 303 to state 301, DDC monitoring circuit 148 configures transmitters 141-144 for restricted mode.

[0046] From state 302, after detecting that the HPD_IN signal is logic low or the DDC monitoring circuit detects that TMDS_Bit_Clock_ratio has changed to a value of 0, the state of the DDC monitoring circuit 148 will change from state 302 to state 301. After transitioning from state 302 to state 301, the DDC monitoring circuit 148 maintains the configuration of transmitters 141-144 in restricted mode.

[0047] Figure 4 This is a flowchart depicting an example method 400 implemented by source device 110. Upon detecting a hot-plug event, at step 401, source device 110 (e.g., GPU 112) reads the receiving device's EDID 165, SCDCS 167, and HF-VSDB 168. At 402, source device 110 (e.g., GPU 112) determines the capabilities (e.g., data rate, resolution, pre-emphasis, etc.) to be implemented by both the source and receiving devices. At 403, source device 110 (e.g., GPU 112) writes parameters to receiving device 160 to indicate the protocol upon which the source and receiving devices communicate with each other. The written parameters include, for example, the TMDS_Bit_Clock_Ratio bit, FRL_Rate, and the source device's version identifier. At 404, the source and receiving devices configure themselves according to the parameters determined by the source device.

[0048] During the parameter write at step 403, the DDC monitoring circuit 148 monitors the traffic between the GPU 112 and the receiving device 160, such as the values ​​of the TMDS_Bit_Clock_Ratio bit and FRL_Rate written by the GPU 112 to the SDCCS 167 of the receiving device. Based on, for example, the values ​​of the TMDS_Bit_Clock_Ratio bit and FRL_Rate written by the GPU 112 to the receiving device 160, the DDC monitoring circuit determines at 406 whether the source device and the receiving device are configured to operate according to HDMI 2.1. If the source device and the receiving device are configured to operate according to HDMI 2.1 (“Yes” branch), then at 407, the DDC monitoring circuit 148 causes the transmitters 141-144 within the adapter driver system 130 to operate in linear mode. If the source and receiver devices are not configured to operate according to HDMI 2.1 (“No” branch), then at 408, the DDC monitoring circuit 148 causes the transmitters 141-144 within the adapter driver system 130 to operate in restricted mode.

[0049] In this specification, the term "coupled" may cover a connection, communication, or signal path that achieves a functional relationship consistent with this specification. For example, if device A generates a signal to control device B to perform an action, then: (a) in a first example, device A is coupled to device B via a direct connection; or (b) in a second example, if intermediate component C does not change the functional relationship between device A and device B, then device A is coupled to device B via intermediate component C such that control signals generated by device B via device A are controlled by device A.

[0050] A device “configured” to perform a task or function can be configured by the manufacturer at manufacturing time (e.g., programmed and / or hardwired) to perform that function and / or can be configured (or reconfigured) by the user after manufacturing to perform that function and / or other additional or alternative functions. Configuration can be achieved through firmware and / or software programming of the device, through the construction and / or layout of hardware components, and the interconnection of the device, or a combination thereof.

[0051] As used herein, the terms “terminal,” “node,” “interconnect,” “pin,” and “lead” are used interchangeably. Unless otherwise specified, these terms are generally used to refer to interconnections or terminations between device elements, circuit elements, integrated circuits, devices, or other electronic or semiconductor components.

[0052] A circuit or device described herein as including certain components may be modified to be coupled to those components to form the described circuit system or device. For example, a description 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 sources and / or current sources) may be modified to include only semiconductor elements within a single physical device (e.g., a semiconductor die and / or integrated circuit (IC) package), and may be modified to be coupled to at least some of the passive elements and / or sources during or after manufacturing, for example by an end user and / or a third party, to form the described structure.

[0053] Unless otherwise stated, "about," "approximately," or "substantially" preceding a numerical value means + / - 10% of that value. Modifications to the described examples are possible within the scope of the claims, and other examples are also possible.

[0054] Within the scope of the claims, modifications to the described embodiments are possible, and other embodiments are also possible.

Claims

1. A transfer driver system suitable for coupling to a first device and a second device, comprising: A first transmitter driver is configured to operate as a linear driver and has a first enable input; A second transmitter driver is configured to operate as a restricted driver and has a second enable input; as well as A monitoring circuit, coupled to the first enable input and the second enable input, is configured to: Determine whether the first device and the second device will operate according to the first protocol; In response to the monitoring circuit determining that the first device and the second device will operate according to the first protocol, the first transmitter driver is enabled and the second transmitter driver is disabled; as well as In response to the monitoring circuit determining that the first device and the second device will operate according to the second protocol, the first transmitter driver is disabled and the second transmitter driver is enabled.

2. The adapter driver system of claim 1, wherein the monitoring circuit determines that the first device and the second device will operate according to the first protocol by detecting a non-zero fixed rate link value, i.e., a non-zero FRL value.

3. The adapter driver system of claim 1, wherein the monitoring circuit determines that the first device and the second device will operate according to the second protocol by detecting a fixed rate link value equal to zero, i.e., a FRL value.

4. The adapter driver system of claim 1, wherein the monitoring circuit determines that the first device and the second device will operate according to the second protocol by detecting the absence of a fixed rate link value, i.e., a FRL value.

5. The adapter driver system of claim 1, wherein the first protocol is the High Definition Multimedia Interface 2.1 protocol, i.e., the HDMI 2.1 protocol, and the second protocol is an HDMI protocol other than HDMI 2.

1.

6. The adapter driver system of claim 1, wherein the first transmitter driver and the second transmitter driver are used for a first data channel, and the adapter driver system includes a third transmitter driver and a fourth transmitter driver, and wherein the monitoring circuit is configured to: In response to the monitoring circuit determining that the first device and the second device will operate according to the first protocol, the third transmitter driver is enabled and the fourth transmitter driver is disabled; and In response to the monitoring circuit determining that the first device and the second device will not operate according to the first protocol, the third transmitter driver is disabled and the fourth transmitter driver is enabled.

7. The adapter drive system of claim 1, wherein the monitoring circuitry is configured to monitor write transactions from the first device to the second device.

8. The adapter drive system of claim 1, wherein the monitoring circuitry is configured to monitor write transactions from the first device to the second device, the first device configuring the second device via the write transactions.

9. A source device suitable for providing media data to a receiving device, comprising: Graphics processing unit, or GPU; as well as An adapter driver system coupled to the GPU, the adapter driver system comprising: A first transmitter driver is configured to operate as a linear driver and has a first enable input; A second transmitter driver, configured to operate as a restricted driver and having a second enable input; and A monitoring circuit, coupled to the first enable input and the second enable input, is configured to: Determine whether the source device and the receiving device will operate according to the first protocol; In response to the monitoring circuit determining that the source device and the receiver device will operate according to the first protocol, the first transmitter is enabled and the second transmitter is disabled; and In response to the monitoring circuit determining that the source device and the receiver device will not operate according to the first protocol, the first transmitter is disabled and the second transmitter is enabled.

10. The source device of claim 9, wherein the monitoring circuit determines that the source device and the receiver device will operate according to the first protocol by detecting a non-zero fixed rate link value, i.e., a non-zero FRL value.

11. The source device according to claim 10, wherein the first protocol is the High Definition Multimedia Interface 2.1 protocol, i.e., the HDMI 2.1 protocol.

12. The source device of claim 9, wherein the monitoring circuit determines that the source device and the receiver device will operate according to the second protocol by detecting a fixed rate link value equal to zero, i.e., a FRL value.

13. The source device of claim 12, wherein the second protocol is a high-definition multimedia interface protocol other than HDMI 2.1, i.e., the HDMI protocol.

14. The source device of claim 12, wherein the monitoring circuit determines that the source device and the receiver device will operate according to the second protocol by detecting the absence of a fixed rate link value, i.e., a FRL value.

15. The source device of claim 9, wherein the monitoring circuitry is configured to monitor write transactions from the GPU to the receiver device.

16. The source device of claim 9, wherein the monitoring circuitry is configured to monitor write transactions from the source device to the receiver device, the source device configuring the receiver device through the write transactions.

17. A method for transmitting data, comprising: Determine whether the first device and the second device will operate according to the first protocol; In response to determining that the first device and the second device will operate according to the first protocol, the linear driver is enabled and the restricted driver is disabled; as well as In response to determining that the first device and the second device will operate according to the second protocol, the linear driver is disabled and the restricted driver is enabled.

18. The method of claim 17, wherein determining that the first device and the second device will operate according to the first protocol includes detecting a non-zero fixed rate link value, i.e., a non-zero FRL value.

19. The method of claim 17, wherein determining that the first device and the second device will operate according to the second protocol includes detecting at least one of the following: a fixed rate link value (FRL) equal to zero, or the absence of a fixed rate link value (FRL).

20. The method of claim 17, wherein the first protocol is the High Definition Multimedia Interface 2.1 protocol, i.e., the HDMI 2.1 protocol, and the second protocol is any other than HDMI. HDMI protocols other than 2.1.

Citation Information

Patent Citations

  • Projection method, device and projector

    CN106162017A

  • Current detecting circuit based on bi-directional saturation current sensor and driving method thereof

    CN106291049A