The present invention relates to a data processing system, and more particularly, a method and apparatus for interconnecting portions of circuitry within a data processing system.
As data processing systems become more and more complex, the method and apparatus for interconnecting portions of circuitry within the data processing system become more important. If the interconnection topology and protocols are not designed properly, bottlenecks can occur at the interconnection interfaces. Performance of the data processing system can be degraded due to these bottlenecks. It is also important that the interconnect scheme in a data processing system be configurable so that a specific hardware configuration can be used to support a variety of functional configurations.
The present invention is illustrated by way of example and not limited by the accompanying figures, in which like references indicate similar elements, and in which:
Skilled artisans appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help improve the understanding of the embodiments of the present invention.
As used herein, the term “bus” is used to refer to a plurality of signals or conductors which may be used to transfer one or more various types of information, such as data, addresses, control, or status. The terms “assert” and “negate” is used when referring to the rendering of a signal, status bit, or similar apparatus into its logically true or logically false state, respectively. If the logically true state is a logic level one, the logically false state is a logic level zero. And if the logically true state is a logic level zero, the logically false state is a logic level one.
Brackets are used to indicate the conductors of a bus or the bit locations of a value. For example, “bus 60 [0–7]” or “conductors [0–7] of bus 60” indicates the eight lower order conductors of bus 60, and “address bits [0–7]” or “ADDRESS [0–7]” indicates the eight lower order bits of an address value.
Circuit portion 12 may include one or more signals 154 which may be used to communicate external to circuit portion 12. For example, signals 154 may be used to write, and thus configure, configuration register 21. Circuit portion 14 may include one or more signals 151 which may be used to communicate external to circuit portion 14. For example, signals 151 may be used to write, and thus configure, configuration register 22. Circuit portion 16 may include one or more signals 152 which may be used to communicate external to circuit portion 16. For example, signals 152 may be used to write, and thus configure, configuration register 23. Circuit portion 18 may include one or more signals 153 which may be used to communicate external to circuit portion 18. For example, signals 153 may be used to write, and thus configure, configuration register 24.
In one embodiment of the present invention, interface 30 includes signals slave_enable 40, data 41, transfer_request 42, address [28:0] 44, address [29] 45, address [30] 46, address [31] 47, and data_valid 120. Interface 31 includes signals slave_enable 48, data 49, transfer_request 50, address [31:0] 52, and data_valid 121. Interface 32 includes signals slave_enable 53, data 54, transfer_request 55, address [31:0] 57, and data_valid 122. Interface 33 includes signals slave_enable 58, data 59, transfer_request 60, address [31:0] 62, and data_valid 123.
In one embodiment of the present invention, interface 34 includes signals transfer_request 200, slave_enable 70, data 71, and data_valid 72; interface 35 includes signals transfer_request 201, slave_enable 73, data 744, and data_valid 75; interface 36 includes signals transfer_request 202, slave_enable 76, data 77, and data_valid 78; and interface 37 includes signals transfer_request 203, address [15] 79, address [13] 80, address [8] 81, address [14, 12–9, 7–0] 82, data 83, and data_valid 84.
Note that data processing system 10 may be implemented using any desired circuitry. As possible examples, data processing system 10 may be implemented using one or more integrated circuits, or one or more circuit boards. An interface (e.g. 30–37 and 134) may be implemented on the same integrated circuit as its corresponding circuit portion (e.g. 12, 14, 16, 18, 14, 16, 18, 20, and 20, respectively), or alternately, may be implemented on a different integrated circuit. One possible use for a data processing system 10 as illustrated in
Note that external address generation circuitry 140 and internal address generation circuitry 142 correspond to and are used with interface 37. Interface 134 also has a corresponding external address generation circuitry 148 and a corresponding internal address generation circuitry 146. Note that control circuitry 152 is bi-directionally coupled to external address generation circuitry 140, internal address generation circuitry 142, storage and/or control processing circuitry 144, external address generation circuitry 148, and internal address generation circuitry 146 to receive and provide status and control information. Control circuitry 152 receives request 203 by way of interface 37, and provides request 204 by way of interface 134. In one embodiment of the present invention, interface 134 includes signals transfer_request 204, slave_enable 130, data 133, address [15:0] 132, and data_valid 131. Alternate embodiments of the present invention may implement circuit portion 20 in any appropriate manner. The block diagram illustrated in
Operation of data processing system 10 will now be described. Note that in one embodiment of the present invention, a same master/slave interface structure and protocol may be used to communicate among all of the circuit portions 12, 14, 16, 18, and 20. For example, interface 30 of circuit portion 12 may be configured as the master and may provide data to any number of slave interfaces (e.g. 31–33). Optionally, each circuit portion (14, 16, and 18) may then have a second interface which can be independently configured as a master or slave. In the illustrated embodiment, circuit portions 14, 16, and 18 each have a second interface 34–36, respectively, which functions as a slave to provide data to circuit portion 20 by way of interface 37. Note that interface 37 in this configuration is a master interface. In one embodiment of the present invention, the same master/slave interface structure and protocol may be used to communicate in one direction at a time between a single master interface and one or more slave interfaces. Note that for some embodiments of the present invention, software and/or hardware reconfiguration may be required if the direction of data flow is to be changed.
Note that the data processing system 10 of
Note that a circuit portion may have any number of master/slave interface structures, and thus may function as a slave for a first master/slave interface structure and may function as a slave for a second master/slave interface structure. For example, circuit portion 20 (see
A sample transfer will now be described using master interface 37 and slave interfaces 34–36 of
A sample transfer will now be described using master interface 30 and slave interfaces 31–33 of
How the fields in configuration register 100 (see
In one embodiment, an integrated circuit comprises: a first interface and a second interface, wherein each of the first and second interface operate according to a same protocol and are capable of operating simultaneously; configuration circuitry coupled to the first and second interface and capable of configuration each of the first and second interfaces as one of a master interface or a slave interface; a plurality of inputloutput terminals; and multiplexing circuitry coupled to the first and second interface, wherein the multiplexing circuitry selectively communicates signals to or from one of the first and second interface to the plurality of input/output terminals.
In one embodiment, a data processor, comprises: a first interface; configuration circuitry coupled to the first interface and capable of configuring the first interface as one of a master interface or a slave interface; storage circuitry; first address generation circuitry coupled to the first interface, said first address generation circuitry generating an external address when the first interface is configured as a master interface and providing only a portion of said external address via the first interface, wherein the portion of the external address provides a slave enable indicator; and second address generation circuitry coupled to the first external address generation circuitry and to the storage circuitry, said second address generation circuitry generating an internal address for accessing the storage circuitry, wherein the first address generation circuitry operates independently of the second address generation circuitry, and wherein the first address generation circuitry and the second address generation circuitry operate using different clock rates.
In one embodiment, a data processor, comprises: a first interface; configuration circuitry coupled to the first interface and capable of configuring the first interface as one of a master interface or a slave interface; storage circuitry; first address generation circuitry coupled to the first interface, said first address generation circuitry generating an external address when the first interface is configured as a master interface and providing only a portion of said external address via the first interface, wherein the portion of the external address provides a slave enable indicator; and second address generation circuitry coupled to the first external address generation circuitry and to the storage circuitry, said second address generation circuitry generating an internal address for accessing the storage circuitry, wherein the first address generation circuitry operates independently of the second address generation circuitry, and wherein the first address generation circuitry and the second address generation circuitry operate using different data burst sizes.
In the foregoing specification, the invention has been described with reference to specific embodiments. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or element of any or all the claims. As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
Number | Name | Date | Kind |
---|---|---|---|
4368514 | Persaud et al. | Jan 1983 | A |
4700292 | Campanini | Oct 1987 | A |
4752870 | Matsumura | Jun 1988 | A |
5109490 | Arimilli et al. | Apr 1992 | A |
5218681 | Gephardt | Jun 1993 | A |
5353415 | Wolford et al. | Oct 1994 | A |
5541853 | Croft | Jul 1996 | A |
5734843 | Gephardt | Mar 1998 | A |
5790801 | Funato | Aug 1998 | A |
6038259 | Nanya | Mar 2000 | A |
6079010 | D'Arcy | Jun 2000 | A |
6112229 | Hardy et al. | Aug 2000 | A |
6122690 | Nannetti et al. | Sep 2000 | A |
6247046 | Yanai et al. | Jun 2001 | B1 |
6425068 | Vorbach | Jul 2002 | B1 |
20050033951 | Madter et al. | Feb 2005 | A1 |
Number | Date | Country | |
---|---|---|---|
20040225862 A1 | Nov 2004 | US |