US20230198801A1 - Multi-protocol bus circuit - Google Patents
Multi-protocol bus circuit Download PDFInfo
- Publication number
- US20230198801A1 US20230198801A1 US17/552,497 US202117552497A US2023198801A1 US 20230198801 A1 US20230198801 A1 US 20230198801A1 US 202117552497 A US202117552497 A US 202117552497A US 2023198801 A1 US2023198801 A1 US 2023198801A1
- Authority
- US
- United States
- Prior art keywords
- bus
- master
- slave
- protocol
- circuits
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000002457 bidirectional effect Effects 0.000 claims abstract description 28
- 238000006243 chemical reaction Methods 0.000 claims abstract description 18
- 238000004891 communication Methods 0.000 abstract description 30
- 238000010586 diagram Methods 0.000 description 6
- 238000010295 mobile communication Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000000758 substrate Substances 0.000 description 2
- 239000003990 capacitor Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4004—Coupling between buses
- G06F13/4027—Coupling between buses using bus bridges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/403—Bus networks with centralised control, e.g. polling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40006—Architecture of a communication node
- H04L12/40019—Details regarding a bus master
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4063—Device-to-bus coupling
- G06F13/4068—Electrical coupling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40006—Architecture of a communication node
- H04L12/40013—Details regarding a bus controller
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40052—High-speed IEEE 1394 serial bus
- H04L12/40084—Bus arbitration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F2213/0016—Inter-integrated circuit (I2C)
Definitions
- the technology of the disclosure relates generally to a hybrid bus apparatus incorporating heterogeneous communication buses.
- Mobile communication devices have become increasingly common in current society. The prevalence of these mobile communication devices is driven in part by the many functions that are now enabled on such devices. Increased processing capabilities in such devices means that mobile communication devices have evolved from being pure communication tools into sophisticated mobile multimedia centers that enable enhanced user experiences.
- a radio frequency (RF) signal(s) may first be modulated by a transceiver circuit(s) based on a selected modulation and coding scheme (MCS) and then amplified by a power amplifier(s) prior to being radiated from an antenna(s).
- MCS modulation and coding scheme
- the power amplifier(s) and the antenna(s) are typically located in an RF front-end (RFFE) circuit communicatively coupled to the transceiver circuit(s) via an RFFE bus based on an RFFE protocol as defined in the MIPI® alliance specification for radio frequency front-end control interface, version 2.1 (hereinafter referred to as “RFFE specification”).
- RFFE RF front-end
- FIG. 1 is a schematic diagram of an exemplary RFFE bus apparatus 10 as defined in the RFFE specification.
- the RFFE bus apparatus 10 includes an RFFE master 12 coupled to a number of RFFE slaves 14 ( 1 )- 14 (M) over an RFFE bus 16 .
- the RFFE bus 16 is a two-wire serial bus that includes a data line 18 and a clock line 20 for communicating a bidirectional data signal SDATA and a clock signal SCLK, respectively.
- the RFFE bus 16 operates at a first data rate.
- FIG. 2 is a schematic diagram of an exemplary conventional hybrid bus apparatus 22 in which a single-wire bus (SuBUS) bridge circuit 24 is configured to bridge communications between the RFFE master 12 in FIG. 1 with one or more SuBUS slaves 26 ( 1 )- 26 (N). Common elements between FIGS. 1 and 2 are shown therein with common element numbers and will not be re-described herein.
- SuBUS single-wire bus
- the SuBUS bridge circuit 24 is coupled to the SuBUS slaves 26 ( 1 )- 26 (N) over a SuBUS 28 having a single data wire 30 . Accordingly, the SuBUS 28 is configured to operate at a second data rate that can be faster or slower than the first data rate of the RFFE bus 16 .
- the SuBUS bridge circuit 24 may be coupled to the RFFE master 12 via the RFFE bus 16 .
- the SuBUS bridge circuit 24 and the SuBUS slaves 26 ( 1 )- 26 (N) are also RFFE slaves, such as the RFFE slaves 14 ( 1 )- 14 (M) coupled to the RFFE master 12 in the RFFE bus apparatus 10 of FIG. 1 .
- the SuBUS 28 differs from the RFFE bus 16 in several aspects.
- the RFFE bus 16 includes the data line 18 and the clock line 20
- the SuBUS 28 includes only the single data wire 30 .
- the SuBUS bridge circuit 24 is configured to communicate with the SuBUS slaves 26 ( 1 )- 26 (N) based on SuBUS command sequences, which may be compatible but different from the RFFE command sequences communicated over the RFFE bus 16 .
- the SuBUS bridge circuit 24 may perform command conversion between the RFFE command sequences and the SuBUS command sequences to facilitate communications between the RFFE bus 16 and the SuBUS 28 .
- the RFFE bus 16 may be configured to operate at the first data rate and the SuBUS 28 may be configured to operate at the second data rate, which is different from the first data rate.
- the SuBUS bridge circuit 24 may buffer SuBUS data payloads prior to communicating over the RFFE bus 16 to help compensate for a difference between the first data rate and the second data rate.
- the SuBUS slaves 26 ( 1 )- 26 (N) can also include other types of active or passive circuits (e.g., audio circuits) that need to communicate with other types of masters via the SuBUS 28 .
- the SuBUS bridge circuit 24 in the conventional hybrid bus apparatus 22 is only capable of bridging the SuBUS slaves 26 ( 1 )- 26 (N) with a single RFFE master 12 based exclusively on the RFFE protocol, it may be necessary to employ additional SuBUS bridge circuits to bridge the SuBUS slaves 26 ( 1 )- 26 (N) to additional types of masters.
- the conventional hybrid bus apparatus 22 may occupy a larger footprint and/or become more expensive.
- the multi-protocol bus circuit includes multiple master circuits each configured to communicate a respective master bus command(s) via a respective one of multiple master buses based on a respective one of multiple master bus protocols, and a slave circuit(s) configured to communicate a slave bus command(s) via a slave bus based on a slave bus protocol that is different from any of the master bus protocols.
- the multi-protocol bus circuit further includes a multi-protocol bridge circuit configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols.
- a multi-protocol bus circuit in one aspect, includes multiple master circuits each coupled to a respective on of multiple master buses.
- the multiple master circuits are each configured to communicate a respective one or more master bus commands based on a respective one of multiple master bus protocols.
- Each of the master bus protocols is different from at least another one of the master bus protocols.
- the multi-protocol bus circuit also includes one or more slave circuits each coupled to a slave bus.
- the slave circuits are each configured to communicate a respective one or more slave bus commands based on a slave bus protocol different from any of the master bus protocols.
- the multi-protocol bus circuit also includes a multi-protocol bridge circuit coupled to the master buses and the slave bus.
- the multi-protocol bridge circuit is configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols.
- a multi-protocol bridge circuit in another aspect, includes multiple master bus ports each coupled to a respective one of multiple master circuits configured to communicate a respective one or more master bus commands via a respective one of multiple master buses based on a respective one of multiple master bus protocols. Each of the master bus protocols is different from at least another one of the master bus protocols.
- the multi-protocol bridge circuit also includes a slave bus port coupled to one or more slave circuits. The slave circuits are each configured to communicate a respective one or more slave bus commands based on a slave bus protocol different from any of the master bus protocols.
- the multi-protocol bridge circuit also includes a control circuit. The control circuit is configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols.
- FIG. 1 is a schematic diagram of an exemplary radio frequency front-end (RFFE) bus apparatus as defined in the MlPI® alliance specification for radio frequency (RF) front-end control interface, version 2.1;
- RFFE radio frequency front-end
- FIG. 2 is a schematic diagram of an exemplary conventional hybrid bus apparatus in which a single-wire bus (SuBUS) bridge circuit is configured to bridge communications between an RFFE master in the RFFE bus apparatus of FIG. 1 with one or more SuBUS slaves; and
- SuBUS single-wire bus
- FIG. 3 is a schematic diagram of an exemplary multi-protocol hybrid bus apparatus configured according to embodiments of the present disclosure to support bidirectional bus communications between multiple master circuits and a slave circuit(s) based on heterogeneous bus protocols.
- the multi-protocol bus circuit includes multiple master circuits each configured to communicate a respective master bus command(s) via a respective one of multiple master buses based on a respective one of multiple master bus protocols, and a slave circuit(s) configured to communicate a slave bus command(s) via a slave bus based on a slave bus protocol that is different from any of the master bus protocols.
- the multi-protocol bus circuit further includes a multi-protocol bridge circuit configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols.
- FIG. 3 is a schematic diagram of an exemplary multi-protocol bus circuit 32 configured according to embodiments of the present disclosure to support bidirectional bus communications between multiple master circuits 34 ( 1 )- 34 (M) and one or more slave circuits 36 ( 1 )- 36 (N) based on heterogeneous bus protocols.
- the bidirectional bus communications refer to bus communications originated from any of the master circuits 34 ( 1 )- 34 (M) and destined to any of the slave circuits 36 ( 1 )- 36 (N) (a.k.a. forward communication), and bus communications originated from any of the slave circuits 36 ( 1 )- 36 (N) and destined to any of the master circuits 34 ( 1 )- 34 (M) (a.k.a. reverse communication).
- the master circuits 34 ( 1 )- 34 (M) are coupled to multiple master buses 38 ( 1 )- 38 (M), respectively.
- Each of the master circuits 34 ( 1 )- 34 (M) is configured to communicate a respective one or more master bus commands 40 ( 1 )- 40 (K) based on a respective one of multiple master bus protocols P M1 -P MM .
- all of the master bus protocols P M1 -P MM are different bus protocols.
- each of the master bus protocols P M1 -P MM is different from any other one of the master bus protocols P M1 -P MM .
- only a subset of the master bus protocols P M1 -P MM are different bus protocols.
- each of the master bus protocols P M1 -P MM is different from at least another one of the master bus protocols P M1 -P MM .
- the slave circuits 36 ( 1 )- 36 (N) are each coupled to a slave bus 42 and configured to communicate a respective one or more slave bus commands 44 ( 1 )- 44 (L) based on a slave bus protocol Ps that is different from any of the master bus protocols P M1 -P MM .
- the slave bus 42 is a single-wire bus (SuBUS) that is functionally equivalent to the SuBUS 28 in FIG. 2 . Accordingly, each of the slave circuits 36 ( 1 )- 36 (N) can be functionally equivalent to the SuBUS slaves 26 ( 1 )- 26 (N) in FIG. 2 .
- the multi-protocol bus circuit is further configured to include a multi-protocol bridge circuit 46 .
- the multi-protocol bridge circuit 46 includes multiple master ports 48 ( 1 )- 48 (M), each coupled to a respective one of the master buses 38 ( 1 )- 38 (M).
- the multi-protocol bridge circuit 46 also includes a slave bus port 50 coupled to the slave bus 42 .
- the multi-protocol bridge circuit 46 can be configured to perform a bidirectional conversion between the slave bus protocol Ps and each of the master bus protocols P M1 -P MM .
- the bidirectional conversion refers to converting the master bus commands 40 ( 1 )- 40 (K) from any of the master bus protocols P M1 -P MM into the slave bus commands 44 ( 1 )- 44 (L) in accordance with the slave bus protocol Ps, and vice versa.
- the multi-protocol bridge circuit 46 By bridging the master circuits 34 ( 1 )- 34 (M) with the slave circuits 36 ( 1 )- 36 (N) using the multi-protocol bridge circuit 46 , it is possible to support bidirectional bus communications based on heterogeneous bus protocols with minimal cost and/or footprint impact on the multi-protocol bus circuit 32 .
- the multi-protocol bridge circuit 46 includes a control circuit 52 , which can be a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), as an example.
- the control circuit 52 can be configured to receive the respective master bus commands 40 ( 1 )- 40 (K) from any of the master circuits 34 ( 1 )- 34 (M) via a respective one of the master ports 48 ( 1 )- 48 (M).
- the respective master bus commands 40 ( 1 )- 40 (K) may be destined to any of the slave circuits 36 ( 1 )- 36 (N) or to the multi-protocol bridge circuit 46 itself.
- control circuit 52 may be configured to first determine whether the respective master bus commands 40 ( 1 )- 40 (K) are destined to at least one of the slave circuits 36 ( 1 )- 36 (N). If the control circuit 52 determines that the respective master bus commands 40 ( 1 )- 40 (K) are indeed destined to any of the slave circuits 36 ( 1 )- 36 (N), the control circuit 52 will then convert the respective master bus commands 40 ( 1 )- 40 (K) into the respective slave bus commands 44 ( 1 )- 44 (L) and provide the respective slave bus commands 44 ( 1 )- 44 (L) to any of the slave circuits 36 ( 1 )- 36 (N) to which the respective master bus commands 40 ( 1 )- 40 (K) are destined.
- the control circuit 52 is configured to receive the respective slave bus commands 44 ( 1 )- 44 (L) from any of the one or more slave circuits 36 ( 1 )- 36 (N) via the slave bus port 50 .
- the respective slave bus commands 44 ( 1 )- 44 (L) may be destined to any of the master circuits 34 ( 1 )- 34 (M) or to the multi-protocol bridge circuit 46 itself.
- the control circuit 52 may be configured to first determine whether the respective slave bus commands 44 ( 1 )- 44 (L) are destined to at least one of the master circuits 34 ( 1 )- 34 (M).
- control circuit 52 determines that the respective slave bus commands 44 ( 1 )- 44 (L) are indeed destined to any of the master circuits 34 ( 1 )- 34 (M)
- the control circuit 52 will then convert the respective slave bus commands 44 ( 1 )- 44 (L) into the respective master bus commands 40 ( 1 )- 40 (M) and provide the respective master bus commands 40 ( 1 )- 40 (M) to any of the master circuits 34 ( 1 )- 34 (N) to which the respective slave bus commands 44 ( 1 )- 44 (L) are destined.
- control circuit 52 can include at least one encoder-decoder circuit 54 (denoted as “CODEC”).
- the encoder-decoder circuit 54 can be configured to convert the respective master bus commands 40 ( 1 )- 40 (M) into the respective slave bus commands 44 ( 1 )- 44 (L) in the forward communication, and to convert the respective slave bus commands 44 ( 1 )- 44 (L) into the respective master bus commands 40 ( 1 )- 40 (K) in the reverse communication.
- the multi-protocol bridge circuit 46 may simultaneously receive the respective master bus commands 40 ( 1 )- 40 (M) from more than one of the master circuits 34 ( 1 )- 34 (M).
- the control circuit 52 upon converting the respective master bus commands 40 ( 1 )- 40 (M) received from each of the master circuits 34 ( 1 )- 34 (M) into the respective slave bus commands 44 ( 1 )- 44 (L), the control circuit 52 needs to determine an order for providing the respective slave bus commands 44 ( 1 )- 44 (L) to some or all of the slave circuits 36 ( 1 )- 36 (N).
- control circuit 52 can provide the respective slave bus commands 44 ( 1 )- 44 (L), which are converted from the respective master bus commands 40 ( 1 )- 40 (M) received simultaneously from more than one of the master circuits 34 ( 1 )- 34 (M), to any of the slave circuits 36 ( 1 )- 36 (N) based on a predefined priority of the master circuits 34 ( 1 )- 34 (M).
- the respective slave bus commands 44 ( 1 )- 44 (L) converted from the respective master bus commands 40 ( 1 )- 40 (M) received from a higher priority one of the master circuits 34 ( 1 )- 34 (M) will be sent to the slave bus port 50 before the respective slave bus commands 44 ( 1 )- 44 (L) converted from the respective master bus commands 40 ( 1 )- 40 (M) are received from a lower priority one of the master circuits 34 ( 1 )- 34 (M).
- control circuit 52 can include a data buffer 56 that functions as a first-in first-out (FIFO) queue.
- the control circuit 52 may be configured to enqueue the respective slave bus commands 44 ( 1 )- 44 (L) based on the predefined priority of the master circuits 34 ( 1 )- 34 (M).
- control circuit 52 will enqueue the respective slave bus commands 44 ( 1 )- 44 (L) that are converted from the respective master bus commands 40 ( 1 )- 40 (M) received from the higher priority one of the master circuits 34 ( 1 )- 34 (M) in the data buffer 56 before enqueuing the respective slave bus commands 44 ( 1 )- 44 (L) that are converted from the respective master bus commands 40 ( 1 )- 40 (M) received from the lower priority one of the master circuits 34 ( 1 )- 34 (M).
- the data buffer 56 may be utilized only for the forward communication.
- the respective slave bus commands 44 ( 1 )- 44 (L) received from any of the slave circuits 36 ( 1 )- 36 (N) are directly routed to the encoder-decoder circuit 54 from the slave bus port 50 .
- the encoder-decoder circuit 54 is configured to convert the respective slave bus commands 44 ( 1 )- 44 (L) destined to any of the master circuits 34 ( 1 )- 34 (M) on a first come first serve basis.
- the multi-protocol bridge circuit 46 can include a storage circuit 58 (denoted as “REGMAP”), which can be a register bank, or a flash storage circuit, as an example.
- the storage circuit 58 may be programmed to store the predefined priority among the master circuits 34 ( 1 )- 34 (M).
- the respective master bus commands 40 ( 1 )- 40 (K) originated from any of the master circuits 34 ( 1 )- 34 (M) can be destined to the multi-protocol bridge circuit 46 , as opposed to any of the slave circuits 36 ( 1 )- 36 (N).
- the respective master bus commands 40 ( 1 )- 40 (K), which are originated from any of the master circuits 34 ( 1 )- 34 (M) and destined to the multi-protocol bridge circuit 46 may be utilized to program (dynamically or statically) the predefined priority in the storage circuit 58 .
- each of the master circuits 34 ( 1 )- 34 (M) may be configured to communicate the respective master bus commands 40 ( 1 )- 40 (K) by asserting a respective one of multiple master bus voltages V M1 -V MM on the respective one of the master buses 38 ( 1 )- 38 (M).
- each of the slave circuits 36 ( 1 )- 36 (N) is configured to communicate the respective slave bus commands 44 ( 1 )- 44 (L) based on a slave bus voltage Vs that is different from at least one of the master bus voltages V M1 -V MM .
- any mismatch between the master bus voltages V M1 -V MM and the slave bus voltage Vs can cause potential damage to the slave circuits 36 ( 1 )- 36 (N), particularly when the slave bus voltage Vs is lower than any mismatched master bus voltage among the master bus voltages V M1 -V MM .
- the multi-protocol bridge circuit 46 can be further configured to perform a bidirectional voltage conversion between the slave bus voltage Vs and any of the master bus voltages V M1 -V MM .
- the multi-protocol bridge circuit 46 can further include multiple master bus interface circuits 60 ( 1 )- 60 (M), each coupled to a respective one of the master ports 48 ( 1 )- 48 (M).
- each of the master bus interface circuits 60 ( 1 )- 60 (M) can include a respective voltage conversion circuit 62 , which can be a capacitor-based or an inductor-based buck-boost converter, or a level shifter, as an example, for carrying out the bidirectional voltage conversion between the slave bus voltage Vs and any of the master bus voltage V M1 -V MM .
- a respective voltage conversion circuit 62 can be a capacitor-based or an inductor-based buck-boost converter, or a level shifter, as an example, for carrying out the bidirectional voltage conversion between the slave bus voltage Vs and any of the master bus voltage V M1 -V MM .
- the multi-protocol bridge circuit 46 can include a radio-frequency front-end (RFFE) master circuit (e.g., the master circuit 34 ( 1 )) and an inter-integrated circuit (I2C) master circuit (e.g., the master circuit 34 (M)).
- RFFE radio-frequency front-end
- I2C inter-integrated circuit
- the RFFE master circuit 34 ( 1 ) is configured to communicate one or more RFFE bus commands 40 ( 1 )- 40 (K) over the RFFE bus 38 ( 1 ) based on an RFFE bus protocol and by asserting a respective one of the master bus voltage V M1 -V MM on the RFFE bus 38 ( 1 ), and the I2C master circuit 34 (M) is configured to communicate one or more I2C bus commands 40 ( 1 )- 40 (K) over the I2C bus 38 (M) based on a I2C bus protocol and by asserting a respective one of the master bus voltage V M1 -V MM on the I2C bus 38 (M).
- Each of the slave circuits 36 ( 1 )- 36 (N), on the other hand, is a SuBUS slave circuit configured to communicate the respective SuBUS slave bus commands 44 ( 1 )- 44 (N) over the SuBUS 42 based on the SuBUS protocol.
- the multi-protocol bridge circuit 46 is configured to perform the bidirectional conversion between the RFFE bus protocol, the I2C bus protocol, and the SuBUS bus protocol.
- the multi-protocol bridge circuit 46 may also perform the bidirectional voltage conversion should there be a mismatch between the RFFE master bus voltage V M1 , the I2C master bus voltage V MM , and the SuBUS slave bus voltage Vs.
- the multi-protocol bridge circuit 46 can further include a second RFFE master circuit (e.g., the master circuit 34 ( 2 )), which is configured to communicate a respective one or more RFFE bus commands 40 ( 1 )- 40 (K) over a respective one of the master buses (e.g., the master bus 38 ( 2 )) based on the RFFE bus protocol.
- the second RFFE master circuit is configured to assert a different master bus voltage from the respective master bus voltage asserted by the RFFE master circuit 38 ( 1 ).
Abstract
A multi-protocol bus circuit is provided. The multi-protocol bus circuit includes multiple master circuits each configured to communicate a respective master bus command(s) via a respective one of multiple master buses based on a respective one of multiple master bus protocols, and a slave circuit(s) configured to communicate a slave bus command(s) via a slave bus based on a slave bus protocol that is different from any of the master bus protocols. To enable bidirectional bus communications between the master circuits and the slave circuit(s), the multi-protocol bus circuit further includes a multi-protocol bridge circuit configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols. As a result, it is possible to support bidirectional bus communications based on heterogeneous bus protocols with minimal impact on cost and/or footprint.
Description
- The technology of the disclosure relates generally to a hybrid bus apparatus incorporating heterogeneous communication buses.
- Mobile communication devices have become increasingly common in current society. The prevalence of these mobile communication devices is driven in part by the many functions that are now enabled on such devices. Increased processing capabilities in such devices means that mobile communication devices have evolved from being pure communication tools into sophisticated mobile multimedia centers that enable enhanced user experiences.
- The redefined user experience requires higher data rates offered by wireless communication technologies, such as Wi-Fi, long-term evolution (LTE), and fifth-generation new-radio (5G-NR). To achieve the higher data rates in a mobile communication device, a radio frequency (RF) signal(s) may first be modulated by a transceiver circuit(s) based on a selected modulation and coding scheme (MCS) and then amplified by a power amplifier(s) prior to being radiated from an antenna(s). In many wireless communication devices, the power amplifier(s) and the antenna(s) are typically located in an RF front-end (RFFE) circuit communicatively coupled to the transceiver circuit(s) via an RFFE bus based on an RFFE protocol as defined in the MIPI® alliance specification for radio frequency front-end control interface, version 2.1 (hereinafter referred to as “RFFE specification”).
- In this regard,
FIG. 1 is a schematic diagram of an exemplaryRFFE bus apparatus 10 as defined in the RFFE specification. TheRFFE bus apparatus 10 includes anRFFE master 12 coupled to a number of RFFE slaves 14(1)-14(M) over anRFFE bus 16. According to the RFFE specification, theRFFE bus 16 is a two-wire serial bus that includes adata line 18 and aclock line 20 for communicating a bidirectional data signal SDATA and a clock signal SCLK, respectively. The RFFEbus 16 operates at a first data rate. - However, not all communications require a two-wire serial bus like the RFFE
bus 16. In some cases, a single-wire serial bus may be sufficient or even desired for carrying out certain types of communications between circuits. In this regard,FIG. 2 is a schematic diagram of an exemplary conventionalhybrid bus apparatus 22 in which a single-wire bus (SuBUS) bridge circuit 24 is configured to bridge communications between the RFFEmaster 12 inFIG. 1 with one or more SuBUS slaves 26(1)-26(N). Common elements betweenFIGS. 1 and 2 are shown therein with common element numbers and will not be re-described herein. - The SuBUS bridge circuit 24 is coupled to the SuBUS slaves 26(1)-26(N) over a SuBUS 28 having a single data wire 30. Accordingly, the SuBUS 28 is configured to operate at a second data rate that can be faster or slower than the first data rate of the
RFFE bus 16. The SuBUS bridge circuit 24 may be coupled to theRFFE master 12 via theRFFE bus 16. In this regard, the SuBUS bridge circuit 24 and the SuBUS slaves 26(1)-26(N) are also RFFE slaves, such as the RFFE slaves 14(1)-14(M) coupled to the RFFEmaster 12 in the RFFEbus apparatus 10 ofFIG. 1 . - Notably, the SuBUS 28 differs from the
RFFE bus 16 in several aspects. First, the RFFEbus 16 includes thedata line 18 and theclock line 20, while the SuBUS 28 includes only the single data wire 30. Second, the SuBUS bridge circuit 24 is configured to communicate with the SuBUS slaves 26(1)-26(N) based on SuBUS command sequences, which may be compatible but different from the RFFE command sequences communicated over theRFFE bus 16. In this regard, the SuBUS bridge circuit 24 may perform command conversion between the RFFE command sequences and the SuBUS command sequences to facilitate communications between theRFFE bus 16 and the SuBUS 28. Third, the RFFEbus 16 may be configured to operate at the first data rate and the SuBUS 28 may be configured to operate at the second data rate, which is different from the first data rate. In this regard, the SuBUS bridge circuit 24 may buffer SuBUS data payloads prior to communicating over theRFFE bus 16 to help compensate for a difference between the first data rate and the second data rate. - Besides the power amplifier(s) and the antenna(s), the SuBUS slaves 26(1)-26(N) can also include other types of active or passive circuits (e.g., audio circuits) that need to communicate with other types of masters via the SuBUS 28. Given that the SuBUS bridge circuit 24 in the conventional
hybrid bus apparatus 22 is only capable of bridging the SuBUS slaves 26(1)-26(N) with asingle RFFE master 12 based exclusively on the RFFE protocol, it may be necessary to employ additional SuBUS bridge circuits to bridge the SuBUS slaves 26(1)-26(N) to additional types of masters. As a result, the conventionalhybrid bus apparatus 22 may occupy a larger footprint and/or become more expensive. - Aspects disclosed in the detailed description include a multi-protocol bus circuit. The multi-protocol bus circuit includes multiple master circuits each configured to communicate a respective master bus command(s) via a respective one of multiple master buses based on a respective one of multiple master bus protocols, and a slave circuit(s) configured to communicate a slave bus command(s) via a slave bus based on a slave bus protocol that is different from any of the master bus protocols. To enable bidirectional bus communications between the master circuits and the slave circuit(s), the multi-protocol bus circuit further includes a multi-protocol bridge circuit configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols. As a result, it is possible to support bidirectional bus communications based on heterogeneous bus protocols with minimal impact on cost and/or footprint.
- In one aspect, a multi-protocol bus circuit is provided. The multi-protocol bus circuit includes multiple master circuits each coupled to a respective on of multiple master buses. The multiple master circuits are each configured to communicate a respective one or more master bus commands based on a respective one of multiple master bus protocols. Each of the master bus protocols is different from at least another one of the master bus protocols. The multi-protocol bus circuit also includes one or more slave circuits each coupled to a slave bus. The slave circuits are each configured to communicate a respective one or more slave bus commands based on a slave bus protocol different from any of the master bus protocols. The multi-protocol bus circuit also includes a multi-protocol bridge circuit coupled to the master buses and the slave bus. The multi-protocol bridge circuit is configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols.
- In another aspect, a multi-protocol bridge circuit is provided. The multi-protocol bridge circuit includes multiple master bus ports each coupled to a respective one of multiple master circuits configured to communicate a respective one or more master bus commands via a respective one of multiple master buses based on a respective one of multiple master bus protocols. Each of the master bus protocols is different from at least another one of the master bus protocols. The multi-protocol bridge circuit also includes a slave bus port coupled to one or more slave circuits. The slave circuits are each configured to communicate a respective one or more slave bus commands based on a slave bus protocol different from any of the master bus protocols. The multi-protocol bridge circuit also includes a control circuit. The control circuit is configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols.
- Those skilled in the art will appreciate the scope of the disclosure and realize additional aspects thereof after reading the following detailed description in association with the accompanying drawings.
- The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.
-
FIG. 1 is a schematic diagram of an exemplary radio frequency front-end (RFFE) bus apparatus as defined in the MlPI® alliance specification for radio frequency (RF) front-end control interface, version 2.1; -
FIG. 2 is a schematic diagram of an exemplary conventional hybrid bus apparatus in which a single-wire bus (SuBUS) bridge circuit is configured to bridge communications between an RFFE master in the RFFE bus apparatus ofFIG. 1 with one or more SuBUS slaves; and -
FIG. 3 is a schematic diagram of an exemplary multi-protocol hybrid bus apparatus configured according to embodiments of the present disclosure to support bidirectional bus communications between multiple master circuits and a slave circuit(s) based on heterogeneous bus protocols. - The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
- It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present disclosure. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
- It will be understood that when an element such as a layer, region, or substrate is referred to as being “on” or extending “onto” another element, it can be directly on or extend directly onto the other element or intervening elements may also be present. In contrast, when an element is referred to as being “directly on” or extending “directly onto” another element, there are no intervening elements present. Likewise, it will be understood that when an element such as a layer, region, or substrate is referred to as being “over” or extending “over” another element, it can be directly over or extend directly over the other element or intervening elements may also be present. In contrast, when an element is referred to as being “directly over” or extending “directly over” another element, there are no intervening elements present. It will also be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected” or “directly coupled” to another element, there are no intervening elements present.
- Relative terms such as “below” or “above” or “upper” or “lower” or “horizontal” or “vertical” may be used herein to describe a relationship of one element, layer, or region to another element, layer, or region as illustrated in the Figures. It will be understood that these terms and those discussed above are intended to encompass different orientations of the device in addition to the orientation depicted in the Figures.
- The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including” when used herein specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
- Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
- Aspects disclosed in the detailed description include a multi-protocol bus circuit. The multi-protocol bus circuit includes multiple master circuits each configured to communicate a respective master bus command(s) via a respective one of multiple master buses based on a respective one of multiple master bus protocols, and a slave circuit(s) configured to communicate a slave bus command(s) via a slave bus based on a slave bus protocol that is different from any of the master bus protocols. To enable bidirectional bus communications between the master circuits and the slave circuit(s), the multi-protocol bus circuit further includes a multi-protocol bridge circuit configured to perform a bidirectional conversion between the slave bus protocol and each of the master bus protocols. As a result, it is possible to support bidirectional bus communications based on heterogeneous bus protocols with minimal impact on cost and/or footprint.
- In this regard,
FIG. 3 is a schematic diagram of an exemplarymulti-protocol bus circuit 32 configured according to embodiments of the present disclosure to support bidirectional bus communications between multiple master circuits 34(1)-34(M) and one or more slave circuits 36(1)-36(N) based on heterogeneous bus protocols. Herein, the bidirectional bus communications refer to bus communications originated from any of the master circuits 34(1)-34(M) and destined to any of the slave circuits 36(1)-36(N) (a.k.a. forward communication), and bus communications originated from any of the slave circuits 36(1)-36(N) and destined to any of the master circuits 34(1)-34(M) (a.k.a. reverse communication). - The master circuits 34(1)-34(M) are coupled to multiple master buses 38(1)-38(M), respectively. Each of the master circuits 34(1)-34(M) is configured to communicate a respective one or more master bus commands 40(1)-40(K) based on a respective one of multiple master bus protocols PM1-PMM. In some embodiments, all of the master bus protocols PM1-PMM are different bus protocols. In this regard, each of the master bus protocols PM1-PMM is different from any other one of the master bus protocols PM1-PMM. In some other embodiments, only a subset of the master bus protocols PM1-PMM are different bus protocols. In this regard, each of the master bus protocols PM1-PMM is different from at least another one of the master bus protocols PM1-PMM.
- The slave circuits 36(1)-36(N) are each coupled to a
slave bus 42 and configured to communicate a respective one or more slave bus commands 44(1)-44(L) based on a slave bus protocol Ps that is different from any of the master bus protocols PM1-PMM. In a non-limiting example, theslave bus 42 is a single-wire bus (SuBUS) that is functionally equivalent to theSuBUS 28 inFIG. 2 . Accordingly, each of the slave circuits 36(1)-36(N) can be functionally equivalent to the SuBUS slaves 26(1)-26(N) inFIG. 2 . - To enable the bidirectional bus communications based on the heterogeneous bus protocols, the multi-protocol bus circuit is further configured to include a
multi-protocol bridge circuit 46. In an embodiment, themulti-protocol bridge circuit 46 includes multiple master ports 48(1)-48(M), each coupled to a respective one of the master buses 38(1)-38(M). Themulti-protocol bridge circuit 46 also includes aslave bus port 50 coupled to theslave bus 42. As discussed in further detail below, themulti-protocol bridge circuit 46 can be configured to perform a bidirectional conversion between the slave bus protocol Ps and each of the master bus protocols PM1-PMM. Herein, the bidirectional conversion refers to converting the master bus commands 40(1)-40(K) from any of the master bus protocols PM1-PMM into the slave bus commands 44(1)-44(L) in accordance with the slave bus protocol Ps, and vice versa. By bridging the master circuits 34(1)-34(M) with the slave circuits 36(1)-36(N) using themulti-protocol bridge circuit 46, it is possible to support bidirectional bus communications based on heterogeneous bus protocols with minimal cost and/or footprint impact on themulti-protocol bus circuit 32. - In an embodiment, the
multi-protocol bridge circuit 46 includes acontrol circuit 52, which can be a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), as an example. To enable the forward communication, thecontrol circuit 52 can be configured to receive the respective master bus commands 40(1)-40(K) from any of the master circuits 34(1)-34(M) via a respective one of the master ports 48(1)-48(M). Notably, the respective master bus commands 40(1)-40(K) may be destined to any of the slave circuits 36(1)-36(N) or to themulti-protocol bridge circuit 46 itself. In this regard, thecontrol circuit 52 may be configured to first determine whether the respective master bus commands 40(1)-40(K) are destined to at least one of the slave circuits 36(1)-36(N). If thecontrol circuit 52 determines that the respective master bus commands 40(1)-40(K) are indeed destined to any of the slave circuits 36(1)-36(N), thecontrol circuit 52 will then convert the respective master bus commands 40(1)-40(K) into the respective slave bus commands 44(1)-44(L) and provide the respective slave bus commands 44(1)-44(L) to any of the slave circuits 36(1)-36(N) to which the respective master bus commands 40(1)-40(K) are destined. - To enable the reverse communication, the
control circuit 52 is configured to receive the respective slave bus commands 44(1)-44(L) from any of the one or more slave circuits 36(1)-36(N) via theslave bus port 50. Notably, the respective slave bus commands 44(1)-44(L) may be destined to any of the master circuits 34(1)-34(M) or to themulti-protocol bridge circuit 46 itself. In this regard, thecontrol circuit 52 may be configured to first determine whether the respective slave bus commands 44(1)-44(L) are destined to at least one of the master circuits 34(1)-34(M). If thecontrol circuit 52 determines that the respective slave bus commands 44(1)-44(L) are indeed destined to any of the master circuits 34(1)-34(M), thecontrol circuit 52 will then convert the respective slave bus commands 44(1)-44(L) into the respective master bus commands 40(1)-40(M) and provide the respective master bus commands 40(1)-40(M) to any of the master circuits 34(1)-34(N) to which the respective slave bus commands 44(1)-44(L) are destined. - In an embodiment, the
control circuit 52 can include at least one encoder-decoder circuit 54 (denoted as “CODEC”). Specifically, the encoder-decoder circuit 54 can be configured to convert the respective master bus commands 40(1)-40(M) into the respective slave bus commands 44(1)-44(L) in the forward communication, and to convert the respective slave bus commands 44(1)-44(L) into the respective master bus commands 40(1)-40(K) in the reverse communication. - In an embodiment, the
multi-protocol bridge circuit 46 may simultaneously receive the respective master bus commands 40(1)-40(M) from more than one of the master circuits 34(1)-34(M). In this regard, upon converting the respective master bus commands 40(1)-40(M) received from each of the master circuits 34(1)-34(M) into the respective slave bus commands 44(1)-44(L), thecontrol circuit 52 needs to determine an order for providing the respective slave bus commands 44(1)-44(L) to some or all of the slave circuits 36(1)-36(N). - For example, the
control circuit 52 can provide the respective slave bus commands 44(1)-44(L), which are converted from the respective master bus commands 40(1)-40(M) received simultaneously from more than one of the master circuits 34(1)-34(M), to any of the slave circuits 36(1)-36(N) based on a predefined priority of the master circuits 34(1)-34(M). In this regard, the respective slave bus commands 44(1)-44(L) converted from the respective master bus commands 40(1)-40(M) received from a higher priority one of the master circuits 34(1)-34(M) will be sent to theslave bus port 50 before the respective slave bus commands 44(1)-44(L) converted from the respective master bus commands 40(1)-40(M) are received from a lower priority one of the master circuits 34(1)-34(M). - In a non-limiting example, the
control circuit 52 can include adata buffer 56 that functions as a first-in first-out (FIFO) queue. In this regard, thecontrol circuit 52 may be configured to enqueue the respective slave bus commands 44(1)-44(L) based on the predefined priority of the master circuits 34(1)-34(M). In other words, thecontrol circuit 52 will enqueue the respective slave bus commands 44(1)-44(L) that are converted from the respective master bus commands 40(1)-40(M) received from the higher priority one of the master circuits 34(1)-34(M) in thedata buffer 56 before enqueuing the respective slave bus commands 44(1)-44(L) that are converted from the respective master bus commands 40(1)-40(M) received from the lower priority one of the master circuits 34(1)-34(M). - In an embodiment, the
data buffer 56 may be utilized only for the forward communication. As for the reverse communication, the respective slave bus commands 44(1)-44(L) received from any of the slave circuits 36(1)-36(N) are directly routed to the encoder-decoder circuit 54 from theslave bus port 50. Accordingly, the encoder-decoder circuit 54 is configured to convert the respective slave bus commands 44(1)-44(L) destined to any of the master circuits 34(1)-34(M) on a first come first serve basis. - In an embodiment, the
multi-protocol bridge circuit 46 can include a storage circuit 58 (denoted as “REGMAP”), which can be a register bank, or a flash storage circuit, as an example. Thestorage circuit 58 may be programmed to store the predefined priority among the master circuits 34(1)-34(M). - As previously mentioned, the respective master bus commands 40(1)-40(K) originated from any of the master circuits 34(1)-34(M) can be destined to the
multi-protocol bridge circuit 46, as opposed to any of the slave circuits 36(1)-36(N). In this regard, the respective master bus commands 40(1)-40(K), which are originated from any of the master circuits 34(1)-34(M) and destined to themulti-protocol bridge circuit 46, may be utilized to program (dynamically or statically) the predefined priority in thestorage circuit 58. - In an embodiment, each of the master circuits 34(1)-34(M) may be configured to communicate the respective master bus commands 40(1)-40(K) by asserting a respective one of multiple master bus voltages VM1-VMM on the respective one of the master buses 38(1)-38(M). In contrast, each of the slave circuits 36(1)-36(N) is configured to communicate the respective slave bus commands 44(1)-44(L) based on a slave bus voltage Vs that is different from at least one of the master bus voltages VM1-VMM. Notably, any mismatch between the master bus voltages VM1-VMM and the slave bus voltage Vs can cause potential damage to the slave circuits 36(1)-36(N), particularly when the slave bus voltage Vs is lower than any mismatched master bus voltage among the master bus voltages VM1-VMM.
- In this regard, the
multi-protocol bridge circuit 46 can be further configured to perform a bidirectional voltage conversion between the slave bus voltage Vs and any of the master bus voltages VM1-VMM. In a non-limiting example, themulti-protocol bridge circuit 46 can further include multiple master bus interface circuits 60(1)-60(M), each coupled to a respective one of the master ports 48(1)-48(M). More specifically, each of the master bus interface circuits 60(1)-60(M) can include a respectivevoltage conversion circuit 62, which can be a capacitor-based or an inductor-based buck-boost converter, or a level shifter, as an example, for carrying out the bidirectional voltage conversion between the slave bus voltage Vs and any of the master bus voltage VM1-VMM. - As a non-limiting example, the
multi-protocol bridge circuit 46 can include a radio-frequency front-end (RFFE) master circuit (e.g., the master circuit 34(1)) and an inter-integrated circuit (I2C) master circuit (e.g., the master circuit 34(M)). In this regard, the RFFE master circuit 34(1) is configured to communicate one or more RFFE bus commands 40(1)-40(K) over the RFFE bus 38(1) based on an RFFE bus protocol and by asserting a respective one of the master bus voltage VM1-VMM on the RFFE bus 38(1), and the I2C master circuit 34(M) is configured to communicate one or more I2C bus commands 40(1)-40(K) over the I2C bus 38(M) based on a I2C bus protocol and by asserting a respective one of the master bus voltage VM1-VMM on the I2C bus 38(M). Each of the slave circuits 36(1)-36(N), on the other hand, is a SuBUS slave circuit configured to communicate the respective SuBUS slave bus commands 44(1)-44(N) over theSuBUS 42 based on the SuBUS protocol. - Accordingly, the
multi-protocol bridge circuit 46 is configured to perform the bidirectional conversion between the RFFE bus protocol, the I2C bus protocol, and the SuBUS bus protocol. In addition, themulti-protocol bridge circuit 46 may also perform the bidirectional voltage conversion should there be a mismatch between the RFFE master bus voltage VM1, the I2C master bus voltage VMM, and the SuBUS slave bus voltage Vs. - The
multi-protocol bridge circuit 46 can further include a second RFFE master circuit (e.g., the master circuit 34(2)), which is configured to communicate a respective one or more RFFE bus commands 40(1)-40(K) over a respective one of the master buses (e.g., the master bus 38(2)) based on the RFFE bus protocol. However, the second RFFE master circuit is configured to assert a different master bus voltage from the respective master bus voltage asserted by the RFFE master circuit 38(1). - Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.
Claims (20)
1. A multi-protocol bus circuit comprising:
a plurality of master circuits each coupled to a respective one of a plurality of master buses and configured to communicate a respective one or more master bus commands based on a respective one of a plurality of master bus protocols, wherein each of the plurality of master bus protocols is different from at least another one of the plurality of master bus protocols;
one or more slave circuits each coupled to a slave bus and configured to communicate a respective one or more slave bus commands based on a slave bus protocol different from any of the plurality of master bus protocols; and
a multi-protocol bridge circuit coupled to the plurality of master buses and the slave bus and configured to perform a bidirectional conversion between the slave bus protocol and each of the plurality of master bus protocols.
2. The multi-protocol bus circuit of claim 1 , wherein:
the plurality of master circuits comprises:
a radio-frequency front-end (RFFE) master circuit coupled to an RFFE bus and configured to communicate one or more RFFE bus commands based on an RFFE bus protocol;
an inter-integrated circuit (I2C) master circuit coupled to a I2C bus and configured to communicate one or more I2C bus commands based on a I2C bus protocol;
the one or more slave circuits comprise one or more single-wire bus (SuBUS) slave circuits each coupled to an SuBUS and configured to communicate a respective one or more SuBUS commands based on an SuBUS protocol; and
the multi-protocol bridge circuit is coupled to the RFFE bus, the I2C bus, and the SuBUS and configured to perform the bidirectional conversion between the SuBUS protocol and each of the RFFE bus protocol and the I2C bus protocol.
3. The multi-protocol bus circuit of claim 1 , wherein the multi-protocol bridge circuit is further configured to:
receive the respective one or more master bus commands from the respective one of the plurality of master circuits via the respective one of the plurality of master buses;
determine that the respective one or more master bus commands are destined to at least one of the one or more slave circuits;
convert the respective one or more master bus commands into the respective one or more slave bus commands of the at least one of the one or more slave circuits; and
provide the respective one or more slave bus commands to the at least one of the one or more slave circuits.
4. The multi-protocol bus circuit of claim 3 , wherein the multi-protocol bridge circuit is further configured to:
receive the respective one or more slave bus commands from the at least one of the one or more slave circuits;
convert the respective one or more slave bus commands into the respective one or more master bus commands of the at least one of the plurality of master circuits; and
provide the respective one or more master bus commands to the at least one of the plurality of master circuits.
5. The multi-protocol bus circuit of claim 4 , wherein the multi-protocol bridge circuit comprises at least one encoder-decoder circuit configured to:
convert the respective one or more master bus commands into the respective one or more slave bus commands of the at least one of the one or more slave circuits; and
convert the respective one or more slave bus commands into the respective one or more master bus commands of the at least one of the plurality of master circuits.
6. The multi-protocol bus circuit of claim 1 , wherein the multi-protocol bridge circuit is further configured to:
receive concurrently the respective one or more master bus commands from each of the plurality of master circuits;
determine that the respective one or more master bus commands received from the each of the plurality of master circuits are destined to the at least one of the one or more slave circuits;
convert the respective one or more master bus commands received from the each of the plurality of master circuits into the respective one or more slave bus commands; and
provide the respective one or more slave bus commands to the at least one of the one or more slave circuits based on a predefined priority of the plurality of master circuits.
7. The multi-protocol bus circuit of claim 6 , further comprising a data buffer coupled to the slave bus, wherein the multi-protocol bridge circuit is further configured to enqueue the respective one or more slave bus commands destined to the at least one of the one or more slave circuits in the data buffer based on the predefined priority of the plurality of master circuits.
8. The multi-protocol bus circuit of claim 6 , wherein the multi-protocol bridge circuit further comprises a storage circuit configured to store the predefined priority of the plurality of master circuits.
9. The multi-protocol bus circuit of claim 8 , wherein the multi-protocol bridge circuit is further configured to:
receive the respective one or more master bus commands from a respective one of the plurality of master circuits via the respective one of the plurality of master buses;
determine that the respective one or more master bus commands are destined to the multi-protocol bridge circuit; and
update the predefined priority stored in the storage circuit based on the respective one or more master bus commands.
10. The multi-protocol bus circuit of claim 1 , wherein:
each of the plurality of master circuits is further configured to communicate the respective one or more master bus commands by asserting a respective one of a plurality of master bus voltages on the respective one of the plurality of master buses; and
the one or more slave circuits are each configured to communicate the respective one or more slave bus commands based on a slave bus voltage different from at least one of the plurality of master bus voltages.
11. The multi-protocol bus circuit of claim 10 , wherein the multi-protocol bridge circuit is further configured to:
determine that the slave bus voltage is different from the at least one of the plurality of master bus voltages; and
perform bidirectional voltage conversion between the slave bus voltage and the at least one of the plurality of master bus voltages.
12. The multi-protocol bus circuit of claim 11 , wherein the multi-protocol bridge circuit further comprises a plurality of master bus interface circuits each coupled to a respective one of the plurality of master circuits, and at least one of the plurality of master bus interface circuits is configured to perform the bidirectional voltage conversion between the slave bus voltage and the at least one of the plurality of master bus voltages.
13. The multi-protocol bus circuit of claim 11 , wherein at least two of the plurality of master circuits are each configured to communicate the respective one or more master bus commands based on an identical one of the plurality of master bus protocols and by asserting a different one of the plurality of master bus voltages on the respective one of the plurality of master buses.
14. A multi-protocol bridge circuit comprising:
a plurality of master bus ports each coupled to a respective one of a plurality of master circuits configured to communicate a respective one or more master bus commands via a respective one of a plurality of master buses based on a respective one of a plurality of master bus protocols, wherein each of the plurality of master bus protocols is different from at least another one of the plurality of master bus protocols;
a slave bus port coupled to one or more slave circuits each configured to communicate a respective one or more slave bus commands based on a slave bus protocol different from any of the plurality of master bus protocols; and
a control circuit configured to perform a bidirectional conversion between the slave bus protocol and each of the plurality of master bus protocols.
15. The multi-protocol bridge circuit of claim 14 , wherein the control circuit is further configured to:
receive the respective one or more master bus commands via the respective one of the plurality of master bus ports;
determine that the respective one or more master bus commands are destined to at least one of the one or more slave circuits;
convert the respective one or more master bus commands into the respective one or more slave bus commands; and
provide the respective one or more slave bus commands to the slave bus port.
16. The multi-protocol bridge circuit of claim 15 , wherein the control circuit is further configured to:
receive the respective one or more slave bus commands via the slave bus port;
convert the respective one or more slave bus commands into the respective one or more master bus commands; and
provide the respective one or more master bus commands to at least one of the plurality of master bus ports.
17. The multi-protocol bridge circuit of claim 16 , wherein the control circuit comprises at least one encoder-decoder circuit configured to:
convert the respective one or more master bus commands into the respective one or more slave bus commands; and
convert the respective one or more slave bus commands into the respective one or more master bus commands.
18. The multi-protocol bridge circuit of claim 14 , wherein the control circuit is further configured to:
receive concurrently the respective one or more master bus commands via each of the plurality of master bus ports;
determine that the respective one or more master bus commands are destined to at least one of the one or more slave circuits;
convert the respective one or more master bus commands received via the each of the plurality of master bus ports into the respective one or more slave bus commands; and
provide the respective one or more slave bus commands to the slave bus port based on a predefined priority of the plurality of master circuits.
19. The multi-protocol bridge circuit of claim 18 , wherein the control circuit further comprises a data buffer coupled to the slave bus port, wherein the control circuit is further configured to enqueue the respective one or more slave bus commands destined to the at least one of the one or more slave circuits in the data buffer based on the predefined priority of the plurality of master circuits.
20. The multi-protocol bridge circuit of claim 14 , wherein:
each of the plurality of master circuits is further configured to communicate the respective one or more master bus commands by asserting a respective one of a plurality of master bus voltages on the respective one of the plurality of master buses; and
the one or more slave circuits are each configured to communicate the respective one or more slave bus commands based on a slave bus voltage different from at least one of the plurality of master bus voltages.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/552,497 US11706048B1 (en) | 2021-12-16 | 2021-12-16 | Multi-protocol bus circuit |
EP22210008.3A EP4199436A1 (en) | 2021-12-16 | 2022-11-28 | Multi-protocol bus circuit |
KR1020220174835A KR20230091802A (en) | 2021-12-16 | 2022-12-14 | Multi-protocol bus circuit |
CN202211640959.2A CN116266166A (en) | 2021-12-16 | 2022-12-16 | Multi-protocol bus circuit |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/552,497 US11706048B1 (en) | 2021-12-16 | 2021-12-16 | Multi-protocol bus circuit |
Publications (2)
Publication Number | Publication Date |
---|---|
US20230198801A1 true US20230198801A1 (en) | 2023-06-22 |
US11706048B1 US11706048B1 (en) | 2023-07-18 |
Family
ID=84363706
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/552,497 Active 2041-12-22 US11706048B1 (en) | 2021-12-16 | 2021-12-16 | Multi-protocol bus circuit |
Country Status (4)
Country | Link |
---|---|
US (1) | US11706048B1 (en) |
EP (1) | EP4199436A1 (en) |
KR (1) | KR20230091802A (en) |
CN (1) | CN116266166A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210218595A1 (en) * | 2020-01-13 | 2021-07-15 | Maxim Integrated Products, Inc. | System and method for dual-port communication and power delivery |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9152598B2 (en) * | 2012-11-28 | 2015-10-06 | Atmel Corporation | Connecting multiple slave devices to a single master controller in bus system |
Family Cites Families (108)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3555196A (en) | 1967-09-21 | 1971-01-12 | Northern Electric Co | Telephone switching system with programmed auxiliary control for providing special services |
US3953835A (en) | 1974-01-18 | 1976-04-27 | Honeywell Information Systems, Inc. | Method and apparatus for adapting a data processing port to receive and transmit different frequency signals |
US4336447A (en) | 1977-11-14 | 1982-06-22 | Osaka Gas Co., Ltd. | Converter of meter-gauge readings |
US4424812A (en) | 1980-10-09 | 1984-01-10 | Cordis Corporation | Implantable externally programmable microprocessor-controlled tissue stimulator |
US4497068A (en) | 1982-01-25 | 1985-01-29 | Eaton Corporation | Encoding system for optic data link |
US4736367A (en) | 1986-12-22 | 1988-04-05 | Chrysler Motors Corporation | Smart control and sensor devices single wire bus multiplex system |
KR100201580B1 (en) | 1991-04-02 | 1999-06-15 | 후루까와 준노스께 | Miltiplex transmission system |
DE4230913C2 (en) | 1992-09-16 | 1994-09-15 | Itt Ind Gmbh Deutsche | Method and circuit arrangement for a serial bus system with a single-wire connection |
US5748675A (en) | 1992-09-28 | 1998-05-05 | Chrysler Corporation | Vehicle communications network with improved current sourcing |
US5586266A (en) | 1993-10-15 | 1996-12-17 | International Business Machines Corporation | System and method for adaptive, active monitoring of a serial data stream having a characteristic pattern |
US5459660A (en) | 1993-12-22 | 1995-10-17 | Chrysler Corporation | Circuit and method for interfacing with vehicle computer |
EP0663637A1 (en) | 1994-01-12 | 1995-07-19 | T.R.T. Telecommunications Radioelectriques Et Telephoniques | Communication medium for electronic system with several distributed processors |
JPH0898284A (en) | 1994-07-25 | 1996-04-12 | Nippondenso Co Ltd | Data receiver, data transmitter and data communication equipment |
US5495469A (en) | 1994-12-16 | 1996-02-27 | Chrysler Corporation | Communications network, state machine therefor |
US5621897A (en) | 1995-04-13 | 1997-04-15 | International Business Machines Corporation | Method and apparatus for arbitrating for a bus to enable split transaction bus protocols |
US5978860A (en) | 1995-06-07 | 1999-11-02 | Dell Usa, L.P. | System and method for disabling and re-enabling at least one peripheral device in a computer system by masking a device-configuration-space-access-signal with a disable or re-enable signal |
US5734847A (en) | 1995-06-15 | 1998-03-31 | Intel Corporation | Method and apparatus for enabling intelligent I/O subsystems using PCI I/O devices |
AU6502896A (en) | 1995-07-20 | 1997-02-18 | Dallas Semiconductor Corporation | Single chip microprocessor, math co-processor, random number generator, real-time clock and ram having a one-wire interface |
US5774680A (en) | 1995-12-11 | 1998-06-30 | Compaq Computer Corporation | Interfacing direct memory access devices to a non-ISA bus |
US6141708A (en) | 1998-06-15 | 2000-10-31 | Compaq Computer Corporation | Host bridge configured to mask a portion of peripheral devices coupled to a bus further downstream of the host bridge from a host processor |
US6247138B1 (en) | 1997-06-12 | 2001-06-12 | Fujitsu Limited | Timing signal generating circuit, semiconductor integrated circuit device and semiconductor integrated circuit system to which the timing signal generating circuit is applied, and signal transmission system |
DE19733866C2 (en) | 1997-08-05 | 2002-09-12 | Siemens Ag | System for the transmission of data in a motor vehicle |
US6189063B1 (en) | 1997-09-30 | 2001-02-13 | Texas Instruments Incorporated | Method and apparatus for intelligent configuration register access on a PCI to PCI bridge |
US6292705B1 (en) | 1998-09-29 | 2001-09-18 | Conexant Systems, Inc. | Method and apparatus for address transfers, system serialization, and centralized cache and transaction control, in a symetric multiprocessor system |
GB9727452D0 (en) | 1997-12-31 | 1998-02-25 | Northern Telecom Ltd | Method and apparatus for replicating operations on data |
US6397279B1 (en) | 1998-01-07 | 2002-05-28 | Vlsi Technology, Inc. | Smart retry system that reduces wasted bus transactions associated with master retries |
US6094699A (en) | 1998-02-13 | 2000-07-25 | Mylex Corporation | Apparatus and method for coupling devices to a PCI-to-PCI bridge in an intelligent I/O controller |
US6308255B1 (en) | 1998-05-26 | 2001-10-23 | Advanced Micro Devices, Inc. | Symmetrical multiprocessing bus and chipset used for coprocessor support allowing non-native code to run in a system |
US6360291B1 (en) | 1999-02-01 | 2002-03-19 | Compaq Computer Corporation | System and method for hiding peripheral devices in a computer system |
US7197589B1 (en) | 1999-05-21 | 2007-03-27 | Silicon Graphics, Inc. | System and method for providing access to a bus |
US6775707B1 (en) | 1999-10-15 | 2004-08-10 | Fisher-Rosemount Systems, Inc. | Deferred acknowledgment communications and alarm management |
US20010050713A1 (en) | 2000-01-28 | 2001-12-13 | Naoki Kubo | Device and method for generating timing signals of different kinds |
US6985990B2 (en) | 2002-03-29 | 2006-01-10 | International Business Machines Corporation | System and method for implementing private devices on a secondary peripheral component interface |
US7519005B2 (en) | 2002-05-08 | 2009-04-14 | Semtech Corp. | Single-wire communication bus for miniature low-power systems |
US20050185665A1 (en) | 2002-07-18 | 2005-08-25 | Andrea Uboldi | Management method for a bidirectional and simultaneous exchange of digital signals and a corresponding interface for a bidirectional and simultaneous communication |
TWI236264B (en) | 2002-09-05 | 2005-07-11 | Winbond Electronics Corp | Single wire serial communication protocol method and circuit |
US6744395B1 (en) | 2002-11-27 | 2004-06-01 | International Business Machines Corporation | Power-scalable asynchronous architecture for a wave-pipelined analog to digital converter |
US7075822B2 (en) | 2002-12-31 | 2006-07-11 | Intel Corporation | High bandwidth datapath load and test of multi-level memory cells |
US7685320B1 (en) | 2003-04-11 | 2010-03-23 | Zilker Labs, Inc. | Autonomous sequencing and fault spreading |
US6948023B2 (en) | 2003-05-02 | 2005-09-20 | Atop Technologies, Inc. | Transmission interface conversion device |
US7109694B2 (en) | 2003-07-14 | 2006-09-19 | International Rectifier Corporation | Digital multiphase control system |
DE10335905B4 (en) | 2003-08-06 | 2018-07-05 | Robert Bosch Gmbh | Method and device for bidirectional single-wire data transmission |
DE10335904B4 (en) | 2003-08-06 | 2018-12-13 | Robert Bosch Gmbh | Method and device for bidirectional single-wire data transmission |
US7729427B2 (en) | 2004-02-24 | 2010-06-01 | Intersil Americas Inc. | Pseudo-synchronous one wire bidirectional bus interface |
KR100641706B1 (en) | 2004-11-03 | 2006-11-03 | 주식회사 하이닉스반도체 | On-chip self test circuit and self test method of signal distortion |
US20060031618A1 (en) | 2004-05-20 | 2006-02-09 | Hansquine David W | Single wire and three wire bus interoperability |
US20050259609A1 (en) | 2004-05-20 | 2005-11-24 | Hansquine David W | Single wire bus interface |
US7260661B2 (en) | 2004-09-03 | 2007-08-21 | Intel Corporation | Processing replies to request packets in an advanced switching context |
EP1815056B1 (en) | 2004-11-10 | 2010-02-24 | Koninklijke Philips Electronics N.V. | Method of an device for performing bi-directional transmission using a single-wire |
US7373444B2 (en) | 2005-04-15 | 2008-05-13 | Kabushiki Kaisha Toshiba | Systems and methods for manipulating entries in a command buffer using tag information |
US7752365B2 (en) | 2008-04-01 | 2010-07-06 | Kyocera Corporation | Bi-directional single conductor interrupt line for communication bus |
KR101007046B1 (en) | 2008-04-23 | 2011-01-12 | 주식회사 애트랩 | Communication system which can be restored at the time of malfunction automatically and reconstruction method thereof |
FR2934390B1 (en) | 2008-07-22 | 2010-08-13 | St Microelectronics Rousset | MULTICANAL TRANSMISSION ON A UNIFIL BUS |
JP5332905B2 (en) | 2009-05-26 | 2013-11-06 | 富士通セミコンダクター株式会社 | Bus control system and semiconductor integrated circuit |
JP4788804B2 (en) | 2009-06-01 | 2011-10-05 | 株式会社デンソー | Electronic control unit |
US8489786B2 (en) | 2009-11-09 | 2013-07-16 | Stmicroelectronics International N.V. | Acknowledgement management technique for supported command set of SMBUS/PMBUS slave applications |
FR2963449B1 (en) | 2010-07-27 | 2013-01-25 | St Microelectronics Rousset | CONVERSION OF A BIFILAR BUS IN A UNIFIL BUS |
FR2963451B1 (en) | 2010-07-27 | 2012-12-07 | St Microelectronics Rousset | AUTHENTICATION OF MULTIPROTOCOL COMMUNICATION |
FR2963519B1 (en) | 2010-07-27 | 2012-08-03 | St Microelectronics Rousset | COMMUNICATION PROTOCOL ON A UNIFIL BUS |
US8887022B2 (en) | 2011-03-04 | 2014-11-11 | Infineon Technologies Austria Ag | Reliable data transmission with reduced bit error rate |
US20120303836A1 (en) | 2011-05-23 | 2012-11-29 | Rf Micro Devices, Inc. | Slave id configuration |
US8832331B2 (en) | 2011-08-29 | 2014-09-09 | Ati Technologies Ulc | Data modification for device communication channel packets |
WO2013052886A2 (en) | 2011-10-05 | 2013-04-11 | Analog Devices, Inc. | Two-wire communication system for high-speed data and power distribution |
US9274999B2 (en) | 2011-11-22 | 2016-03-01 | Pixart Imaging Inc. | Communication system and optical navigation device |
US8693317B2 (en) | 2011-11-22 | 2014-04-08 | Tyco Fire & Security Gmbh | System and method for backup communication using power over ethernet |
GB2499699A (en) | 2011-12-14 | 2013-08-28 | Wolfson Ltd | Digital data transmission involving the position of and duration of data pulses within transfer periods |
KR101720134B1 (en) | 2011-12-21 | 2017-03-28 | 한국전자통신연구원 | Bus bridge apparatus |
US8964698B2 (en) | 2012-04-09 | 2015-02-24 | Telefonaktiebolaget L M Ericsson (Publ) | Link failure detection and interworking system relocation in circuit switched fallback |
CN103365259B (en) | 2012-04-10 | 2016-09-28 | 泰科电子(上海)有限公司 | Control circuit module, electrical equipment and modulation-demodulation device |
US8787990B2 (en) | 2012-05-09 | 2014-07-22 | Blackberry Limited | System and method for controlling electromagnetic interference in portable electronic devices having a radio frequency subsystem |
CN104541473B (en) | 2012-06-01 | 2017-09-12 | 黑莓有限公司 | Being used for based on probabilistic method ensures the generic sync engine of the locking in multi-format audio system |
DE112013005093T5 (en) | 2012-10-22 | 2015-10-22 | Intel Corporation | Hochleistungszusammenschaltungsbitübertragungsschicht |
US9465421B2 (en) | 2013-03-15 | 2016-10-11 | Broadcom Corporation | Partitioned switch mode power supply (SMPS) interface |
US9519612B2 (en) | 2013-04-04 | 2016-12-13 | Qorvo Us, Inc. | Serial bus buffer with noise reduction |
US9569386B2 (en) | 2013-04-16 | 2017-02-14 | Nxp B.V. | Method and system for single-line inter-integrated circuit (I2C) bus |
US9780645B2 (en) | 2013-06-25 | 2017-10-03 | Enphase Energy, Inc. | Method and apparatus for providing power conversion using an interleaved flyback converter with reactive power control |
US9276623B2 (en) | 2013-08-20 | 2016-03-01 | Aviacomm Inc. | Cost effective multiband RF front-end architecture for mobile applications |
US9690725B2 (en) | 2014-01-14 | 2017-06-27 | Qualcomm Incorporated | Camera control interface extension with in-band interrupt |
US10108578B2 (en) | 2013-09-11 | 2018-10-23 | Texas Instruments Incorporated | Single wire communications interface and protocol |
US9720872B2 (en) | 2013-10-10 | 2017-08-01 | Qorvo Us, Inc. | Auto-configuration of devices based upon configuration of serial input pins and supply |
US9495318B2 (en) | 2013-11-25 | 2016-11-15 | Apple Inc. | Synchronizing transactions for a single master over multiple busses |
US10282269B2 (en) | 2013-12-18 | 2019-05-07 | Qorvo Us, Inc. | Read technique for a bus interface system |
US10185683B2 (en) | 2013-12-18 | 2019-01-22 | Qorvo Us, Inc. | Bus interface system |
US10579580B2 (en) | 2013-12-18 | 2020-03-03 | Qorvo Us, Inc. | Start of sequence detection for one wire bus |
US10049026B2 (en) | 2013-12-18 | 2018-08-14 | Qorvo Us, Inc. | Group write technique for a bus interface system |
US10528502B2 (en) | 2013-12-18 | 2020-01-07 | Qorvo Us, Inc. | Power management system for a bus interface system |
US10540226B2 (en) | 2013-12-18 | 2020-01-21 | Qorvo Us, Inc. | Write technique for a bus interface system |
US9652451B2 (en) | 2014-05-08 | 2017-05-16 | Marvin Elder | Natural language query |
US9430321B2 (en) | 2014-05-13 | 2016-08-30 | Netapp, Inc. | Reconstructing data stored across archival data storage devices |
US9166584B1 (en) | 2014-06-09 | 2015-10-20 | Xilinx, Inc. | Current-encoded signaling |
US20160050513A1 (en) | 2014-08-15 | 2016-02-18 | Aviacomm Inc. | Rf front-end architecture for machine-to-machine applications |
US9785605B2 (en) | 2014-11-05 | 2017-10-10 | Qualcomm Incorporated | Predefined static enumeration for dynamic enumeration buses |
US9946677B2 (en) | 2015-02-12 | 2018-04-17 | Atmel Corporation | Managing single-wire communications |
US9755821B2 (en) | 2015-04-02 | 2017-09-05 | Samsung Electronics Co., Ltd. | Device including single wire interface and data processing system including the same |
US20170104607A1 (en) * | 2015-10-13 | 2017-04-13 | Qualcomm Incorporated | Methods to avoid i2c void message in i3c |
US10579128B2 (en) | 2016-03-01 | 2020-03-03 | Qorvo Us, Inc. | Switching power supply for subus slaves |
US10698847B2 (en) | 2016-03-01 | 2020-06-30 | Qorvo Us, Inc. | One wire bus to RFFE translation system |
US10437772B2 (en) | 2016-03-24 | 2019-10-08 | Qorvo Us, Inc. | Addressing of slave devices on a single wire communications bus through register map address selection |
US10176130B2 (en) | 2016-03-30 | 2019-01-08 | Qorvo Us, Inc. | Slave device identification on a single wire communications bus |
US10558607B2 (en) | 2017-02-01 | 2020-02-11 | Qorvo Us, Inc. | Bus interface system for power extraction |
US20190250876A1 (en) | 2018-02-13 | 2019-08-15 | Qualcomm Incorporated | Split read transactions over an audio communication bus |
US11614947B2 (en) | 2018-02-23 | 2023-03-28 | Untether Ai Corporation | Computational memory |
US11119966B2 (en) * | 2018-09-07 | 2021-09-14 | Qualcomm Incorporated | Mixed-mode radio frequency front-end interface |
US11176075B2 (en) | 2018-11-08 | 2021-11-16 | Qorvo Us, Inc. | Hybrid bus hub circuit and related apparatus |
US10599601B1 (en) | 2019-01-16 | 2020-03-24 | Qorvo Us, Inc. | Single-wire bus (SuBUS) slave circuit and related apparatus |
US11119958B2 (en) | 2019-04-18 | 2021-09-14 | Qorvo Us, Inc. | Hybrid bus apparatus |
US20200344094A1 (en) * | 2019-04-23 | 2020-10-29 | Qualcomm Incorporated | Digital data and power transmission over single-wire bus |
US10983942B1 (en) | 2019-12-11 | 2021-04-20 | Qorvo Us, Inc. | Multi-master hybrid bus apparatus |
-
2021
- 2021-12-16 US US17/552,497 patent/US11706048B1/en active Active
-
2022
- 2022-11-28 EP EP22210008.3A patent/EP4199436A1/en active Pending
- 2022-12-14 KR KR1020220174835A patent/KR20230091802A/en unknown
- 2022-12-16 CN CN202211640959.2A patent/CN116266166A/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9152598B2 (en) * | 2012-11-28 | 2015-10-06 | Atmel Corporation | Connecting multiple slave devices to a single master controller in bus system |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210218595A1 (en) * | 2020-01-13 | 2021-07-15 | Maxim Integrated Products, Inc. | System and method for dual-port communication and power delivery |
Also Published As
Publication number | Publication date |
---|---|
KR20230091802A (en) | 2023-06-23 |
US11706048B1 (en) | 2023-07-18 |
CN116266166A (en) | 2023-06-20 |
EP4199436A1 (en) | 2023-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11176075B2 (en) | Hybrid bus hub circuit and related apparatus | |
US10983942B1 (en) | Multi-master hybrid bus apparatus | |
US11424779B2 (en) | Heterogeneous bus bridge circuit and related apparatus | |
US10356504B2 (en) | Low latency transmission systems and methods for long distances in soundwire systems | |
EP2540135B1 (en) | Scalable digrf architecture | |
US11349468B2 (en) | Target voltage circuit for fast voltage switching | |
CN104426576A (en) | Cost effective multiband rf front-end architecture for mobile applications | |
US11119958B2 (en) | Hybrid bus apparatus | |
US10417161B2 (en) | Efficient technique for communicating between devices over a multi-drop bus | |
EP4199436A1 (en) | Multi-protocol bus circuit | |
CN102760110A (en) | Multiple subscriber identity module controller | |
JP6650413B2 (en) | System and method for multiple network access by a mobile computing device | |
CN107534616B (en) | Quality of service for universal serial bus | |
US11113220B2 (en) | Single-wire peer-to-peer bus | |
US20180074985A1 (en) | Radio frequency front end (rffe) command code extension with uniform sequence start condition (ssc) | |
KR20230092908A (en) | Tunneling through Universal Serial Bus (USB) sideband channels | |
WO2021145922A1 (en) | Multi-mode antenna tuner circuit and related apparatus | |
US20230315662A1 (en) | Hybrid bus communication circuit | |
US20130222035A1 (en) | Level-shifting interface for a processor-based device | |
US11409677B2 (en) | Bus slave circuit and related single-wire bus apparatus | |
EP2816791A1 (en) | Multi-path speech signal multiplexing circuit, equipment and method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: QORVO US, INC., NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NGO, CHRISTOPHER TRUONG;KHLAT, NADIM;HIETALA, ALEXANDER WAYNE;SIGNING DATES FROM 20211213 TO 20211216;REEL/FRAME:058404/0527 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |