Bidirectional Redriver for Half-Duplex Interfaces

By designing the adapter driver circuit, detecting the signal edge and bus impedance, the signal level shift and adapter driving between different voltage domains are realized, and the problem of low signal transmission efficiency of half-duplex communication interface between different voltage domains is solved. Reduces system complexity and cost.

CN113811863BActive Publication Date: 2024-12-06TEXAS INSTRUMENTS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080034872.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-03-23
Filing Date
2020-05-18
Publication Date
2024-12-06
Estimated Expiration
2040-05-18

Smart Images

  • Figure CN113811863B_ABST
    Figure CN113811863B_ABST
Patent Text Reader

Abstract

The present invention discloses a circuit (102), comprising: a first port (152) coupled to a first device (108); a second port (154) coupled to a second device (110); a first channel (137) having an input terminal (138) coupled to the first port and an output terminal (142) coupled to the second port, wherein the first channel is used to transfer a driving signal and output the transferred driven signal; a second channel (143) having an input terminal (144) coupled to the second port and an output terminal (148) coupled to the first port, The second channel is used to transfer the drive signal and output the transferred driven signal; and a controller (150) is used to: enable the first channel and disable the second channel in response to detecting a signal edge at the first port; enable the second channel and disable the first channel in response to detecting a signal edge at the second port; if the signal received at the first port is de-asserted when the first channel is enabled, then sample the impedance at the first port; and if the signal received at the second port is de-asserted when the second channel is enabled, then sample the impedance at the second port.
Need to check novelty before this filing date? Find Prior Art

Description

Summary of the invention

[0001] In some examples, a redriver circuit includes: a first port configured to couple to a first device via a first bus; and a second port configured to couple to a second device via a second bus. The redriver circuit also includes: a first communication channel having an input coupled to the first port and an output coupled to the second port, the first communication channel configured to redrive an input signal and output the redriven input signal; a second communication channel having an input coupled to the second port and an output coupled to the first port, the second communication channel configured to redrive an input signal and output the redriven input signal; and a controller. The controller is configured to enable the first communication channel and disable the second communication channel in response to detecting a first signal edge at the first port; enable the second communication channel and disable the first communication channel in response to detecting a first signal edge at the second port; sample the impedance at the first port in response to deasserting an input signal received at the first port when the first communication channel is enabled; and sample the impedance at the second port in response to deasserting the input signal received at the second port when the second communication channel is enabled.

[0002] In another example, the redriver circuit includes a first port configured to be coupled to a first device via a first clock bus; a second port configured to be coupled to a second device via a second clock bus; a third port configured to be coupled to the first device via a first data bus; a fourth port configured to be coupled to the second device via a second data bus; a first communication channel configured to re-drive an input clock signal received from the first port to the second port as an output clock signal; a second communication channel configured to re-drive an input clock signal received from the second port to the first port as an output clock signal; a third communication channel configured to re-drive an input data signal received from the third port to the fourth port as an output data signal; a fourth communication channel configured to re-drive an input data signal received from the fourth port to the third port as an output data signal; and a controller. The controller is configured to enable a first communication channel and disable a second communication channel in response to detecting the start of a clock signal edge at the first port; enable the second communication channel and disable the first communication channel in response to detecting the start of a clock signal edge at the second port, enable the third channel and disable the fourth channel in response to detecting the start of a data signal edge at the third port; enable the fourth communication channel and disable the third communication channel in response to detecting the start of a data signal edge at the fourth port; sample the impedance at the first port in response to de-asserting an input clock signal received at the first port when the first communication channel is enabled; sample the impedance at the second port in response to de-asserting the input clock signal received at the second port when the second communication channel is enabled; sample the impedance at the third port in response to de-asserting an input data signal received at the third port when the third communication channel is enabled; and sample the impedance at the fourth port in response to de-asserting an input data signal received at the fourth port when the fourth communication channel is enabled.

[0003] In yet another example, a method includes detecting a first signal edge at a first port, the first port being configured to be coupled to a first device via a first bus; or detecting a first signal edge at a second port, the second port being configured to be coupled to a second device via a second bus. The method also includes, in response to detecting the first signal edge at the first port, enabling a first communication channel configured to re-drive an input signal received from the first port to the second port as an output signal, and disabling a second communication channel configured to re-drive an input signal received from the second port to the first port as an output signal. The method also includes, in response to detecting the first signal edge at the second port, enabling the second communication channel and disabling the first communication channel. The method further includes sampling an impedance at the first port in response to de-asserting an input signal received at the first port when the first communication channel is enabled; and sampling an impedance at the second port in response to de-asserting an input signal received at the second port when the second communication channel is enabled. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0005] Figure 1 Block diagrams of systems presented in various examples;

[0006] Figure 2 schematic diagrams showing redriver circuits in various embodiments;

[0007] Figure 3 Shown in various examples Figure 2 State diagram of the redriver circuit;

[0008] Figure 4 Demonstration confirmation Figure 2 timing diagrams of the operation of the redriver circuit in various examples; and

[0009] Figure 5 Shown in various examples Figure 2 Another state diagram of the redriver circuit. DETAILED DESCRIPTION

[0010] Communication interfaces are common in modern electronics. Some communication interfaces are unidirectional (e.g., data flows in only one direction), while other communication interfaces are bidirectional (e.g., data flows in both directions). A half-duplex communication system utilizes a bidirectional communication interface where devices can communicate with each other, but not simultaneously. For example, communication occurs in only one direction at a time.

[0011] Computers and other electronic devices often use serial communication interfaces to provide data transfer between connected devices. The Universal Serial Bus (USB) interface is one of a variety of serial buses used to interface electronic devices. The System Power Management Interface (SPMI) is another serial bus used to interface electronic devices. SMPI is a bidirectional, two-wire serial bus interface, such as used to control the voltage supplied to the processor and the power management of auxiliary components coupled thereto. Other serial interfaces are also within the scope of the present disclosure. Regardless of the specific type of interface, electronic devices that communicate through such interfaces include, for example, computers, smartphones, video game consoles, and other computing devices. Peripheral devices also communicate through such interfaces and include, for example, flash drives, printers, keyboards, smartphones, cameras, tablets, and various other devices.

[0012] Regardless of the specific type of device communicating via a bidirectional, half-duplex, serial communication interface, in some instances, input / output (I / O) voltage levels differ from one device type to another. For example, as the process technology of processors (e.g., system on a chip (SoC)) becomes smaller, the I / O voltage limits of the processors also decrease. As an example, a processor using a 5nm process technology may have an I / O voltage limit of approximately 1.2V, while a processor using a 3nm process technology may have an I / O voltage limit of approximately 1.0V. In addition, in some instances, the processor interface interfaces with a higher voltage, such as SPMI (e.g., an I / O voltage limit of 1.8V) or USB (e.g., an I / O voltage limit of 3.3V). In order for a device in a first voltage domain (e.g., a processor having an I / O voltage limit of approximately 1.2V) to communicate with a device in a second voltage domain (e.g., an SPMI device having an I / O voltage limit of 1.8V), level shifting is utilized to shift the voltage level of a signal from one voltage domain to another voltage domain. In addition, the communication signal benefits from being re-driven or received and re-transmitted by the re-driver circuit. For example, re-driving the drive signal by the re-driver circuit between the devices increases the allowable range between the devices while isolating the two sides of the communication bus, thereby preventing the bus capacitance from one side of the re-driver circuit from loading the bus on the other side of the re-driver circuit. Although in some examples, a dedicated hub or bridge device completes such level shifting and re-driving of the signal, the dedicated hub takes up space and has high implementation costs. For example, a dedicated hub or bridge device can actively participate in the bus arbitration process and simulate a master device facing the slave device and a slave device facing the master device. Active participation in bus arbitration and such master / slave simulation involves more complex payload unpacking and repacking, which increases the complexity of the overall device.

[0013] Some examples include a redriver circuit between two voltage domains, the redriver circuit being used to level shift a signal voltage to facilitate communication between devices in different voltage domains and / or to redrive those communication signals between devices. Specifically, the redriver circuit facilitates half-duplex communication, where in some examples, level shifting occurs in both directions regardless of the direction of the communication traffic. Preferably, the redriver circuit is configured to detect a first signal edge that indicates the start of a signal transmission from a device in one of the voltage domains (e.g., a rising edge of a signal carried by a clock and / or data bus). However, the redriver circuit may use other techniques that indicate the start of a signal transmission. If a first signal edge is detected from the first of the two voltage domains (e.g., on a first bus coupled to a first port of the redriver circuit), the redriver circuit is configured to enable a first communication channel from the first of the two voltage domains to the second voltage domain. If a first signal edge is detected from the second voltage domain (e.g., on a second bus coupled to a second port of the redriver circuit), the redriver circuit is configured to enable a second communication channel from the second voltage domain to the first voltage domain. As will be further described below, the communication channel facilitates level shifting of signal voltages and / or redriving of signals from one voltage domain to another voltage domain. For example, in some cases, the I / O voltage limits of each voltage domain are substantially the same, and thus redriver circuits are used to drive signals (e.g., clock and / or data signals) between voltage domains but do not necessarily perform level shifting of signals between voltage domains.

[0014] The redriver circuit is also configured to sample the impedance of a bus coupled to a device that provides a communication signal to the redriver circuit (e.g., the redriver circuit level shifts and / or redrives to a device in another voltage domain). The redriver circuit samples the impedance of the bus to determine whether the device is still providing the communication signal, or whether the device has stopped providing the communication signal, in which case the bus coupled to the device is in a high impedance state. In one example, the redriver circuit samples the impedance of the bus by injecting current into the bus (e.g., by controlling a current source)—e.g., when a clock and / or data signal on the bus transitions to a low state—and monitors the voltage on the bus in response to the injected current. In an example, a pull-down resistor is coupled to the bus. If the bus is still being driven, the injected current will have a relatively small effect on the voltage of the bus. However, if the bus is not being driven (e.g., in a high impedance state), the injected current will have a larger effect on the voltage of the bus due to the pull-down resistor detected by the redriver circuit (e.g., using a comparator). The value of the pull-down resistor and the amount of current injected are selected so that a voltage is detected across the pull-down resistor when the bus is in a high impedance state, but also so that this voltage is insufficient to be interpreted as a high or asserted signal on the bus. When a high impedance state is detected on the bus, the communication channel that is level shifting and / or redriving the signal from the bus is disabled, and the redriver circuit again monitors the first signal edge, as described above. In this way, the redriver circuit monitors both sides of the bus and detects the direction of the communication signal to perform level shifting and / or redriving on the communication signal in the direction of data transmission.

[0015] Figure 1A block diagram of a system 100 in some examples is shown. The system 100 shows a redriver circuit 102, a first voltage domain 104, and a second voltage domain 106. Each voltage domain 104, 106 includes one or more devices 108, 110, respectively, that communicate with devices in the other voltage domain. Thus, the redriver circuit 102 is coupled to one or more devices 108 in the first voltage domain 104 through a first bus 107a and to one or more devices 110 in the second voltage domain 106 through a second bus 107b, and facilitates communication between the devices 108 in the first voltage domain 104 and the devices 110 in the second voltage domain 106. Although the buses 107a, 107b are referred to separately, in some examples, the buses 107a, 107b are part of the same bus (e.g., a clock bus or a data bus) that couples the devices 108 in the first voltage domain 104 to the devices 110 in the second voltage domain 106. In other examples, the redriver circuit 102 is coupled to the devices 108, 110 in each voltage domain 104, 106 by more than one bus. In a specific example of an SPMI interface utilizing a two-wire bus (e.g., a clock signal bus and a data signal bus), the redriver circuit 102 is coupled to the devices 108, 110 in each voltage domain 104, 106 by two buses. As described above, the redriver circuit 102 enables bidirectional communication while facilitating half-duplex communication by detecting the start of a signal transmission from the first voltage domain 104 or the second voltage domain 106, preferably by detecting a first signal edge of an input signal.

[0016] As described above, in some examples, the devices 108 in the first voltage domain 104 operate at a first I / O voltage level, while the devices 110 in the second voltage domain 106 operate at a second I / O voltage level that is different from the first I / O voltage level. In these examples, the redriver circuit 102 both level-shifts and redrives the signals originating from the voltage domain 104, 106 from which the first signal edge was first detected. In other examples, the devices 108 in the first voltage domain 104 and the devices 110 in the second voltage domain 106 operate at approximately the same I / O voltage level, and thus the redriver circuit 102 redrives the signals from the voltage domain 104, 106 from which the first signal edge was first detected, but does not necessarily perform level shifting of the signals between the voltage domains 104, 106. In some examples, even without voltage shifting, redriving the signals allows for driving larger capacitive loads than if the redriver circuit 102 were not present between the devices 108, 110.

[0017] As described in further detail below, the redriver circuit 102 is also configured to sample the impedance of the bus 107a, 107b coupled to the device providing the communication signal to the redriver circuit 102. The redriver circuit 102 samples the impedance of the bus 107a, 107b to determine whether the device 108, 110 is still providing the communication signal, or whether the device 108, 110 has stopped providing the communication signal, in which case the bus 107a, 107b coupled to the device 108, 110 is in a high impedance state (e.g., an idle state). When a high impedance state is detected on the bus 107a, 107b, the redriver circuit 102 disables the communication channel that is level shifting and / or redriving the signal from the bus 107a, 107b, and the redriver circuit 102 again monitors the first signal edge as described above. In this manner, the redriver circuit monitors both sides of the bus 107a, 107b and detects the direction of the communication signal to perform level shifting and / or redriving on the communication signal in the direction of data transmission.

[0018] Figure 2 Show above about Figure 1 The depicted system 100 includes a more detailed schematic diagram of a redriver circuit 102. Figure 2 In the example of , the redriver circuit 102 is used in the example SPMI interface and is shown coupled to a plurality of devices 108a-108n in the first voltage domain 104 and to a plurality of devices 110a-110n in the second voltage domain 106. In other examples, there is only a single device 108 in the first voltage domain 104 and / or only a single device 110 in the second voltage domain 106. In the example, for the purpose of implementing the communication protocol between the devices 108, 110, the devices 108, 110 are configured to act as a master device or a slave device. In addition, in Figure 2 In the example of , the redriver circuit 102 is coupled to the devices 108a-108n via a first clock bus 112 (e.g., of a two-wire SPMI interface) and a first data bus 114. Similarly, the redriver circuit 102 is coupled to the devices 110a-110n via a second clock bus 116 and a second data bus 118. Pull-down resistors 120, 122, 124, 126 are coupled to the buses 112, 114, 116, 118, respectively. The pull-down resistors 120, 122, 124, 126 are also coupled to a ground node.

[0019] The redriver circuit 102 includes a controller 150 that is configured to perform various functionalities described herein. In some examples, the controller 150 is an integrated circuit or a processing device. The scope of the present disclosure is not limited by the particular form of the controller 150. The functionality of the controller 150 is described more fully below.

[0020] The redriver circuit 102 includes a first port 152 configured to couple to the first clock bus 112, a second port 154 configured to couple to the second clock bus 116, a third port 156 configured to couple to the first data bus 114, and a fourth port 158 ​​configured to couple to the second data bus 118. Through the ports 152, 154, 156, 158, the redriver circuit 102 is able to send and receive communication signals to and from various devices 108 in the first voltage domain 104 and various devices 110 in the second voltage domain 106, respectively. The controller 150 is coupled to each of the ports 152, 154, 156, 158 as well as various other elements of the redriver circuit 102, as further described below.

[0021] The redriver circuit 102 includes a first communication channel 137 including a receiver 138, a delay element 140, and a driver 142. The first communication channel 137 is configured to redrive an input signal received from a first port 152 to a second port 154 as an output signal. Figure 2 In a specific example, the input signal to the first communication channel 137 and the output signal from the first communication channel are clock signals. In some examples, the first communication channel 137 is also configured to convert the input clock signal received from the first port 152 to a first I / O voltage limit (V IOA ) to a first voltage domain 104 having a first I / O voltage limit (V IOB )'s second voltage domain 106.

[0022] The redriver circuit 102 includes a second communication channel 143, which includes a receiver 144, a delay element 146, and a driver 148. The second communication channel 143 is configured to redrive an input signal received from the second port 154 to the first port 152 as an output signal. Figure 2 In a specific example, the input signal to the second communication channel 143 and the output signal from the second communication channel are clock signals. In some examples, the second communication channel 143 is also configured to receive the input clock signal from the second port 154 from the second voltage domain 106 (V IOB ) is level-shifted to the first voltage domain 104 (V IOA );

[0023] The redriver circuit 102 also includes a third communication channel 167 (including a receiver 168, a delay element 170, and a driver 172) and a fourth communication channel 173 (including a receiver 174, a delay element 176, and a driver 178) that are functionally similar to the first communication channel 137 and the second communication channel 143 described above, except that they are coupled to the third port 156 and the fourth port 158 ​​instead of the first port 152 and the second port 154. Figure 2 In a specific example, the input signals to and output signals from the third communication channel 167 and the fourth communication channel 173 are data signals. In some examples, the third communication channel 167 is also configured to receive the input data signal from the third port 156 from the first voltage domain 104 (V IOA ) is level-shifted to the second voltage domain 106 (V IOB Similarly, the fourth communication channel 173 is also configured to receive the input data signal from the fourth port 158 ​​from the second voltage domain 106 (V IOB ) is level-shifted to the first voltage domain 104 (V IOA ).

[0024] Each of the receivers 138, 144, 168, 174 functions in a similar manner. Specifically, the receiver 138 is configured to receive an input signal from the first port 152. Similarly, the receiver 144 is configured to receive an input signal from the second port 154; the receiver 168 is configured to receive an input signal from the third port 156; and the receiver 174 is configured to receive an input signal from the fourth port 158. The receivers 138, 144, 168, 174 generate signals based on the received input signals and provide the generated signals to the corresponding delay elements 140, 146, 170, 176. In one example, the receivers 138, 144, 168, 174 are comparators that meet specific threshold levels defined by the SPMI specification.

[0025] The delay elements 140, 146, 170, 176 introduce a delay to each of the communication channels 137, 143, 167, 173 to ensure that the control path (e.g., the functionality performed by the controller 150) is faster than the data path (e.g., through the communication channels 137, 143, 167, 173) so that the controller 150 can enable the appropriate one of the communication channels 137, 143, 167, 173 while avoiding the loss of signal data between the device 108 in the voltage domain 104 and the device 110 in the voltage domain 106. The purpose of introducing the delay will be described in more detail below. Each delay element 140, 146, 170, 176 provides its delayed signal to the corresponding driver 142, 148, 172, 178. In one example, the delay elements 140, 146, 170, 176 are inverter chains that can be programmed by adjusting the number of inverter stages and the RC loads of the inverter stages.

[0026] Drivers 142, 148, 172, 178 each drive an output signal to its associated port 154, 152, 158, 156, respectively, and in some cases perform level shifting on the signals received from its respective delay elements 140, 146, 170, 176. For example, drivers 142, 172 level shift signals from delay elements 140, 170 from the first voltage domain 104 to the second voltage domain 106. Similarly, drivers 148, 178 level shift signals from delay elements 146, 176 from the second voltage domain 106 to the first voltage domain 104. In an example, an enable signal may be provided to one or more of the following: drivers 142 (ENCLKB), 148 (ENCLKA), 172 (ENDATB), 178 (ENDATA). When the enable signal is provided, it enables the corresponding driver 142, 148, 172, 178 (and thus the corresponding communication channels 137, 143, 167, 173). In this way, each of the communication channels 137, 143, 167, 173 is configured to redrive signals from one voltage domain 104, 106 to another voltage domain, as well as level shift those signals from the first voltage domain 104 to the second voltage domain 106 or vice versa, facilitating bidirectional communication between the devices 108, 110. Moreover, and as will be described in further detail below, only one of the first communication channel 137 and the second communication channel 143 is enabled at a time; similarly, only one of the third communication channel 167 and the fourth communication channel 173 is enabled at a time. Thus, the redriver circuit 102 also facilitates half-duplex communication between the devices 108, 110.

[0027] The controller 150 is configured to receive certain signals from the rest of the redriver circuit 102 and to control various aspects of the redriver circuit 102 based at least in part on those received signals. For example, the controller receives an indication of whether a signal received at one of the ports 152, 154, 156, 158 is asserted (e.g., from a comparator coupled to the port, described further below); an indication of whether a signal received at one of the ports 152, 154, 156, 158 is deasserted (e.g., from another comparator coupled to the port, described further below); and / or an indication of whether a bus 112, 116, 114, 118 coupled to one of the ports 152, 154, 156, 158 is in a high impedance state (e.g., from one of the comparators 134, 136, 164, 166, described further below). Based on the signals received by the controller 150 , the controller 150 is configured to enable or disable the various communication channels 137 , 143 , 167 , 173 and control the various current sources 130 , 132 , 160 , 162 , which are also described further below.

[0028] The controller 150 of the redriver circuit 102 is configured to detect a first signal edge indicating the start of a signal transmission on the bus 112, 114, 116, 118. Although not shown for simplicity, in one example, a comparator is coupled to each of the ports 152, 154, 156, 158. These comparators are configured to compare the voltage at the ports 152, 154, 156, 158 to a reference voltage. In an example, the reference voltage is set at a level above which it indicates that a signal is asserted for a particular voltage domain 104, 106. For example, the reference voltage is a value slightly less than the I / O voltage limit of the voltage domain 104, 106 to which the port 152, 154, 156, 158 is configured to couple (e.g., within 10%).

[0029] For example, a comparator coupled to the first port 152 or the third port 156 compares these voltages to a reference voltage (VBIASA) that is slightly less than the I / O voltage limit of the first voltage domain 104, such that the output of the comparator of the first port 152 or the third port 156 is asserted when the received signal voltage indicates an asserted signal of the first voltage domain 104 (e.g., which would correspond to a rising edge). In a specific example where one of the voltage domains 104 corresponds to an SPMI interface having an I / O voltage limit of 1.8V, the comparator compares the voltage of the signal received at the ports 152, 156 to a reference voltage of approximately 1.62V (e.g., less than 10% of 1.8V). Similarly, a comparator coupled to the second port 154 or the fourth port 158 ​​compares these voltages to a reference voltage (VBIASA) that is slightly less than the I / O voltage limit of the second voltage domain 106, such that the output of the comparator of the second port 154 or the fourth port 158 ​​is asserted when the received signal voltage indicates an asserted signal of the second voltage domain 106 (e.g., which would correspond to a rising edge). In an example where the other voltage domain 106 corresponds to a processor / SoC interface with an I / O voltage limit of 1.2V, the comparator compares the voltage of the signal received at the ports 154, 158 to a reference voltage of approximately 1.08V (e.g., less than 10% of 1.2V). In some examples, the clock and data signals may be asserted at different voltages, and therefore their reference voltages are also different. However, for simplicity of explanation, it is assumed that the clock signal and the data signal from one of the voltage domains 104, 106 are asserted at approximately the same voltage.

[0030] The controller 150 of the redriver circuit 102 is also configured to detect when a signal received from the bus 112, 114, 116, 118 is deasserted. In addition, although not shown for simplicity, in one example, additional comparators are coupled to each of the ports 152, 154, 156, 158. These comparators are configured to compare the voltage at the ports 152, 154, 156, 158 with a reference voltage that is set at a level below which it indicates a deasserted signal. For example, the reference voltage is a value slightly greater than the ground node voltage (e.g., 0.1V). When the received signal voltage indicates a deasserted signal, the outputs of these comparators are asserted, and when the received signal voltage indicates an asserted signal, the outputs of these comparators are deasserted.

[0031] In addition to detecting asserted signals (or rising edges) and deasserted signals (or falling edges) at the ports 152, 154, 156, 158, the controller 150 is also configured to sample the impedance at each port 152, 154, 156, 158. In particular, and as will be described in further detail below, the controller 150 is configured to sample the impedance at each port 152, 154, 156, 158 in response to a signal at one of the ports 152, 154, 156, 158 being deasserted when the corresponding channel of the port is enabled. For example, if the first communication channel 137 is enabled, the controller 150 is configured to sample the impedance at the first port 152 in response to detecting that an input signal (e.g., a clock signal) of the first port 152 is deasserted. The controller 150 functions similarly for the other ports 154, 156, 158 and their corresponding communication channels 143, 167, 173, respectively.

[0032] The controller 150 is configured to sample the impedance at the first port 152 as described above, for example, to detect a high impedance state of the first clock bus 112 coupled to the first port 152, the high impedance state indicating that the device 108 coupled to the first clock bus 112 is not driving the first clock bus 112. In one example, the current source 130 is coupled to the first port 152. The controller 150 is configured to control the current source 130, for example, to inject current into the first port 152. In other examples, the amount of current injected can also be controlled by the controller 150. The comparator 134 includes a non-inverting terminal coupled to the first port 152 and an inverting terminal coupled to a reference voltage source (whose value is given by VBIASA).

[0033] For example, when a device 108 coupled to the first clock bus 112 is driving the first clock bus 112, the impedance experienced at the first port 152 is the impedance of the device 108 driver, which is relatively low (e.g., approximately 50 ohms). However, when the device 108 is not driving the first clock bus 112, the device 108 driver is in a high impedance state, and thus the impedance experienced at the first port 152 is approximately the resistance of the pull-down resistor 120, which may have a minimum value of approximately 125 kilo-ohms, for example. Therefore, if the controller 150 causes the current source 130 to inject a current (e.g., approximately 2 uA) into the first port 152 when the device 108 is driving the first clock bus 112, the voltage dropped across the pull-down resistor 120 is relatively small (e.g., less than VBIASA) because the impedance of the device 108 driver is much lower than the impedance of the pull-down resistor 120. Therefore, the output of the comparator 134 is not asserted. However, if the controller 150 causes the current source 130 to inject current into the first port 152 when the device 108 is not driving the first clock bus 112, the voltage dropped across the pull-down resistor is larger (e.g., exceeds VBIASA) because the device 108 driver itself is now in a high impedance state. Therefore, the comparator 134 output is asserted, indicating that the first clock bus 112 is in a high impedance state (e.g., an idle state). The specific values ​​of the pull-down resistor 120 resistance, the current injected by the current source 130, and the voltage VBIASA are exemplary and may be different than those described above while still achieving the described functionality for detecting a high impedance bus state.

[0034] In an example, the controller 150 is also configured to control the value of VBIASA. As described above, the pull-down resistor 120 is coupled to the first clock bus 112 and the ground node. Therefore, when the first clock bus 112 is not driven by the device 108 (e.g., in a high impedance state) and current is injected into the first port 152 by the current source 130, the voltage drops across the pull-down resistor 120. However, when the first clock bus 112 is being driven by the device 108, injecting current into the first port 152 has a relatively small effect on the first clock bus 112 voltage. As described above, the value of the pull-down resistor 120 and the amount of current injected by the current source 130 are selected so that the voltage across the pull-down resistor 120 is detected when the first clock bus 112 is in a high impedance state, but also so that this voltage is insufficient to be interpreted as a high or asserted signal on the first clock bus 112. In an example, the controller 150 sets the value of VBIASA so that the voltage across the resistor 120 in response to injecting current through the current source 130 when the first clock bus 112 is in a high impedance state causes the comparator 134 to assert its output. However, the value of VBIASA is also set so that a voltage increase on the first clock bus 112 in response to injecting current through the current source 130 when the first clock bus 112 is driven by the device 108 does not cause the comparator 134 to assert its output. The current sources 132, 160, 162 and the comparators 136, 164, 166 function with respect to the ports 154, 156, 158 in a manner similar to the current sources 130 and the comparators 134 described above with respect to the first port 152.

[0035] The functions of the controller 150 and the redriver circuit 102 are generally related to Figure 3-5 Further Description In one example, as described above, the redriver circuit 102 is used in an SPMI interface, where the buses 112, 116 and the buses 114, 118 comprise a two-wire bus of the SPMI interface. Figure 3A state diagram 300 is shown illustrating the functionality of the controller 150 and the redriver circuit 102 with respect to facilitating level shifting and / or redriving of a clock signal (e.g., on a bus 112, 116) between a device 108 in a first voltage domain 104 and a device 110 in a second voltage domain 106. In an example, a device 108, 110 as a master provides a clock signal that is used for communication to and from a corresponding slave device. For example, when a device 108, 110 provides a clock signal to the redriver circuit 102 (detected by the redriver circuit 102 as a first signal edge), the device 108, 110 is assumed to be a master until the driven clock bus 112, 116 transitions to a high impedance state. Thus, the redriver circuit 102 continues to drive the first detected clock signal from one voltage domain 104, 106 to the other voltage domain until the driven clock bus 112, 116 transitions to a high impedance state. Figure 4 A timing diagram 400 corresponding to this functionality is shown. The timing diagram 400 includes waveforms representing: a signal on the first clock bus 112 (SCLKA) and a signal on the second clock bus 116 (SCLKB); a control signal for the current injected by the current source 130 (ICC_ENCLKA) and a control signal for the current injected by the current source 132 (ICC_ENCLKB); and an enable signal for the first communication channel 137 (ENCLKB, which enables the driver 142 of the first communication channel 137) and an enable signal for the second communication channel 143 (ENCLKA, which enables the driver 148 of the second communication channel 143).

[0036] Initially, for example Figure 4 As shown in portion 402 of , upon a power-on or reset event of the device including the voltage domains 104, 106 and the redriver circuit 102, the state diagram 300 begins at state 302. In state 302, both clock buses 112, 116 are in a high impedance state (e.g., not driven by any device 108, 110). No device 108, 110 is driving the clock buses 112, 116, and thus neither the first communication channel 137 nor the second communication channel 143 of the redriver circuit 102 is enabled, and thus the controller 150 does not assert ENCLKA or ENCLKB. Furthermore, in state 302, it has been determined (e.g., due to a power-on or reset event) that both clock buses 112, 116 are in a high impedance state, and thus the controller 150 does not cause either current source 130, 132 to inject current, and thus ICC_ENCLKA and ICC_ENCLKB are also deasserted.

[0037] Subsequently, during time region 408, the controller 150 detects a first signal edge on the clock bus 112 and the state diagram 300 therefore continues to state 304. For purposes of explanation, it is assumed that the first signal edge is first detected on the first clock bus 112 when SCLKA goes high or is asserted before SCLKB, and therefore the state diagram 300 continues to state 306. In state 306, the controller 150 enables the first communication channel 137 by asserting ENCLKB (also in time region 408), which enables the driver 142 of the first communication channel 137. When enabled, the driver 142 level shifts and / or re-drives the clock signal received from the first clock bus 112 to the second clock bus 116. This is done in state 306. Figure 4 402 is shown as a re-driving of the signal. The second communication channel 143 remains disabled (e.g., ENCLKA is de-asserted). As described above, the delay element 140 in the first communication channel 137 provides the controller 150 with sufficient time to assert ENCLKB before the signal (e.g., the first signal edge) from the first port 152 causing the state change arrives at the driver 142. This is reflected in the timing diagram 400, where SCLKB is delayed from SCLKA.

[0038] Subsequently, the state diagram 300 proceeds to state 308, where the first clock bus 112 (SCLKA) is monitored by the controller 150 to detect whether SCLKA is de-asserted. As described above, in an example, the controller 150 monitors a comparator output that is asserted when the signal on the first clock bus 112 goes low or is de-asserted. While SCLKA remains high or asserted, the state diagram 300 remains in states 306 and 308. However, when SCLKA goes low or is de-asserted, the state diagram 300 continues to state 310.

[0039] In state 310, the controller 150 samples the impedance at the first port 152 coupled to the first clock bus 112, as described above. In particular, the controller 150 asserts ICC_ENCLKA causing the current source 130 to inject current into the first port 152. This is reflected in the timing diagram 400, where ICC_ENCLKA is asserted (e.g., as two pulses 410, 412) while SCLKA is de-asserted. The state diagram 300 continues in state 312, where the controller 150 determines whether the first clock bus 112 is in a high impedance state, for example, by monitoring the output of the comparator 134 as described above. For example, when the first clock bus 112 is driven by the device 108, injecting current into the first port 152 does not cause the voltage of the first clock bus 112 to rise above the reference voltage VBIASA for the comparator 134. This is reflected in the timing diagram 400, where the first assertion of ICC_ENCLKA does not cause the voltage of SCLKA to rise above VBIASA because the device 108 drives SCLKA low. In state 312, if the controller 150 determines that the first clock bus 112 is not in a high impedance state (e.g., the controller 150 determines that HIZCLKA is not a high value), then the state diagram 300 returns to state 308 and, depending on whether SCLKA is low or deasserted, returns to one of the states 306, 310 as described above.

[0040] However, when the first clock bus 112 is not driven by the device 108, the injection of current into the first port 152 causes the voltage across the pull-down resistor 120 to drop, which is greater than the reference voltage VBIASA of the comparator 134 (reflected at 406), which causes the output of the comparator 134 to be asserted. Therefore, in response to the output of the comparator 134 being asserted, the controller 150 determines that the first clock bus 112 is in a high impedance state. This is reflected in the timing diagram 400, where the second assertion of ICC_ENCLKA 412 (after SCLKA has transitioned to a high impedance state, indicated by the dashed line) causes the voltage of SCLKA to exceed VBIASA at 406. In state 312, if the controller 150 determines that the first clock bus 112 is in a high impedance state, the state diagram 300 returns to state 302 and the controller 150 disables the first communication channel 137 and waits to receive a first signal edge from the device 108 in the first voltage domain 104 or the device 110 in the second voltage domain 106, respectively.

[0041] Referring back to state 304, in another example, when SCLKB goes high or is asserted before SCLKA, the controller 150 detects a first signal edge from the second clock bus 116. This is reflected during time region 413 of portion 404 of the timing diagram 400. In this case, the state diagram 300 continues to state 314. States 314, 316, 318, and 320 are generally similar to states 306, 308, 310, 312 described above, but in the opposite direction of communication travel. For example, in state 314, the controller 150 enables the second communication channel 143 by asserting ENCLKA (also during time region 413), which enables the driver 148 of the second communication channel 143. When enabled, the driver 148 level shifts and / or re-drives the clock signal received from the second clock bus 116 to the first clock bus 112. The example of portion 404 of timing diagram 400 illustrates the level shifting of the clock signal from a higher voltage level to a lower voltage level. The first communication channel 137 remains disabled (e.g., ENCLKB is deasserted). As described above, the delay element 146 in the second communication channel 143 provides sufficient time for the controller 150 to assert ENCLKA before the signal (e.g., the first signal edge) from the second port 154 causing the state change arrives at the driver 148. This is reflected in portion 404 of timing diagram 400, where SCLKA is delayed from SCLKB.

[0042] Subsequently, the state diagram 300 proceeds to state 316, where the second clock bus 116 (SCLKB) is monitored by the controller 150 to detect whether SCLKB is de-asserted. As described above, in an example, the controller 150 monitors a comparator output that is asserted when the signal on the second clock bus 116 goes low or is de-asserted. When SCLKB remains high or asserted, the state diagram 300 remains in states 314 and 316. However, when SCLKB goes low or is de-asserted, the state diagram 300 continues to state 318.

[0043] In state 318, the controller 150 samples the impedance at the second port 154 coupled to the second clock bus 116, as described above. Specifically, the controller 150 asserts ICC_ENCLKA causing the current source 132 to inject current into the second port 154. This is reflected in the timing diagram 400, where ICC_ENCLKB is asserted and SCLKB is de-asserted (e.g., as two pulses 414, 416). The state diagram 300 continues in state 320, where the controller 150 determines whether the second clock bus 116 is in a high impedance state, for example, by monitoring the output of the comparator 136 as described above. For example, when the second clock bus 116 is driven by the device 110, injecting current into the second port 154 does not cause the voltage of the second clock bus 116 to rise above the reference voltage VBIASB for the comparator 136. This is reflected in the timing diagram 400 at 418, where the assertion 414 of ICC_ENCLKB does not cause the voltage of SCLKB to rise above VBIASB because the device 110 is driving SCLKB low. In state 320, if the controller 150 determines that the second clock bus 116 is not in a high impedance state, the state diagram 300 returns to state 316 and, depending on whether SCLKB is low or de-asserted, returns to one of the states 314, 318 as described above.

[0044] However, when the second clock bus 116 is not driven by the device 110, injecting current into the second port 154 causes the voltage across the pull-down resistor 124 to drop, which is greater than the reference voltage VBIASB of the comparator 136, which causes the output of the comparator 136 to be asserted. Therefore, in response to the output of the comparator 136 being asserted, the controller 150 determines that the second clock bus 116 is in a high impedance state. This is reflected in the timing diagram 400 at point 420. In state 320, if the controller 150 determines that the second clock bus 116 is in a high impedance state, the state diagram 300 returns to state 302 and the controller 150 disables the second communication channel 143 and waits to receive a first signal edge from the device 108 in the first voltage domain 104 or the device 110 in the second voltage domain 106, respectively.

[0045] As described above, the redriver circuit 102 thus monitors both sides of the clock bus (e.g., the first clock bus 112 and the second clock bus 116) and detects the direction of the received communication signal by detecting the first signal edge arriving from the device 108 in the first voltage domain 104 or the device 110 in the second voltage domain 106, respectively. The redriver circuit 102 performs level shifting and / or redriving on the communication signal in the direction of data transmission. At the same time, the redriver circuit 102 prevents data transmission in the opposite direction by enabling only one of the first communication channel 137 and the second communication channel 143 at a time, thereby enabling bidirectional, half-duplex communication between the device 108 in the first voltage domain 104 and the device 110 in the second voltage domain 106, respectively.

[0046] Figure 5 A state diagram 500 is shown illustrating the functionality of the controller 150 and the redriver circuit 102 with respect to facilitating level shifting and / or redriving of data signals (e.g., on data buses 114, 118) between a device 108 in a first voltage domain 104 and a device 110 in a second voltage domain 106. In an example, a device 108, 110 as a master provides a clock signal (as described above) along with the data signal, which is used for communication to and from the corresponding slave device. However, unlike the clock signal which is always provided by the master, in a bidirectional communication interface, the master also expects to receive data from one or more slave devices. Furthermore, while the redriver circuit 102 itself does not perform any bus arbitration functionality, the redriver circuit 102 is configured to allow the devices 108, 110 to perform such bus arbitration while still facilitating bidirectional, half-duplex communication between the devices 108, 110 in different voltage domains 104, 106.

[0047] As mentioned above about Figure 3 , upon a power-on or reset event of the devices encompassing the voltage domains 104, 106 and the redriver circuit 102, the state diagram 500 begins at state 502. In state 502, both the data buses 114, 118 are in a high impedance state (e.g., not driven by any device 108, 110). No device 108, 110 is driving the data buses 114, 118, and therefore neither the third communication channel 167 nor the fourth communication channel 173 of the redriver circuit 102 is enabled, and therefore the controller 150 does not assert ENDATA or ENDATB. Furthermore, in state 502, it has been determined (e.g., due to a power-on or reset event) that both the data buses 114, 118 are in a high impedance state, and therefore the controller 150 does not cause either current source 160, 162 to inject current, and therefore ICC_ENDATA and ICC_ENDATB are also deasserted.

[0048] Subsequently, the controller 150 detects a first signal edge on one of the data buses 114, 118 and the state diagram 500 therefore continues to state 504. For purposes of explanation, it is assumed that the first signal edge is first detected on the first data bus 114 when SDATA goes high or is asserted before SDATB, and therefore the state diagram 500 continues to state 506. In state 506, the controller 150 enables the third communication channel 167 by asserting ENDATB, which enables the driver 172 of the third communication channel 167. When enabled, the driver 172 level shifts and / or re-drives the data signal received from the first data bus 114 to the second data bus 118. The fourth communication channel 173 remains disabled (e.g., ENDATA is de-asserted). As described above, the delay element 170 in the third communication channel 167 provides the controller 150 with sufficient time to assert ENDATB before the signal (e.g., the first signal edge) from the third port 156 that causes the state change arrives at the driver 172. The effect of the delay element 170 is similar to Figure 4 The effects shown in and described above.

[0049] Subsequently, the state diagram 500 proceeds to state 508, where the controller 150 determines whether a bus arbitration start condition has occurred. As described above, although the redriver circuit 102 itself does not perform any bus arbitration functionality, the redriver circuit 102 is configured to allow the devices 108, 110 to perform such bus arbitration. In the example where the redriver circuit 102 is used for an SPMI interface, the bus arbitration start condition is maintained by the data signal (e.g., received from the first data bus 114) being asserted and the clock signal (e.g., received from the first clock bus 112) being deasserted for at least the bus turnaround time (T BT ). In the example, T BT The value of is determined by the SPMI specification. The occurrence of this bus arbitration start condition indicates to the controller 150 that bus arbitration will occur between the devices 108, 110, and thus the state diagram 500 proceeds to block 510.

[0050] The controller 150 is configured to facilitate various bus arbitration schemes, e.g., as defined in one or more specifications of the interface over which the redriver circuit 102 facilitates communication. In one example, the bus arbitration scheme that occurs in state 510 lasts for a predetermined duration (e.g., a number of clock cycles). Thus, in state 510, the controller 150 facilitates the bus arbitration scheme (e.g., by enabling and disabling the third communication channel 167 and the fourth communication channel 173, respectively), and when the predetermined duration has elapsed, the bus arbitration is complete and the state diagram continues back to state 502, as described above.

[0051] In state 508, if the controller 150 determines that the bus arbitration start condition has not occurred, then the state diagram 500 proceeds to block 512. For example, if SDATA is deasserted, SCLKA is asserted, or SCLKA is deasserted for less than T BT , then the bus arbitration start condition has not occurred. In state 512, the controller 150 continues to enable the third communication channel 167 by asserting ENDATB, while continuing to disable the fourth communication channel 173 by deasserting ENDATA. From state 512, the state diagram 500 proceeds to state 514, where the first data bus 114 (SDATA) and the first clock bus 112 (SCLKA) are monitored by the controller 150 to detect whether SDATA and SCLKA are both deasserted. As described above, in an example, the controller 150 monitors the comparator outputs, one of which is asserted when the signal on the first clock bus 112 goes low or is deasserted, and the other of which is asserted when the signal on the first data bus 114 goes low or is deasserted. When SDATA and / or SCLKA remain high or are asserted, the state diagram 500 remains in states 512 and 514. However, when SDATA and SCLKA go low or are deasserted, the state diagram 500 continues to state 516.

[0052] In state 516, the controller 150 samples the impedance at the third port 156 coupled to the first data bus 114, as described above. In particular, the comparator 150 asserts ICC_ENDATA to cause the current source 160 to inject current into the third port 156. The state diagram 500 continues in state 518, where the controller 150 determines whether the first data bus 114 is in a high impedance state, for example, by monitoring the output terminal (HIZDATA) of the comparator 164 as described above. For example, when the first data bus 114 is driven by the device 108, injecting current into the third port 156 does not cause the voltage of the first data bus 114 to rise above the reference voltage VBIASA for the comparator 164. In state 518, if the controller 150 determines that the first data bus 114 is not in a high impedance state, the state diagram 500 returns to state 514 and, depending on whether SDATA and SCLKA are low or de-asserted, to one of states 512, 516 as described above.

[0053] However, when the first data bus 114 is not driven by the device 108, the injection of current into the third port 156 causes the voltage across the pull-down resistor 122 to drop, which is greater than the reference voltage VBIASB of the comparator 164, which causes the output of the comparator 164 to be asserted. Therefore, in response to the output of the comparator 164 being asserted, the controller 150 determines that the first data bus 114 is in a high impedance state. In state 518, if the controller 150 determines that the first data bus 114 is in a high impedance state, the state diagram 500 returns to state 502 and the controller 150 disables the third communication channel 167 and waits for receiving a first signal edge from the device 108 in the first voltage domain 104 or the device 110 in the second voltage domain 106, respectively.

[0054] Referring back to state 504, in another example, when SDATB goes high or is asserted before SDATA, the controller 150 detects a first signal edge from the second data bus 118. In this case, the state diagram 500 continues to state 520. States 520, 522, 524, 526, 528, 530, and 532 are generally similar to states 506, 508, 510, 512, 514, 516, and 518 described above, but in the opposite direction of communication travel. For example, in state 520, the controller 150 enables the fourth communication channel 173 by asserting ENDATB, which enables the driver 178 of the fourth communication channel 173. When enabled, the driver 178 level shifts and / or re-drives the data signal received from the second data bus 118 to the first data bus 114. The third communication channel 167 remains disabled (e.g., ENDATB is de-asserted). As described above, the delay element 176 in the fourth communication channel 173 provides sufficient time for the controller 150 to assert ENDATA before the signal (eg, the first signal edge) from the fourth port 158 ​​that causes the state change arrives at the driver 178 .

[0055] Subsequently, state diagram 500 proceeds to state 522, where controller 150 determines whether a bus arbitration start condition has occurred. As described above, in one example, a bus arbitration start condition is caused by a data signal (e.g., received from second data bus 118) remaining asserted while a clock signal (e.g., received from second clock bus 116) remains deasserted for at least T BTThe occurrence of this bus arbitration start condition indicates to the controller 150 that bus arbitration will occur between the devices 108, 110, and thus the state diagram 500 proceeds to block 524. As described above, in state 524, the controller 150 facilitates the bus arbitration scheme (e.g., by enabling and disabling the third communication channel 167 and the fourth communication channel 173, respectively), and when the predetermined duration has elapsed, the bus arbitration is complete and the state diagram continues back to state 502, as described above.

[0056] In state 522, if the controller 150 determines that the bus arbitration start condition has not occurred, then the state diagram 500 proceeds to block 526. For example, if SDATB is deasserted, SCLKB is asserted, or SCLKB is deasserted for less than T BT , then the bus arbitration start condition has not occurred. In state 526, the controller 150 continues to enable the fourth communication channel 173 by asserting ENDATA, while continuing to disable the third communication channel 167 by deasserting ENDATB. From state 526, the state diagram 500 proceeds to state 528, wherein the second data bus 118 (SDATB) and the second clock bus 116 (SCLKB) are monitored by the controller 150 to detect whether SDATB and SCLKB are both deasserted. As described above, in an example, the controller 150 monitors the comparator outputs, one of which is asserted when the signal on the second clock bus 116 goes low or is deasserted, and the other of which is asserted when the signal on the second data bus 118 goes low or is deasserted. When SDATB and / or SCLKB remain high or are asserted, the state diagram 500 remains in states 526 and 528. However, when SDATB and SCLKB go low or are deasserted, the state diagram 500 continues to state 530.

[0057] In state 530, the controller 150 samples the impedance at the fourth port 158 ​​coupled to the second data bus 118, as described above. In particular, the controller 150 asserts ICC_ENDATB causing the current source 162 to inject current into the fourth port 158. The state diagram 500 continues in state 532, where the controller 150 determines whether the second data bus 118 is in a high impedance state, e.g., by monitoring the output terminal (HIZDATB) of the comparator 166 as described above. For example, when the second data bus 118 is driven by the device 110, injecting current into the fourth port 158 ​​does not cause the voltage of the second data bus 118 to rise above the reference voltage VBIASB for the comparator 166. In state 532, if the controller 150 determines that the second data bus 118 is not in a high impedance state (HIZDATB is not high), the state diagram 500 returns to state 528 and, depending on whether SDATB and SCLKB are low or deasserted, returns to one of states 526, 530 as described above.

[0058] However, when the second data bus 118 is not driven by the device 110, the injection of current into the fourth port 158 ​​causes the voltage across the pull-down resistor 126 to drop, which is greater than the reference voltage VBIASB of the comparator 166, which causes the output of the comparator 166 to be asserted. Therefore, in response to the output of the comparator 166 being asserted, the controller 150 determines that the second data bus 118 is in a high impedance state. In state 532, if the controller 150 determines that the second data bus 118 is in a high impedance state (HIZDATB is high), the state diagram 500 returns to state 502 and the controller 150 disables the fourth communication channel 173 and waits to receive a first signal edge from the device 108 in the first voltage domain 104 or the device 110 in the second voltage domain 106, respectively.

[0059] As described above, the redriver circuit 102 thus monitors both sides of the data bus (e.g., the first data bus 114 and the second data bus 118) and detects the direction of the received communication signal by detecting the first signal edge arriving from the device 108 in the first voltage domain 104 or the device 110 in the second voltage domain 106, respectively. The redriver circuit 102 performs level shifting and / or redriving on the communication signal in the direction of data transmission. In addition, the redriver circuit 102 facilitates the bus arbitration scheme between the devices 108, 110 by detecting the bus arbitration start condition, allowing the bus arbitration to occur and continuing to facilitate data transmission between the devices 108, 110 when completed. While facilitating data transmission in one direction, the redriver circuit 102 also prevents data transmission in the opposite direction by enabling only one of the third communication channel 167 and the fourth communication channel 173 at a time. Therefore, the redriver circuit 102 also implements bidirectional, half-duplex data communication between the device 108 in the first voltage domain 104 and the device 110 in the second voltage domain 106, respectively.

[0060] In this specification and claims, the terms "include" and "comprising" are open ended and thus mean "including but not limited to...". In addition, the term "coupled" or "coupled" means an indirect or direct connection. Thus, if a first device is coupled to a second device, the connection may be by a direct connection or by an indirect connection via other devices and connections. Similarly, a device coupled between a first component or location and a second component or location may be by a direct connection or by an indirect connection via other devices and connections. An element or feature "configured to" perform a task or function may be configured (e.g., programmed and / or structurally designed) at the time of manufacture by the manufacturer to perform the function and / or may be configured (or reconfigurable) by the user after manufacture to perform the function and / or other additional or alternative functions. The configuration may be programmed by the firmware and / or software of the device, by the construction and / or layout of the hardware components and the interconnection of the device or a combination thereof. In addition, the phrase "grounded" or similar terms include chassis ground, earth ground, floating ground, virtual ground, digital ground, common ground and / or any other form of ground connection that is applicable or suitable for the teachings of this specification. Unless otherwise stated, "about" preceding a value means + / - 10% of the stated value.

[0061] Modifications may be made in the described embodiments, and other embodiments are possible, within the scope of the claims.

Claims

1. A redriver circuit, comprising: a first port configured to be coupled to a first device via a first bus; a second port configured to be coupled to a second device via a second bus; a first communication channel having an input coupled to the first port and an output coupled to the second port, the first communication channel being configured to redrive an input signal and output the redriven input signal; a second communication channel having an input coupled to the second port and an output coupled to the first port, the second communication channel being configured to redrive an input signal and output the redriven input signal; and A controller configured to: enabling the first communication channel and disabling the second communication channel in response to detecting a first signal edge at the first port; in response to detecting a first signal edge at the second port, enabling the second communication channel and disabling the first communication channel; sampling an impedance at the first port in response to deasserting the input signal received at the first port while the first communication channel is enabled; and An impedance at the second port is sampled in response to de-asserting the input signal received at the second port while the second communication channel is enabled.

2. The redriver circuit of claim 1 , wherein: The first device is in a first voltage domain; the second device being in a second voltage domain; The first communication channel is configured to level shift the input signal received from the first port from the first voltage domain to the second voltage domain; and The second communication channel is configured to level shift the input signal received from the second port from the second voltage domain to the first voltage domain.

3. The redriver circuit of claim 1 , wherein: The first communication channel comprises: a first receiver having an input coupled to the first port and an output; a first delay element having an input coupled to the output of the first receiver and an output; and a first driver having an input coupled to the output of the first delay element and an output coupled to the second port; and The second communication channel comprises: a second receiver having an input coupled to the second port and an output; a second delay element having an input coupled to the output of the second receiver and an output; and A second driver has an input coupled to the output of the second delay element and an output coupled to the first port.

4. The redriver circuit of claim 1 , further comprising: a first current source coupled to the first port; A first comparator comprising: a non-inverting input terminal coupled to the first port; and an inverting input terminal coupled to a first reference voltage source; a second current source coupled to the second port; and A second comparator comprising: a non-inverting input terminal coupled to the second port; and an inverting input terminal coupled to a second reference voltage source; wherein the first bus has an impedance and is coupled to a first pull-down resistor, the first pull-down resistor being coupled to a ground node; and The second bus has an impedance and is coupled to a second pull-down resistor, wherein the second pull-down resistor is coupled to the ground node.

5. The redriver circuit of claim 4, wherein: When the controller samples the impedance at the first port, the controller is configured to: causing the first current source to inject current into the first port; and monitoring an output of the first comparator; When the controller samples the impedance at the second port, the controller is configured to: causing the second current source to inject current into the second port; and monitoring an output terminal of the second comparator; asserting the output of the first comparator indicating a high impedance state at the first port, and in response, the controller is configured to disable the first communication channel; and Assertion of the output of the second comparator indicates a high impedance state at the second port, and in response, the controller is configured to disable the second communication channel.

6. The redriver circuit of claim 1 , wherein the controller is further configured to: facilitating bus arbitration between the first device and the second device in response to detecting a bus arbitration start condition at the first port when the first communication channel is enabled, or detecting the bus arbitration start condition at the second port when the second communication channel is enabled; and In response to the bus arbitration being completed, the first communication channel and the second communication channel are disabled.

7. A redriver circuit comprising: a first port configured to be coupled to a first device via a first clock bus; a second port configured to be coupled to a second device via a second clock bus; a third port configured to be coupled to the first device via a first data bus; a fourth port configured to be coupled to the second device via a second data bus; a first communication channel configured to forward drive an input clock signal received from the first port to the second port as an output clock signal; a second communication channel configured to forward drive an input clock signal received from the second port to the first port as an output clock signal; a third communication channel configured to forward drive an input data signal received from the third port to the fourth port as an output data signal; a fourth communication channel configured to forward drive an input data signal received from the fourth port to the third port as an output data signal; and A controller configured to: enabling the first communication channel and disabling the second communication channel in response to detecting a start of a clock signal edge at the first port; enabling the second communication channel and disabling the first communication channel in response to detecting the start of a clock signal edge at the second port; responsive to detecting the start of a data signal edge at the third port, enabling the third communication channel and disabling the fourth communication channel; responsive to detecting the start of a data signal edge at the fourth port, enabling the fourth communication channel and disabling the third communication channel; sampling an impedance at the first port in response to deasserting the input clock signal received at the first port while the first communication channel is enabled; sampling an impedance at the second port in response to deasserting the input clock signal received at the second port when the second communication channel is enabled; sampling an impedance at the third port in response to deasserting the input data signal received at the third port when the third communication channel is enabled; and An impedance at the fourth port is sampled in response to de-asserting the input data signal received at the fourth port while the fourth communication channel is enabled.

8. The redriver circuit of claim 7, wherein: The first device is in a first voltage domain; the second device being in a second voltage domain; The first communication channel is configured to level shift the input clock signal received from the first port from the first voltage domain to the second voltage domain; the second communication channel being configured to level shift the input clock signal received from the second port from the second voltage domain to the first voltage domain; The third communication channel is configured to level shift the input data signal received from the third port from the first voltage domain to the second voltage domain; and The fourth communication channel is configured to level shift the input data signal received from the fourth port from the second voltage domain to the first voltage domain.

9. The redriver circuit of claim 7, wherein: The first communication channel comprises: a first receiver, configured to receive the input clock signal from the first port; a first delay element configured to receive a signal from the first receiver; and a first driver configured to receive a signal from the first delay element and drive the output clock signal to the second port; The second communication channel comprises: a second receiver, configured to receive the input clock signal from the second port; a second delay element for receiving a signal from the second receiver; and a second driver configured to receive a signal from the second delay element and drive the output clock signal to the first port; The third communication channel comprises: a third receiver, configured to receive the input data signal from the third port; a third delay element configured to receive a signal from the third receiver; and a third driver for receiving a signal from the third delay element and driving the output data signal to the fourth port; and The fourth communication channel comprises: a fourth receiver, configured to receive the input data signal from the fourth port; a fourth delay element, configured to receive a signal from the fourth receiver; and A fourth driver is configured to receive a signal from the fourth delay element and drive the output data signal to the third port.

10. The redriver circuit of claim 7, further comprising: a first current source coupled to the first port; A first comparator comprising: a non-inverting input terminal coupled to the first port; and an inverting input terminal coupled to a first reference voltage source; a second current source coupled to the second port; and A second comparator comprising: a non-inverting input terminal coupled to the second port; and an inverting input terminal coupled to a second reference voltage source; a third current source coupled to the third port; A third comparator comprising: a non-inverting input terminal coupled to the third port; and an inverting input terminal coupled to a third reference voltage source; a fourth current source coupled to the fourth port; a fourth comparator, comprising: a non-inverting input terminal coupled to the fourth port; and an inverting input terminal coupled to a fourth reference voltage source; wherein the first clock bus is coupled to a first pull-down resistor, and the first pull-down resistor is coupled to a ground node; wherein the second clock bus is coupled to a second pull-down resistor, and the second pull-down resistor is coupled to the ground node; wherein the first data bus is coupled to a third pull-down resistor, the third pull-down resistor is coupled to the ground node; and The second data bus is coupled to a fourth pull-down resistor, and the fourth pull-down resistor is coupled to the ground node.

11. The redriver circuit of claim 10, wherein: When the controller samples the impedance at the first port, the controller is configured to: causing the first current source to inject current into the first port; and monitoring an output of the first comparator; When the controller samples the impedance at the second port, the controller is configured to: causing the second current source to inject current into the second port; and monitoring an output terminal of the second comparator; When the controller samples the impedance at the third port, the controller is configured to: causing the third current source to inject current into the third port; and monitoring an output terminal of the third comparator; When the controller samples the impedance at the fourth port, the controller is configured to: causing the fourth current source to inject current into the fourth port; and monitoring an output terminal of the fourth comparator; asserting the output of the first comparator indicating a high impedance state at the first port, and in response, the controller is configured to disable the first communication channel; asserting the output of the second comparator indicating a high impedance state at the second port, and in response, the controller is configured to disable the second communication channel; asserting the output of the third comparator to indicate a high impedance state at the third port, and in response, the controller is configured to disable the third communication channel; and Asserting the output of the fourth comparator indicates a high impedance state at the fourth port, and in response, the controller is configured to disable the fourth communication channel.

12. The redriver circuit of claim 7, wherein the controller is further configured to: facilitating bus arbitration between the first device and the second device in response to detecting a bus arbitration start condition at the first port and the third port when the first communication channel and the third communication channel are enabled, or detecting the bus arbitration start condition at the second port and the fourth port when the second communication channel and the fourth communication channel are enabled; and In response to the bus arbitration being completed, the third communication channel and the fourth communication channel are disabled.

13. The redriver circuit of claim 12, wherein: The bus arbitration start condition detected at the first port and the third port includes asserting the input data signal received at the third port and deasserting the input clock signal received at the first port for at least a bus turnaround time; and The bus arbitration start condition detected at the second port and the fourth port includes asserting the input data signal received at the fourth port and deasserting the input clock signal received at the second port for at least the bus turnaround time.

14. A method for operating a redriver circuit, comprising: detecting a first signal edge at a first port configured to be coupled to a first device via a first bus; or detecting a first signal edge at a second port, the second port being configured to be coupled to a second device via a second bus; In response to detecting the first signal edge at the first port: enabling a first communication channel, the first communication channel being configured to transfer drive an input signal received from the first port to a second port as an output signal; and disabling a second communication channel, the second communication channel being configured to divert an input signal received from the second port to the first port as an output signal; In response to detecting the first signal edge at the second port: enabling the second communication channel; and disabling the first communication channel; sampling an impedance at the first port in response to deasserting the input signal received at the first port while the first communication channel is enabled; and An impedance at the second port is sampled in response to de-asserting the input signal received at the second port while the second communication channel is enabled.

15. The method according to claim 14, wherein: The first device is in a first voltage domain; the second device being in a second voltage domain; and The method further comprises: When the first communication channel is enabled, level-shifting the input signal received from the first port from the first voltage domain to the second voltage domain; and When the second communication channel is enabled, the input signal received from the second port is level-shifted from the second voltage domain to the first voltage domain.

16. The method of claim 14, wherein: a first current source coupled to the first port; A first comparator includes a non-inverting input terminal coupled to the first port, and an inverting input terminal coupled to a first reference voltage source; a second current source coupled to the second port; The second comparator comprises a non-inverting input terminal coupled to the second port and an inverting input terminal coupled to a second reference voltage source; The first bus is coupled to a first pull-down resistor, the first pull-down resistor being coupled to a ground node; and The second bus is coupled to a second pull-down resistor, which is coupled to the ground node.

17. The method of claim 16, wherein: Sampling the impedance at the first port further comprises: causing the first current source to inject current into the first port; and monitoring an output of the first comparator; Sampling the impedance at the second port further comprises: causing the second current source to inject current into the second port; and monitoring an output terminal of the second comparator; The method further comprises: disabling the first communication channel in response to asserting the output of the first comparator indicating a high impedance state at the first port; and The second communication channel is disabled in response to asserting the output of the second comparator indicating a high impedance state at the second port.

18. The method of claim 14, further comprising: facilitating bus arbitration between the first device and the second device in response to detecting a bus arbitration start condition at the first port when the first communication channel is enabled, or detecting the bus arbitration start condition at the second port when the second communication channel is enabled; and In response to the bus arbitration being completed, the first communication channel and the second communication channel are disabled.