Programming of DIMM termination resistance values

Information

  • Patent Grant
  • 8169233
  • Patent Number
    8,169,233
  • Date Filed
    Wednesday, June 9, 2010
    14 years ago
  • Date Issued
    Tuesday, May 1, 2012
    12 years ago
Abstract
Systems, methods, and apparatus, including computer program products, for providing termination resistance in a memory module are provided. An apparatus is provided that includes a plurality of memory circuits; an interface circuit operable to communicate with the plurality of memory circuits and to communicate with a memory controller; and a transmission line electrically coupling the interface circuit to a memory controller, wherein the interface circuit is operable to terminate the transmission line with a single termination resistance that is selected based on a plurality of resistance-setting commands received from the memory controller.
Description
BACKGROUND

This specification relates to controlling of termination resistance values in memory modules.


A typical memory system includes memory modules that are arranged in slots. Each memory module includes a number of memory chips. For example, the memory module can be a dual inline memory module (DIMM) and the memory chips can be dynamic random access memory chips (DRAMs). Memory modules are physically placed in slot connectors and are electrically coupled to other components, e.g., one or more memory controllers, through channels and buses. These channels and buses form transmission lines that are electrically terminated at the connected DIMMs. A memory controller can select any of the DIMMs in a channel for reading or writing, but it will only access one DIMM at a time. The slot in which the DIMM accessed for reading or writing is located is referred to as the “active” slot, while slots in which the other non-accessed DIMMs are located are referred to as the “standby” slots.


A typical DIMM can have a single rank or multiple ranks. A rank is an independent set of DRAMs within the DIMM that can be simultaneously accessed for the full data bit-width of the DIMM, such as 72 bits. The rank to which data is being written is called the target rank for writes. The rank from which data is being read is called the target rank for reads.


SUMMARY

This specification describes technologies relating to controlling of termination resistance values in memory modules.


In general, one aspect of the subject matter described in this specification can be embodied in an apparatus for providing termination resistance in a memory module that includes a plurality of memory circuits; an interface circuit operable to communicate with the plurality of memory circuits and to communicate with a memory controller; and a transmission line electrically coupling the interface circuit to a memory controller, wherein the interface circuit is operable to terminate the transmission line with a single termination resistance that is selected based on a plurality of resistance-setting commands received from the memory controller. Other embodiments of this aspect include corresponding systems, method, computer readable media, and computer program products.


These and other embodiments can optionally include one or more of the following features. The apparatus provides single termination resistance with an on-die termination (ODT) resistor. The interface circuit selects a value of the single termination resistance from a look-up table. The plurality of resistance-setting commands received from the memory controller include a first mode register set (MRS) command and a second MRS command. A value of the single termination resistance during read operations is different from a value of the single termination resistance during write operations. The plurality of memory circuits is a plurality of dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM). The single termination resistance has a value that is different from values specified by the resistance-setting commands received from the memory controller.


In general, one aspect of the subject matter described in this specification can be embodied in methods that include the actions of receiving a plurality of resistance-setting commands from a memory controller at an interface circuit, wherein the interface circuit is operable to communicate with a plurality of memory circuits and with the memory controller; selecting a resistance value based on the received plurality of resistance-setting commands; and terminating a transmission line between the interface circuit and the memory controller with a resistor of the selected resistance value. Other embodiments of this aspect include corresponding systems, apparatus, computer readable media, and computer program products.


In general, one aspect of the subject matter described in this specification can be embodied in an apparatus for providing termination resistance in a memory module that includes a first memory circuit having a first termination resistor with a selectable value; a second memory circuit having a second termination resistor with a selectable value; and an interface circuit operable to communicate with the first and the second memory circuits and a memory controller, wherein the interface circuit is operable to select a single value for the first and the second termination resistors that is chosen based on a plurality of resistance-setting commands received from the memory controller. Other embodiments of this aspect include corresponding systems, method, computer readable media, and computer program products.


These and other embodiments can optionally include one or more of the following features. The first and the second termination resistors are ODT resistors. The interface circuit selects a single value for the first and the second termination resistors from a look-up table. The plurality of resistance-setting commands received from the memory controller includes an MRS command and a second MRS command. Values of the first and the second termination resistors during read operations are different from values of the first and the second termination resistors during write operations. The first and the second memory circuits are DRAM integrated circuits in a DIMM. The single value selected by the interface circuit for the first and the second termination resistors is different from values indicated by the plurality of resistance-setting commands received from the memory controller.


Particular embodiments of the subject matter described in this specification can be implemented to realize one or more of the following advantages. The use of the interface circuit for transmission line termination allows for the creation of a single point of termination for a DIMM. This can improve performance, reduce cost, and provide other benefits for a memory module design. An interface circuit for transmission line termination can be used to tune termination values specifically for a DIMM. Standard termination values, for example the termination values mandated by Joint Electron Devices Engineering Council (JEDEC), might not always be optimal for a given DIMM, leading to sub-optimal performance.


The use of an interface circuit for transmission line termination can provide optimal ODT resistance for a given DIMM, which preserves signal integrity and minimizes noise on the transmission line. Furthermore, the use of the interface circuit can also provide termination resistance for a DIMM that is higher than the resistance mandated by a standard. If higher resistance is used while signal integrity is maintained, power dissipation will be reduced because the amount of dissipated power is inversely proportional to the value of termination resistance. As a result, the use of an interface circuit for transmission line termination can improve electrical performance and signal quality within a memory system using one or more DIMMs.


The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1A-F are block diagrams of example computer systems.



FIG. 2 is an example timing diagram for a 3-DIMMs per channel (3DPC) configuration.



FIGS. 3A-C are block diagrams of an example memory module using an interface circuit to provide DIMM termination.



FIG. 4 is a block diagram illustrating a slice of an example 2-rank DIMM using two interface circuits for DIMM termination per slice.



FIG. 5 is a block diagram illustrating a slice of an example 2-rank DIMM with one interface circuit per slice.



FIG. 6 illustrates a physical layout of an example printed circuit board (PCB) of a DIMM with an interface circuit.



FIG. 7 is a flowchart illustrating an example method for providing termination resistance in a memory module.





Like reference numbers and designations in the various drawings indicate like elements.


DETAILED DESCRIPTION

Electrical termination of a transmission line involves placing a termination resistor at the end of the transmission line to prevent the signal from being reflected back from the end of the line, causing interference. In some memory systems, transmission lines that carry data signals are terminated using on-die termination (ODT). ODT is a technology that places an impedance matched termination resistor in transmission lines inside a semiconductor chip. During system initialization, values of ODT resistors used by DRAMs can be set by the memory controller using mode register set (MRS) commands. In addition, the memory controller can turn a given ODT resistor on or turn off at the DRAM with an ODT control signal. When the ODT resistor is turned on with an ODT control signal, it begins to terminate the associated transmission line. For example, a memory controller in a double-data-rate three (DDR3) system can select two static termination resistor values during initialization for all DRAMs within a DIMM using MRS commands. During system operation, the first ODT value (Rtt_Nom) is applied to non-target ranks when the corresponding rank's ODT signal is asserted for both reads and writes. The second ODT value (Rtt_WR) is applied only to the target rank of a write when that rank's ODT signal is asserted.



FIGS. 1A-F are block diagrams of example computer systems. FIG. 1A is a block diagram of an example computer system 100A. Computer system 100A includes a platform chassis 110, which includes at least one motherboard 120. In some implementations, the example computer system 100A includes a single case, a single power supply, and a single motherboard/blade. In other implementations, computer system 100A can include multiple cases, power supplies, and motherboards/blades.


The motherboard 120 includes a processor section 126 and a memory section 128. In some implementations, the motherboard 120 includes multiple processor sections 126 and/or multiple memory sections 128. The processor section 126 includes at least one processor 125 and at least one memory controller 124. The memory section 128 includes one or more memory modules 130 that can communicate with the processor section 126 using the memory bus 134 (e.g., when the memory section 128 is coupled to the processor section 126). The memory controller 124 can be located in a variety of places. For example, the memory controller 124 can be implemented in one or more of the physical devices associated with the processor section 126, or it can be implemented in one or more of the physical devices associated with the memory section 128.



FIG. 1B is a block diagram that illustrates a more detailed view of the processor section 126 and the memory section 128, which includes one or more memory modules 130. Each memory module 130 communicates with the processor section 126 over the memory bus 134. In some implementations, the example memory module 130 includes one or more interface circuits 150 and one or more memory chips 142. While the following discussion generally references a single interface circuit 150, more than one interface circuit 150 can be used. In addition, though the computer systems are described with reference to memory chips as DRAMs, the memory chip 142 can be, but is not limited to, DRAM, synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, DDR4 SDRAM, etc.), graphics double data rate synchronous DRAM (GDDR SDRAM, GDDR2 SDRAM, GDDR3 SDRAM, etc.), quad data rate DRAM (QDR DRAM), RAMBUS XDR DRAM (XDR DRAM), fast page mode DRAM (FPM DRAM), video DRAM (VDRAM), extended data out DRAM (EDO DRAM), burst EDO RAM (BEDO DRAM), multibank DRAM (MDRAM), synchronous graphics RAM (SGRAM), phase-change memory, flash memory, and/or any other type of volatile or non-volatile memory.


Each of the one or more interface circuits 150 can be, for example, a data buffer, a data buffer chip, a buffer chip, or an interface chip. The location of the interface circuit 150 is not fixed to a particular module or section of the computer system. For example, the interface circuit 150 can be positioned between the processor section 126 and the memory module 130 (FIG. 1C). In some implementations, the interface circuit 150 is located in the memory controller 124, as shown in FIG. 1D. In yet some other implementations, each memory chip 142 is coupled to its own interface circuit 150 within memory module 130 (FIG. 1E). And in another implementation, the interface circuit 150 is located in the processor section 126 or in processor 125, as shown in FIG. 1F.


The interface circuit 150 can act as an interface between the memory chips 142 and the memory controller 124. In some implementations, the interface circuit 150 accepts signals and commands from the memory controller 124 and relays or transmits commands or signals to the memory chips 142. These could be the same or different signals or commands. Each of the one or more interface circuits 150 can also emulate a virtual memory module, presenting the memory controller 124 with an appearance of one or more virtual memory circuits. In the emulation mode, the memory controller 124 interacts with the interface circuit 150 as it would with a physical DRAM or multiple physical DRAMs on a memory module, depending on the configuration of the interface circuit 150. Therefore, in emulation mode, the memory controller 124 could see a single-rank memory module or a multiple-rank memory module in the place of the interface circuit 150, depending on the configuration of the interface circuit 150. In case multiple interface circuits 150 are used for emulation, each interface circuit 150 can emulate a portion (i.e., a slice) of the virtual memory module that is presented to the memory controller 124.


An interface circuit 150 that is located on a memory module can also act as a data buffer for multiple memory chips 142. In particular, the interface circuit 150 can buffer one or more ranks and present a single controllable point of termination for a transmission line. The interface circuit 150 can be connected to memory chips 142 or to the memory controller 124 with one or more transmission lines. The interface circuit 150 can therefore provide a more flexible memory module (e.g., DIMM) termination instead of, or in addition to, the memory chips (e.g., DRAM) located on the memory module.


The interface circuit 150 can terminate all transmission lines or just a portion of the transmission lines of the DIMM. In case when multiple interface circuits 150 are used, each interface circuit 150 can terminate a portion of the transmission lines of the DIMM. For example, the interface circuit 150 can be used to terminate 8 bits of data. If there are 72 bits of data provided by a DIMM, then nine interface circuits are needed to terminate the entire DIMM. In another example, the interface circuit 150 can be used to terminate 72 bits of data, in which case one interface circuit 150 would be needed to terminate the entire 72-bit DIMM. Additionally, the interface circuit 150 can terminate various transmission lines. For example, the interface circuit 150 can terminate a transmission line between the memory controller 124 and the interface circuit 150. In addition or alternatively, the interface circuit 150 can terminate a transmission line between the interface circuit 150 and one or more of the memory chips 142.


Each of one or more interface circuits 150 can respond to a plurality of ODT signals or MRS commands received from the memory controller 124. In some implementations, the memory controller 124 sends one ODT signal or MRS command per physical rank. In some other implementations, the memory controller 124 sends more than one ODT signal or MRS command per physical rank. Regardless, because the interface circuit 150 is used as a point of termination, the interface circuit 150 can apply different or asymmetric termination values for non-target ranks during reads and writes. Using different non-target DIMM termination values for reads and writes allows for improved signal quality of the channel and reduced power dissipation due to the inherent asymmetry of a termination line.


Moreover, because the interface circuit 150 can be aware of the state of other signals/commands to a DIMM, the interface circuit 150 can choose a single termination value that is optimal for the entire DIMM. For example, the interface circuit 150 can use a lookup table filled with termination values to select a single termination value based on the MRS commands it receives from the memory controller 124. The lookup table can be stored within interface circuit 150 or in other memory locations, e.g., memory controller 124, processor 125, or a memory module 130. In another example, the interface circuit 150 can compute a single termination based on one or more stored formula. The formula can accept input parameters associated with MRS commands from the memory controller 124 and output a single termination value. Other techniques of choosing termination values can be used, e.g., applying specific voltages to specific pins of the interface circuit 150 or programming one or more registers in the interface circuit 150. The register can be, for example, a flip-flop or a storage element.


Tables 1A and 1B show example lookup tables that can be used by the interface circuit 150 to select termination values in a memory system with a two-rank DIMM.









TABLE 1A







Termination values expressed in terms of resistance RZQ.









term_b
















disabled
RZQ/4
RZQ/2
RZQ/6
RZQ/12
RZQ/8
reserved
reserved




















term_a
disabled
disabled
RZQ/4
RZQ/2
RZQ/6
RZQ/12
RZQ/8
TBD
TBD



RZQ/4

RZQ/8
RZQ/6
RZQ/12
RZQ/12
RZQ/12
TBD
TBD



RZQ/2


RZQ/4
RZQ/8
RZQ/12
RZQ/12
TBD
TBD



RZQ/6



RZQ/12
RZQ/12
RZQ/12
TBD
TBD



RZQ/12




RZQ/12
RZQ/12
TBD
TBD



RZQ/8





RZQ/12
TBD
TBD



reserved






TBD
TBD



reserved







TBD
















TABLE 1B







Termination values of Table 1A with RZQ = 240 ohm









term_b
















inf
60
120
40
20
30
reserved
reserved




















term_a
inf
inf
60
120
40
20
30
TBD
TBD



60

30
40
20
20
20
TBD
TBD



120 


60
30
20
20
TBD
TBD



40



20
20
20
TBD
TBD



20




20
20
TBD
TBD



30





20
TBD
TBD



reserved






TBD
TBD



reserved







TBD









Because the example memory system has two ranks, it would normally require two MRS commands from the memory controller 124 to set ODT values in each of the ranks. In particular, memory controller 124 would issue an MRS0 command that would set the ODT resistor values in DRAMs of the first rank (e.g., as shown by term_a in Tables 1A-B) and would also issue an ODT0 command signal that would activate corresponding ODT resistors in the first rank. Memory controller 124 would also issue an MRS1 command that would set the ODT resistor values in DRAMs of the second rank (e.g., as shown by term_b in Tables 1A-B) and would also issue an ODT1 command signal that would enable the corresponding ODT resistors in the second rank.


However, because the interface circuit 150 is aware of signals/commands transmitted by the memory controller 124 to both ranks of the DIMM, it can select a single ODT resistor value for both ranks using a lookup table, for example, the resistor value shown in Tables 1A-B. The interface circuit 150 can then terminate the transmission line with the ODT resistor having the single selected termination value.


In addition or alternatively, the interface circuit 150 can also issue signals/commands to DRAMs in each rank to set their internal ODTs to the selected termination value. This single termination value may be optimized for multiple ranks to improve electrical performance and signal quality.


For example, if the memory controller 124 specifies the first rank's ODT value equal to RZQ/6 and the second rank's ODT value equal to RZQ/12, the interface circuit 150 will signal or apply an ODT resistance value of RZQ/12. The resulting value can be found in the lookup table at the intersection of a row and a column for given resistance values for rank 0 (term_a) and rank 1 (term_b), which are received from the memory controller 124 in the form of MRS commands. In case the RZQ variable is set to 240 ohm, the single value signaled or applied by the interface circuit 150 will be 240/12=20 ohm. A similar lookup table approach can be applied to Rtt_Nom values, Rtt_WR values, or termination values for other types of signals.


In some implementations, the size of the lookup table is reduced by ‘folding’ the lookup table due to symmetry of the entry values (Rtt). In some other implementations, an asymmetric lookup table is used in which the entry values are not diagonally symmetric. In addition, the resulting lookup table entries do not need to correspond to the parallel resistor equivalent of Joint Electron Devices Engineering Council (JEDEC) standard termination values. For example, the table entry corresponding to 40 ohm for the first rank in parallel with 40 ohm for the second rank (40//40) does not have to result in a 20 ohm termination setting. In addition, in some implementations, the lookup table entries are different from Rtt_Nom or Rtt_WR values required by the JEDEC standards.


While the above discussion focused on a scenario with a single interface circuit 150, the same techniques can be applied to a scenario with multiple interface circuits 150. For example, in case multiple interface circuits 150 are used, each interface circuit 150 can select a termination value for the portion of the DIMM that is being terminated by that interface circuit 150 using the techniques discussed above.



FIG. 2 is an example timing diagram 200 for a 3-DIMMs per channel (3DPC) configuration, where each DIMM is a two-rank DIMM. The timing diagram 200 shows timing waveforms for each of the DIMMs in three slots: DIMM A 220, DIMM B 222, and DIMM C 224. In FIG. 2, each DIMM receives two ODT signal waveforms for ranks 0 and 1 (ODT0, ODT1), thus showing a total of six ODT signals: signals 230 and 232 for DIMM A, signals 234 and 236 for DIMM B, and signals 238 and 240 for DIMM C. In addition, the timing diagram 200 shows a Read signal 250 applied to DIMM A either at rank 0 (R0) or rank 1 (R1). The timing diagram 200 also shows a Write signal 252 applied to DIMM A at rank 0 (R0).


The values stored in the lookup table can be different from the ODT values mandated by JEDEC. For example, in the 40//40 scenario (R0 Rtt_Nom=ZQ/6=40 ohm, R1 Rtt_Nom=ZQ/6=40 ohm, with ZQ=240 ohm), a traditional two-rank DIMM system relying on JEDEC standard will have its memory controller set DIMM termination values of either INF (infinity or open circuit), 40 ohm (assert either ODT0 or ODT1), or 20 ohm (assert ODT0 and ODT1). On the other hand, the interface circuit 150 relying on the lookup table can set the ODT resistance value differently from memory controller relying on JEDEC-mandated values. For example, for the same values of R0 Rtt_Nom and R1 Rtt_Nom, the interface circuit 150 can select a resistance value that is equal to ZQ/12 (20 ohm) or ZQ/8 (30 ohm) or some other termination value. Therefore, even though the timing diagram 200 shows a 20 ohm termination value for the 40//40 scenario, the selected ODT value could correspond to any other value specified in the lookup table for the specified pair of R0 and R1 values.


When the interface circuit 150 is used with one-rank DIMMs, the memory controller can continue to provide ODT0 and ODT1 signals to distinguish between reads and writes even though ODT1 signal might not have any effect in a traditional memory channel. This allows single and multiple rank DIMMs to have the same electrical performance. In some other implementations, various encodings of the ODT signals are used. For example, the interface circuit 150 can assert ODT0 signal for non-target DIMMs for reads and ODT1 signal for non-target DIMMs for writes.


In some implementations, termination resistance values in multi-rank DIMM configurations are selected in a similar manner. For example, an interface circuit provides a multi-rank DIMM termination resistance using a look-up table. In another example, an interface circuit can also provide a multi-rank DIMM termination resistance that is different from the JEDEC standard termination value. Additionally, an interface circuit can provide a multi-rank DIMM with a single termination resistance. An interface circuit can also provide a multi-rank DIMM with a termination resistance that optimizes electrical performance. The termination resistance can be different for reads and writes.


In some implementations, a DIMM is configured with a single load on the data lines but receives multiple ODT input signals or commands. This means that while the DIMM can terminate the data line with a single termination resistance, the DIMM will appear to the memory controller as though it has two termination resistances that can be configured by the memory controller with multiple ODT signals and MRS commands. In some other implementations a DIMM has an ODT value that is a programmable function of the of ODT input signals that are asserted by the system or memory controller.



FIGS. 3A-C are block diagrams of an example memory module using an interface circuit to provide DIMM termination. In some implementations, FIGS. 3A-C include an interface circuit similar to interface circuit 150 described in the context of the computer systems in FIGS. 1A-F. In particular, DRAMs 316, 318, 320, and 324 can have attributes comparable to those described with respect to memory chips 142, respectively. Likewise, the interface circuit 314 can have attributes comparable to, and illustrative of, the interface circuits 150 shown in FIGS. 1A-F. Similarly, other elements within FIGS. 3A-C have attributes comparable to, and illustrative of, corresponding elements in FIGS. 1A-F.


Referring to FIG. 3A, the interface circuit 314 is coupled to DRAMs 316, 318, 320, and 324. The interface circuit 314 is coupled to the memory controller using memory bus signals DQ[3:0], DQ[7:4], DQS1_t, DQS1_c, DQS0_t, DQS0_c, VSS. Additionally, other bus signals (not shown) can be included. FIG. 3A shows only a partial view of the DIMM, which provides 8 bits of data to the system through DQ[7:4] bus signal. For an ECC DIMM with 72 bits of data, there would be a total of 36 DRAM devices and there would be 9 instances of interface circuit 314. In FIG. 3A, the interface circuit combines two virtual ranks to present a single physical rank to the system (e.g., to a memory controller). DRAMs 316 and 320 belong to a virtual rank 0 and DRAMs 318 and 324 are parts of virtual rank 1. As shown, DRAMs devices 316 and 318 together with interface circuit 314 operate to form a single larger virtual DRAM device 312. In a similar fashion, DRAM devices 320 and 324 together with interface circuit 314 operate to form a virtual DRAM device 310.


The virtual DRAM device 310 represents a “slice” of the DIMM, as it provides a “nibble” (e.g., 4 bits) of data to the memory system. DRAM devices 316 and 318 also represent a slice that emulates a single virtual DRAM 312. The interface circuit 314 thus provides termination for two slices of DIMM comprising virtual DRAM devices 310 and 312. Additionally, as a result of emulation, the system sees a single-rank DIMM.


In some implementations, the interface circuit 314 is used to provide termination of transmission lines coupled to DIMM. FIG. 3A shows resistors 333, 334, 336, 337 that can be used, either alone or in various combinations with each other, for transmission line termination. First, the interface circuit 314 can include one or more ODT resistors 334 (annotated as T2). For example, ODT resistor 334 may be used to terminate DQ[7:4] channel. It is noted that DQ[7:4] is a bus having four pins: DQ7, DQ6, DQ5, DQ4 and thus may require four different ODT resistors. In addition, DRAMs 316, 318, 320, and 324 can also include their own ODT resistors 336 (annotated as T).


In some implementations, the circuit of FIG. 3A also includes one or more resistors 333 that provide series stub termination of the DQ signals. These resistors are used in addition to any parallel DIMM termination, for example, provided by ODT resistors 334 and 336. Other similar value stub resistors can also be used with transmission lines associated with other data signals. For example, in FIG. 3A, resistor 337 is a calibration resistor connected to pin ZQ.



FIG. 3A also shows that the interface circuit 314 can receive ODT control signals though pins ODT0326 and ODT1328. As described above, the ODT signal turns on or turns off a given ODT resistor at the DRAM. As shown in FIG. 3A, the ODT signal to DRAM devices in virtual rank 0 is ODT0326 and the ODT signal to the DRAM devices in virtual rank 1 is ODT1328.


Because the interface circuit 314 provides for flexibility pins for signals ODT 330, ODT 332, ODT0326, and ODT1328 may be connected in a number of different configurations.


In one example, ODT0326 and ODT1328 are connected directly to the system (e.g., memory controller); ODT 330 and ODT 332 are hard-wired; and interface circuit 314 performs the function determine the value of DIMM termination based on the values of ODT0 and ODT1 (e.g., using a lookup table as describe above with respect to Tables 1A-B). In this manner, the DIMM can use the flexibility provided by using two ODT signals, yet provide the appearance of a single physical rank to the system.


For example, if the memory controller instructs rank 0 on the DIMM to terminate to 40 ohm and rank 1 to terminate to 40 ohm, without the interface circuit, a standard DIMM would then set termination of 40 ohm on each of two DRAM devices. The resulting parallel combination of two nets each terminated to 40 ohm would then appear electrically to be terminated to 20 ohm. However, the presence of interface circuit provides for additional flexibility in setting ODT termination values. For example, a system designer may determine, through simulation, that a single termination value of 15 ohm (different from the normal, standard-mandated value of 20 ohm) is electrically better for a DIMM embodiment using interface circuits. The interface circuit 314, using a lookup table as described, may therefore present a single termination value of 15 ohm to the memory controller.


In another example, ODT0326 and ODT1328 are connected to a logic circuit (not shown) that can derive values for ODT0326 and ODT1328 not just from one or more ODT signals received from the system, but also from any of the control, address, or other signals present on the DIMM. The signals ODT 330 and ODT 332 can be hard-wired or can be wired to the logic circuit. Additionally, there can be fewer or more than two ODT signals between the logic circuit and interface circuit 314. The one or more logic circuits can be a CPLD, ASIC, FPGA, or part of an intelligent register (on an R-DIMM or registered-DIMM for example), or a combination of such components.


In some implementations, the function of the logic circuit is performed by a modified JEDEC register with a number of additional pins added. The function of the logic circuit can also be performed by one or more interface circuits and shared between the interface circuits using signals (e.g., ODT 330 and ODT 332) as a bus to communicate the termination values that are to be used by each interface circuit.


In some implementations, the logic circuit determines the target rank and non-target ranks for reads or writes and then communicates this information to each of the interface circuits so that termination values can be set appropriately. The lookup table or tables for termination values can be located in the interface circuits, in one or more logic circuit, or shared/partitioned between components. The exact partitioning of the lookup table function to determine termination values between the interface circuits and any logic circuit depends, for example, on the economics of package size, logic function and speed, or number of pins.


In another implementation, signals ODT 330 and ODT 332 are used in combination with dynamic termination of the DRAM (i.e., termination that can vary between read and write operations and also between target and non-target ranks) in addition to termination of the DIMM provided by interface circuit 314. For example, the system can operate as though the DIMM is a single-rank DIMM and send termination commands to the DIMM as though it were a single-rank DIMM. However, in reality, there are two virtual ranks and two DRAM devices (such as DRAM 316 and DRAM 318) that each have their own termination in addition to the interface circuit. A system designer has an ability to vary or tune the logical and timing behavior as well as the values of termination in three places: (a) DRAM 316; (b) DRAM 318; and (c) interface circuit 314, to improve signal quality of the channel and reduce power dissipation.


A DIMM with four physical ranks and two logical ranks can be created in a similar fashion to the one described above. A computer system using 2-rank DIMMs would have two ODT signals provided to each DIMM. In some implementations, these two ODT signals are used, with or without an additional logic circuit(s) to adjust the value of DIMM termination at the interface circuits and/or at any or all of the DRAM devices in the four physical ranks behind the interface circuits.



FIG. 3B is a block diagram illustrating the example structure of an ODT block within a DIMM. The structure illustrated in FIG. 3B embodies the ODT resistor 336 (box T in DRAMs 316, 318, 320, and 324) described with respect to FIG. 3A. In particular, ODT block 342 includes an ODT resistor 346 that is coupled to ground/reference voltage 344 on one side and a switch 348 on the other side. The switch 348 is controlled with ODT signal 352, which can turn the switch either on or off. When the switch 348 is turned on, it connects the ODT resistor 346 to transmission line 340, permitting ODT resistor 346 to terminate the transmission line 340. When the switch 348 is turned off, it disconnects the ODT resistor 346 from the transmission line 340. In addition, transmission line 340 can be coupled to other circuitry 350 within DIMM. The value of the ODT resistor 346 can be selected using MRS command 354.



FIG. 3C is a block diagram illustrating the exemplary structure of ODT block within an interface circuit. The structure illustrated in FIG. 3B embodies the ODT resistor 366 (box T2 in DRAMs 316, 318, 320, and 324) described above with respect to FIG. 3A. In particular, ODT block 360 includes an ODT resistor 366 that is coupled to ground/reference voltage 362 on one side and a switch 368 on the other side. In addition, the ODT block 360 can be controlled by circuit 372, which can receive ODT signals and MRS commands from a memory controller. Circuit 372 is a part of the interface circuit 314 in FIG. 3A and is responsible for controlling the ODT. The switch 368 can be controlled with either ODT0 signal 376 or ODT1 signal 378, which are supplied by the circuit 372.


In some implementations, circuit 372 transmits the same MRS commands or ODT signals to the ODT resistor 366 that it receives from the memory controller. In some other implementations, circuit 372 generates its own commands or signals that are different from the commands/signals it receives from the memory controller. Circuit 372 can generate these MRS commands or ODT signals based on a lookup table and the input commands/signals from the memory controller. When the switch 368 receives an ODT signal from the circuit 372, it can either turn on or turn off. When the switch 368 is turned on, it connects the ODT resistor 366 to the transmission line 370, permitting ODT resistor 366 to terminate the transmission line 370. When the switch 368 is turned off, it disconnects the ODT resistor 366 from the transmission line 370. In addition, transmission line 370 can be coupled to other circuitry 380 within the interface circuit. The value of the ODT resistor 366 can be selected using MRS command 374.



FIG. 4 is a block diagram illustrating one slice of an example 2-rank DIMM using two interface circuits for DIMM termination per slice. In some implementations, FIG. 4 includes an interface circuit similar to those previously described in FIGS. 1A-F and 3A-C. Elements within FIG. 4 can have attributes comparable to and illustrative of corresponding elements in FIGS. 1A-F and 3A-C.



FIG. 4 shows a DIMM 400 that has two virtual ranks and four physical ranks DRAM 410 is in physical rank number zero, DRAM 412 is in the first physical rank, DRAM 414 is in the second physical rank, DRAM 416 is in the third physical rank. DRAM 410 and DRAM 412 are in virtual rank 0 440. DRAM 414 and DRAM 416 are in virtual rank 1 442. In general, DRAMs 410, 412, 414, and 416 have attributes comparable to and illustrative to DRAMs discussed with respect to FIGS. 1A-F and 3A-C. For example, DRAMs 410, 412, 414, and 416 can include ODT resistors 464, which were discussed with respect to FIG. 3B.


In addition, FIG. 4 shows an interface circuit 420 and an interface circuit 422. In some implementations, interface circuits 420 and 422 have attributes similar to the interface circuits described with respect to FIGS. 1A-F and 3A-C. For example, interface circuits 420 and 422 can include ODT resistors 460 and 462, which function similarly to ODT resistor 366 discussed above with respect to FIG. 3C.



FIG. 4 also shows one instance of a logic circuit 424. DIMM 400 can include other components, for example, a register, smart (i.e. modified or enhanced) register device or register circuit for R-DIMMs, a discrete PLL and/or DLL, voltage regulators, SPD, other non-volatile memory devices, bypass capacitors, resistors, and other components. In addition or alternatively, some of the above components can be integrated with each other or with other components.


In some implementation, DIMM 400 is connected to the system (e.g., memory controller) through conducting fingers 430 of the DIMM PCB. Some, but not all, of these fingers are illustrated in FIG. 4, for example, the finger for DQS0_t, shown as finger 430. Each finger receives a signal and corresponds to a signal name, e.g., DQS0_t 432. DQ0434 is an output (or pin) of the interface circuits 420 and 422. In some implementations, these two outputs are tied, dotted or connected to an electrical network. Any termination applied to any pin on this electrical network thus applies to the entire electrical network (and the same is true for other similar signals and electrical networks). Furthermore, interface circuits 420 and 422 are shown as containing multiple instances of switch 436. Net DQ0434 is connected through switches 436 to signal pin DQ[0] of DRAM 410, DRAM 412, DRAM 414, and DRAM 416.


In some implementations, switch 436 is a single-pole single-throw (SPST) switch. In some other implementations, switch 436 is mechanical or non-mechanical. Regardless, the switch 436 can be one of various switch types, for example, SPST, DPDT, or SPDT, a two-way or bidirectional switch or circuit element, a parallel combination of one-way, uni-directional switches or circuit elements, a CMOS switch, a multiplexor (MUX), a de-multiplexer (de-MUX), a CMOS bidirectional buffer; a CMOS pass gate, or any other type of switch.


The function of the switches 436 is to allow the physical DRAM devices behind the interface circuit to be connected together to emulate a virtual DRAM. These switches prevent such factors as bus contention, logic contention or other factors that may prevent or present unwanted problems from such a connection. Any logic function or switching element that achieves this purpose can be used. Any logical or electrical delay introduced by such a switch or logic can be compensated for. For example, the address and/or command signals can be modified through controlled delay or other logical devices.


Switch 436 is controlled by signals from logic circuit 424 coupled to the interface circuits, including interface circuit 420 and interface circuit 422. In some implementations, switches 436 in the interface circuits are controlled so that only one of the DRAM devices is connected to any given signal net at one time. Thus, for example, if the switch connecting net DQ0434 to DRAM 410 is closed, then switches connecting net DQ0434 to DRAMs 412, 414, 416 are open.


In some implementations, the termination of nets, such as DQ0434, by interface circuits 420 and 422 is controlled by inputs ODT0i 444 (where “i” stands for internal) and ODT1i 446. While the term ODT has been used in the context of DRAM devices, the on-die termination used by an interface circuit can be different from the on-die termination used by a DRAM device. Since ODT0i 444 and ODT1i 446 are internal signals, the interface circuit termination circuits can be different from standard DRAM devices. Additionally, the signal levels, protocol, and timing can also be different from standard DRAM devices.


The ability to adjust the interface circuit's ODT behavior provides the system designer with an ability to vary or tune the values and timing of ODT, which may improve signal quality of the channel and reduce power dissipation. In one example, as part of the target rank, interface circuit 420 provides termination when DRAM 410 is connected to net DQ0434. In this example, the interface circuit 420 can be controlled by ODT0i 444 and ODT1i 446. As part of the non-target rank, interface circuit 422 can also provide a different value of termination (including no termination at all) as controlled by signals ODT0i 444 and ODT1i 446.


In some implementations, the ODT control signals or commands from the system are ODT0448 and ODT1450. The ODT input signals or commands to the DRAM devices are shown by ODT signals 452, 454, 456, 458. In some implementations, the ODT signals 452, 454, 456, 458 are not connected. In some other implementations, ODT signals 452, 454, 456, 458 are connected, for example, as: (a) hardwired (i.e. to VSS or VDD or other fixed voltage); (b) connected to logic circuit 424; (c) directly connected to the system; or (d) a combination of (a), (b), and (c).


As shown in FIG. 4, transmission line termination can be placed in a number of locations, for example, (a) at the output of interface circuit 420; (b) the output of interface circuit 422; (c) the output of DRAM 410; (d) the output of DRAM 412; (e) the output of DRAM 414; (f) the output of DRAM 416; or may use any combination of these. By choosing location for termination, the system designer can vary or tune the values and timing of termination to improve signal quality of the channel and reduce power dissipation.


Furthermore, in some implementations, a memory controller in a DDR3 system sets termination values to different values than used in normal operation during different DRAM modes or during other DRAM, DIMM and system modes, phases, or steps of operation. DRAM modes can include initialization, wear-leveling, initial calibration, periodic calibration, DLL off, DLL disabled, DLL frozen, or various power-down modes.


In some implementations, the logic circuit 424 may also be programmed (by design as part of its logic or caused by control or other signals or means) to operate differently during different modes/phases of operation so that a DIMM with one or more interface circuits can appear, respond to, and communicate with the system as if it were a standard or traditional DIMM without interface circuits. Thus, for example, logic circuit 424 can use different termination values during different phases of operation (e.g., memory reads and memory writes) either by pre-programmed design or by external command or control, or the logic timing may operate differently. For example, logic circuit 424 can use a termination value during read operations that is different from a termination value during write operations.


As a result, in some implementations, no changes to a standard computer system (motherboard, CPU, BIOS, chipset, component values, etc.) need to be made to accommodate DIMM 400 with one or more interface circuits. Therefore, while in some implementations the DIMM 400 with the interface circuit(s) may operate differently from a standard or traditional DIMM (for example, by using different termination values or different timing than a standard DIMM), the modified DIMM would appear to the computer system/memory controller as if it were operating as a standard DIMM.


In some implementations, there are two ODT signals internal to the DIMM 400. FIG. 4 shows these internal ODT signals between logic circuit 424 and the interface circuits 420 and 422 as ODT0i 444 and ODT1i 446. Depending on the flexibility of termination required, the size and complexity of the lookup table, and the type of signaling interface used, there may be any number of signals between logic circuit 424 and the interface circuits 420 and 422. For example, the number of internal ODT signals can be same, fewer, or greater than the number of ODT signals from the system/memory controller.


In some implementations, there are two interface circuits per slice of a DIMM 400. Consequently, an ECC DIMM with 72 bits would include 2×72/4=36 interface circuits. Similarly, a 64-bit DIMM would include 2×64/4=32 interface circuits.


In some implementations, interface circuit 420 and interface circuit 422 are combined into a single interface circuit, resulting in one interface circuit per slice. In these implementations, a DIMM would include 72/4=18 interface circuits. Other number (8, 9, 16, 18, etc.), arrangement, or integration of interface circuits may be used depending on a type of DIMM, cost, power, physical space on the DIMM, layout restrictions and other factors.


In some alternative implementations, logic circuit 424 is shared by all of the interface circuits on the DIMM 400. In these implementations, there would be one logic circuit per DIMM 400. In yet other implementations, a logic circuit or several logic circuits are positioned on each side of a DIMM 400 (or side of a PCB, board, card, package that is part of a module or DIMM, etc.) to simplify PCB routing. Any number of logic circuits may be used depending on the type of DIMM, the number of PCBs used, or other factors.


Other arrangements and levels of integration are also possible. There arrangements can depend, for example, on silicon die area and cost, package size and cost, board area, layout complexity as well as other engineering and economic factors. For example, all of the interface circuits and logic circuits can be integrated together into a single interface circuit. In another example, an interface circuit and/or logic circuit can be used on each side of a PCB or PCBs to improve board routing. In yet another example, some or all of the interface circuits and/or logic circuits can be integrated with one or more register circuits or any of the other DIMM components on an R-DIMM.



FIG. 5 is a block diagram illustrating a slice of an example 2-rank DIMM 500 with one interface circuit per slice. In some implementations, DIMM 500 includes on or more interface circuit as described above in FIGS. 1A-F, 3A-C, and 4. Additionally, elements within DIMM 500 can have attributes similar to corresponding elements in FIGS. 1A-F, 3A-C, and 4. For example, interface circuit 520 can include ODT resistor 560, which can be similar to ODT resister 366, discussed with respect to FIG. 3C. Likewise, DRAM devices 510, 512, 514, and 516 can include ODT resistors 580, which can be similar to ODT resistor 346 discussed with respect to FIG. 3B.


DIMM 500 has virtual rank 0 540, with DRAM devices 510 and 512 and virtual rank 1 542, with DRAM devices 514 and 516. Interface circuit 520 uses switches 562 and 564 to either couple or isolate data signals such as DQ0534 to the DRAM devices. Signals, for example, DQ0534 are received from the system through connectors e.g., finger 530. A register circuit 524 provides ODT control signals on bus 566 and switch control signals on bus 568 to interface circuit 520 and/or other interface circuits. Register circuit 524 can also provide standard JEDEC register functions. For example, register circuit 524 can receive inputs 572 that include command, address, control, and other signals from the system through connectors, e.g., finger 578. In some implementations, other signals are not directly connected to the register circuit 524, as shown in FIG. 5 by finger 576. The register circuit 524 can transmit command, address, control and other signals (possibly modified in timing and values) through bus 574 to the DRAM devices, for example, DRAM device 516. Not all the connections of command, address, control and other signals between DRAM devices are shown in FIG. 5.


The register circuit 524 can receive inputs ODT0548 and ODT1550 from a system (e.g., a memory controller of a host system). The register circuit 524 can also alter timing and behavior of ODT control before passing this information to interface circuit 520 through bus 566. The interface circuit 520 can then provide DIMM termination at DQ pin with ODT resistor 560. In some implementations, the timing of termination signals (including when and how they are applied, changed, removed) and determination of termination values are split between register circuit 524 and interface circuit 520.


Furthermore, in some implementations, the register circuit 524 also creates ODT control signals 570: R0_ODT0, R0_ODT1, R1_ODT0, R1_ODT1. These signals can be coupled to DRAM device signals 552, 554, 556 and 558. In some alternative implementations, (a) some or all of signals 552, 554, 556 and 558 may be hard-wired (to VSS, VDD or other potential); (b) some or all of signals 570 are created by interface circuit 520; (c) some or all of signals 570 are based on ODT0548 and ODT1550; (d) some or all of signals 570 are altered in timing and value from ODT0548 and ODT1550; or (e) any combination of implementations (a)-(d).



FIG. 6 illustrates an physical layout of an example printed circuit board (PCB) 600 of a DIMM with an interface circuit. In particular, PCB 600 includes an ECC R-DIMM with nine interface circuits and thirty six DRAMs 621. Additionally, FIG. 6 shows the two sides of a single DIMM 610. The DIMM 610 includes fingers 612 that permit the DIMM 610 to be electrically coupled to a system. Furthermore, as shown in FIG. 6, PCB 600 includes 36 DRAM (621-629, front/bottom; 631-639 front/top; 641-649 back/top; 651-659 back/bottom).



FIG. 6 also shows nine interface circuits 661-669, located in the front/middle. In addition, FIG. 6 shows one register circuit 670 located in front/center of the PCB 600. The register circuit 670 can have attributes comparable to those described with respect to interface circuit 150. DIMMs with a different number of DRAMs, interface circuits, or layouts can be used.


In some implementations, interface circuits can be located at the bottom of the DIMM PCB, so as to place termination electrically close to fingers 612. In some other implementations, DRAMs can be arranged on the PCB 600 with different orientations. For example, their longer sides can be arranged parallel to the longer edge of the PCB 600. DRAMs can also be arranged with their longer sides being perpendicular to the longer edge of the PCB 600. Alternatively, the DRAMs can be arranged such that some have long sides parallel to the longer edge of the PCB 600 and others have longer sides perpendicular to the longer edge of the PCB 600. Such arrangement may be useful to optimize high-speed PCB routing. In some other implementations, PCB 600 can include more than one register circuit. Additionally, PCB 600 can include more than one PCB sandwiched to form a DIMM. Furthermore, PCB 600 can include interface circuits placed on both side of the PCB.



FIG. 7 is a flowchart illustrating an example method 700 for providing termination resistance in a memory module. For convenience, the method 700 will be described with reference to an interface circuit that performs the method (e.g., interface circuit 150). It should be noted, however, that some or all steps of method 700 can be performed by other components within computer systems 100A-F.


The interface circuit communicates with memory circuits and with a memory controller (step 702). The memory circuits are, for example, dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM).


The interface circuit receives resistance-setting commands from the memory controller (step 704). The resistance-setting commands can be mode register set (MRS) commands directed to on-die termination (ODT) resistors within the memory circuits.


The interface circuit selects a resistance value based on the received resistance-setting commands (step 706). The interface circuit can select a resistance value from a look-up table. In addition, the selected resistance value can depend on the type of operation performed by the system. For example, the selected resistance value during read operations can be different from the selected resistance value during write operations. In some implementations, the selected resistance value is different from the values specified by the resistance-setting commands. For example, the selected resistance value can be different from a value prescribed by JEDEC standard for DDR3 DRAM.


The interface circuit terminates a transmission line with a resistor of the selected resistance value (step 708). The resistor can be an on-die termination (ODT) resistor. The transmission line can be, for example, a transmission line between the interface circuit and the memory controller.


While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. Therefore, the scope of the present invention is determined by the claims that follow. In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. It will be apparent, however, to one skilled in the art that implementations can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the disclosure.


In particular, one skilled in the art will recognize that other architectures can be used. Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.


It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.


An apparatus for performing the operations herein can be specially constructed for the required purposes, or it can comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.


The algorithms and modules presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct more specialized apparatuses to perform the method steps. The required structure for a variety of these systems will appear from the description. In addition, the present examples are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings as described herein. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, features, attributes, methodologies, and other aspects can be implemented as software, hardware, firmware or any combination of the three. Of course, wherever a component is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of skill in the art of computer programming. Additionally, the present description is in no way limited to implementation in any specific operating system or environment.


While this specification contains many specifics, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features specific to particular implementations of the subject matter. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.


Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.


The subject matter of this specification has been described in terms of particular embodiments, but other embodiments can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims.

Claims
  • 1. An apparatus for providing termination resistance in a memory module, the apparatus comprising: a plurality of memory circuits;an interface circuit operable to communicate with the plurality of memory circuits and to communicate with a memory controller; anda transmission line electrically coupling the interface circuit to the memory controller,wherein the interface circuit is operable to terminate the transmission line with a single termination resistance that is selected based on a plurality of resistance-setting commands received from the memory controller, and wherein the single termination resistance has a value that is different from values specified by the resistance-setting commands received from the memory controller.
  • 2. The apparatus of claim 1, wherein the single termination resistance is provided by an on-die termination (ODT) resistor.
  • 3. The apparatus of claim 1, wherein the interface circuit selects a value of the single termination resistance from a look-up table.
  • 4. The apparatus of claim 1, wherein the plurality of resistance-setting commands received from the memory controller comprises a first mode register set (MRS) command and a second MRS command.
  • 5. The apparatus of claim 1, wherein a value of the single termination resistance during read operations is different from a value of the single termination resistance during write operations.
  • 6. The apparatus of claim 1, wherein the plurality of memory circuits is a plurality of dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM).
  • 7. The apparatus of claim 1, further comprising a resistor operable to provide the single termination resistance value, wherein the resistor is activated in response to a resistance-setting command issued by the interface circuit.
  • 8. A method for providing termination resistance in a memory module, the method comprising: receiving a plurality of resistance-setting commands from a memory controller at an interface circuit, wherein the interface circuit is operable to communicate with a plurality of memory circuits and with the memory controller;selecting a resistance value based on the received plurality of resistance-setting commands; andterminating a transmission line between the interface circuit and the memory controller with a resistor of the selected resistance value, wherein the selected resistance value is different from the values specified by the resistance-setting commands.
  • 9. The method of claim 8, wherein the selected resistance value is a value for an on-die termination (ODT) resistor.
  • 10. The method of claim 8, wherein the selected resistance value is selected from a look-up table.
  • 11. The method of claim 8, wherein the selected resistance value during read operations is different from the selected resistance value during write operations.
  • 12. The method of claim 8, wherein the plurality of memory circuits is a plurality of dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM).
  • 13. The method of claim 8, wherein the plurality of resistance-setting commands is a plurality of mode register set (MRS) commands.
  • 14. An apparatus for providing termination resistance in a memory module, the apparatus comprising: a first memory circuit having a first termination resistor with a selectable value;a second memory circuit having a second termination resistor with a selectable value; andan interface circuit operable to communicate with the first and the second memory circuits and a memory controller, wherein the interface circuit is operable to select a single value for the first and the second termination resistors that is chosen based on a plurality of resistance-setting commands received from the memory controller, wherein the single value selected by the interface circuit for the first and the second termination resistors is different from values indicated by the plurality of resistance-setting commands received from the memory controller.
  • 15. The apparatus of claim 14, wherein the first and the second termination resistors are on-die termination (ODT) resistors.
  • 16. The apparatus of claim 14, wherein the interface circuit selects a single value for the first and the second termination resistors from a look-up table.
  • 17. The apparatus of claim 14, wherein the plurality of resistance-setting commands received from the memory controller comprises a first mode register set (MRS) command and a second MRS command.
  • 18. The apparatus of claim 14, wherein values of the first and the second termination resistors during read operations are different from values of the first and the second termination resistors during write operations.
  • 19. The apparatus of claim 14, wherein the first and the second memory circuits are dynamic random access memory (DRAM) integrated circuits in a dual in-line memory module (DIMM).
  • 20. The apparatus of claim 14, wherein the first and second terminations resistors are activated in response to one or more resistance-setting commands issued by the interface circuit.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/185,585, filed on Jun. 9, 2009, which is hereby incorporated by reference in its entirety.

US Referenced Citations (776)
Number Name Date Kind
3800292 Curley et al. Mar 1974 A
4069452 Conway et al. Jan 1978 A
4323965 Johnson et al. Apr 1982 A
4334307 Bourgeois et al. Jun 1982 A
4345319 Bernardini et al. Aug 1982 A
4392212 Miyasaka et al. Jul 1983 A
4525921 Carson et al. Jul 1985 A
4566082 Anderson Jan 1986 A
4592019 Huang et al. May 1986 A
4646128 Carson et al. Feb 1987 A
4698748 Juzswik et al. Oct 1987 A
4706166 Go Nov 1987 A
4710903 Hereth et al. Dec 1987 A
4764846 Go Aug 1988 A
4780843 Tietjen Oct 1988 A
4794597 Ooba et al. Dec 1988 A
4796232 House Jan 1989 A
4841440 Yonezu et al. Jun 1989 A
4862347 Rudy Aug 1989 A
4884237 Mueller et al. Nov 1989 A
4887240 Garverick et al. Dec 1989 A
4888687 Allison et al. Dec 1989 A
4899107 Corbett et al. Feb 1990 A
4912678 Mashiko Mar 1990 A
4922451 Lo et al. May 1990 A
4935734 Austin Jun 1990 A
4937791 Steele et al. Jun 1990 A
4956694 Eide Sep 1990 A
4982265 Watanabe et al. Jan 1991 A
4983533 Go Jan 1991 A
5025364 Zellmer Jun 1991 A
5072424 Brent et al. Dec 1991 A
5083266 Watanabe Jan 1992 A
5104820 Go et al. Apr 1992 A
5220672 Nakao et al. Jun 1993 A
5241266 Ahmad et al. Aug 1993 A
5252807 Chizinsky Oct 1993 A
5257233 Schaefer Oct 1993 A
5278796 Tillinghast et al. Jan 1994 A
5282177 McLaury Jan 1994 A
5332922 Oguchi et al. Jul 1994 A
5347428 Carson et al. Sep 1994 A
5384745 Konishi et al. Jan 1995 A
5388265 Volk Feb 1995 A
5390334 Harrison Feb 1995 A
5408190 Wood et al. Apr 1995 A
5432729 Carson et al. Jul 1995 A
5448511 Paurus et al. Sep 1995 A
5467455 Gay et al. Nov 1995 A
5483497 Mochizuki et al. Jan 1996 A
5498886 Hsu et al. Mar 1996 A
5502333 Bertin et al. Mar 1996 A
5502667 Bertin et al. Mar 1996 A
5513135 Dell et al. Apr 1996 A
5513339 Agrawal et al. Apr 1996 A
5519832 Warchol May 1996 A
5526320 Zagar et al. Jun 1996 A
5530836 Busch et al. Jun 1996 A
5550781 Sugawara et al. Aug 1996 A
5559990 Cheng et al. Sep 1996 A
5561622 Bertin et al. Oct 1996 A
5563086 Bertin et al. Oct 1996 A
5566344 Hall et al. Oct 1996 A
5581498 Ludwig et al. Dec 1996 A
5581779 Hall et al. Dec 1996 A
5590071 Kolor et al. Dec 1996 A
5598376 Merritt et al. Jan 1997 A
5604714 Manning et al. Feb 1997 A
5606710 Hall et al. Feb 1997 A
5608262 Degani et al. Mar 1997 A
5610864 Manning Mar 1997 A
5623686 Hall et al. Apr 1997 A
5627791 Wright et al. May 1997 A
5640337 Huang et al. Jun 1997 A
5640364 Merritt et al. Jun 1997 A
5652724 Manning Jul 1997 A
5654204 Anderson Aug 1997 A
5661677 Rondeau et al. Aug 1997 A
5661695 Zagar et al. Aug 1997 A
5668773 Zagar et al. Sep 1997 A
5675549 Ong et al. Oct 1997 A
5680342 Frankeny Oct 1997 A
5682354 Manning Oct 1997 A
5692121 Bozso et al. Nov 1997 A
5692202 Kardach et al. Nov 1997 A
5696732 Zagar et al. Dec 1997 A
5702984 Bertin et al. Dec 1997 A
5703813 Manning et al. Dec 1997 A
5706247 Merritt et al. Jan 1998 A
RE35733 Hernandez et al. Feb 1998 E
5717654 Manning Feb 1998 A
5721859 Manning Feb 1998 A
5724288 Cloud et al. Mar 1998 A
5729503 Manning Mar 1998 A
5729504 Cowles Mar 1998 A
5742792 Yanai et al. Apr 1998 A
5748914 Barth et al. May 1998 A
5752045 Chen May 1998 A
5757703 Merritt et al. May 1998 A
5761703 Bolyn Jun 1998 A
5781766 Davis Jul 1998 A
5787457 Miller et al. Jul 1998 A
5798961 Heyden et al. Aug 1998 A
5802010 Zagar et al. Sep 1998 A
5802395 Connolly et al. Sep 1998 A
5802555 Shigeeda Sep 1998 A
5812488 Zagar et al. Sep 1998 A
5831833 Shirakawa et al. Nov 1998 A
5831931 Manning Nov 1998 A
5831932 Merritt et al. Nov 1998 A
5834838 Anderson Nov 1998 A
5835435 Bogin et al. Nov 1998 A
5838165 Chatter Nov 1998 A
5838177 Keeth Nov 1998 A
5841580 Farmwald et al. Nov 1998 A
5843799 Hsu et al. Dec 1998 A
5843807 Burns Dec 1998 A
5845108 Yoo et al. Dec 1998 A
5850368 Ong et al. Dec 1998 A
5859792 Rondeau et al. Jan 1999 A
5860106 Domen et al. Jan 1999 A
5870347 Keeth et al. Feb 1999 A
5870350 Bertin Feb 1999 A
5872907 Griess et al. Feb 1999 A
5875142 Chevallier Feb 1999 A
5878279 Athenes Mar 1999 A
5884088 Kardach et al. Mar 1999 A
5901105 Ong et al. May 1999 A
5903500 Tsang et al. May 1999 A
5905688 Park May 1999 A
5907512 Parkinson et al. May 1999 A
5915105 Farmwald et al. Jun 1999 A
5915167 Leedy Jun 1999 A
5917758 Keeth Jun 1999 A
5923611 Ryan Jul 1999 A
5924111 Huang et al. Jul 1999 A
5926435 Park et al. Jul 1999 A
5929650 Pappert et al. Jul 1999 A
5943254 Bakeman, Jr. et al. Aug 1999 A
5946265 Cowles Aug 1999 A
5949254 Keeth Sep 1999 A
5953215 Karabatsos Sep 1999 A
5953263 Farmwald et al. Sep 1999 A
5954804 Farmwald et al. Sep 1999 A
5956233 Yew et al. Sep 1999 A
5963429 Chen Oct 1999 A
5963463 Rondeau et al. Oct 1999 A
5963464 Dell et al. Oct 1999 A
5963504 Manning Oct 1999 A
5966724 Ryan Oct 1999 A
5966727 Nishino Oct 1999 A
5969996 Muranaka et al. Oct 1999 A
5973392 Senba et al. Oct 1999 A
5995424 Lawrence et al. Nov 1999 A
5995443 Farmwald et al. Nov 1999 A
6001671 Fjelstad Dec 1999 A
6002613 Cloud et al. Dec 1999 A
6002627 Chevallier Dec 1999 A
6014339 Kobayashi et al. Jan 2000 A
6016282 Keeth Jan 2000 A
6026050 Baker et al. Feb 2000 A
6029250 Keeth Feb 2000 A
6032214 Farmwald et al. Feb 2000 A
6032215 Farmwald et al. Feb 2000 A
6034916 Lee Mar 2000 A
6034918 Farmwald et al. Mar 2000 A
6035365 Farmwald et al. Mar 2000 A
6038195 Farmwald et al. Mar 2000 A
6038673 Benn et al. Mar 2000 A
6044032 Li Mar 2000 A
6047073 Norris et al. Apr 2000 A
6047344 Kawasumi et al. Apr 2000 A
6053948 Vaidyanathan et al. Apr 2000 A
6069504 Keeth May 2000 A
6070217 Connolly et al. May 2000 A
6073223 McAllister et al. Jun 2000 A
6075730 Barth et al. Jun 2000 A
6075744 Tsern et al. Jun 2000 A
6078546 Lee Jun 2000 A
6079025 Fung Jun 2000 A
6084434 Keeth Jul 2000 A
6088290 Ohtake et al. Jul 2000 A
6091251 Wood et al. Jul 2000 A
RE36839 Simmons et al. Aug 2000 E
6101152 Farmwald et al. Aug 2000 A
6101564 Athenes et al. Aug 2000 A
6101612 Jeddeloh Aug 2000 A
6108795 Jeddeloh Aug 2000 A
6111812 Gans et al. Aug 2000 A
6134638 Olarig et al. Oct 2000 A
6154370 Degani et al. Nov 2000 A
6166991 Phelan Dec 2000 A
6182184 Farmwald et al. Jan 2001 B1
6199151 Williams et al. Mar 2001 B1
6208168 Rhee Mar 2001 B1
6216246 Shau Apr 2001 B1
6222739 Bhakta et al. Apr 2001 B1
6226709 Goodwin et al. May 2001 B1
6233192 Tanaka May 2001 B1
6233650 Johnson et al. May 2001 B1
6240048 Matsubara May 2001 B1
6243282 Rondeau et al. Jun 2001 B1
6252807 Suzuki et al. Jun 2001 B1
6260097 Farmwald et al. Jul 2001 B1
6260154 Jeddeloh Jul 2001 B1
6262938 Lee et al. Jul 2001 B1
6266285 Farmwald et al. Jul 2001 B1
6266292 Tsern et al. Jul 2001 B1
6274395 Weber Aug 2001 B1
6279069 Robinson et al. Aug 2001 B1
6295572 Wu Sep 2001 B1
6298426 Ajanovic Oct 2001 B1
6304511 Gans et al. Oct 2001 B1
6307769 Nuxoll et al. Oct 2001 B1
6314051 Farmwald et al. Nov 2001 B1
6317352 Halbert et al. Nov 2001 B1
6317381 Gans et al. Nov 2001 B1
6324120 Farmwald et al. Nov 2001 B2
6326810 Keeth Dec 2001 B1
6327664 Dell et al. Dec 2001 B1
6330683 Jeddeloh Dec 2001 B1
6336174 Li et al. Jan 2002 B1
6338108 Motomura Jan 2002 B1
6338113 Kubo et al. Jan 2002 B1
6341347 Joy et al. Jan 2002 B1
6343042 Tsern et al. Jan 2002 B1
6353561 Funyu et al. Mar 2002 B1
6356105 Volk Mar 2002 B1
6356500 Cloud et al. Mar 2002 B1
6362656 Rhee Mar 2002 B2
6363031 Phelan Mar 2002 B2
6378020 Farmwald et al. Apr 2002 B2
6381188 Choi et al. Apr 2002 B1
6381668 Lunteren Apr 2002 B1
6389514 Rokicki May 2002 B1
6392304 Butler May 2002 B1
6414868 Wong et al. Jul 2002 B1
6418034 Weber et al. Jul 2002 B1
6421754 Kau et al. Jul 2002 B1
6424532 Kawamura Jul 2002 B2
6426916 Farmwald et al. Jul 2002 B2
6429029 Eldridge et al. Aug 2002 B1
6430103 Nakayama et al. Aug 2002 B2
6437600 Keeth Aug 2002 B1
6438057 Ruckerbauer Aug 2002 B1
6442698 Nizar Aug 2002 B2
6445591 Kwong Sep 2002 B1
6452826 Kim et al. Sep 2002 B1
6452863 Farmwald et al. Sep 2002 B2
6453400 Maesako et al. Sep 2002 B1
6453402 Jeddeloh Sep 2002 B1
6453434 Delp et al. Sep 2002 B2
6455348 Yamaguchi Sep 2002 B1
6457095 Volk Sep 2002 B1
6459651 Lee et al. Oct 2002 B1
6473831 Schade Oct 2002 B1
6476476 Glenn Nov 2002 B1
6480929 Gauthier et al. Nov 2002 B1
6487102 Halbert et al. Nov 2002 B1
6489669 Shimada et al. Dec 2002 B2
6490161 Johnson Dec 2002 B1
6493789 Ware et al. Dec 2002 B2
6496440 Manning Dec 2002 B2
6496897 Ware et al. Dec 2002 B2
6498766 Lee et al. Dec 2002 B2
6510097 Fukuyama Jan 2003 B2
6510503 Gillingham et al. Jan 2003 B2
6512392 Fleury et al. Jan 2003 B2
6521984 Matsuura Feb 2003 B2
6526471 Shimomura et al. Feb 2003 B1
6526473 Kim Feb 2003 B1
6526484 Stacovsky et al. Feb 2003 B1
6545895 Li et al. Apr 2003 B1
6546446 Farmwald et al. Apr 2003 B2
6553450 Dodd et al. Apr 2003 B1
6560158 Choi et al. May 2003 B2
6563337 Dour May 2003 B2
6563759 Yahata et al. May 2003 B2
6564281 Farmwald et al. May 2003 B2
6564285 Mills et al. May 2003 B1
6574150 Suyama et al. Jun 2003 B2
6584037 Farmwald et al. Jun 2003 B2
6587912 Leddige et al. Jul 2003 B2
6590822 Hwang et al. Jul 2003 B2
6594770 Sato et al. Jul 2003 B1
6597616 Tsern et al. Jul 2003 B2
6597617 Ooishi et al. Jul 2003 B2
6614700 Dietrich et al. Sep 2003 B2
6618267 Dalal et al. Sep 2003 B1
6618791 Dodd et al. Sep 2003 B1
6621760 Ahmad et al. Sep 2003 B1
6630729 Huang Oct 2003 B2
6631086 Bill et al. Oct 2003 B1
6639820 Khandekar et al. Oct 2003 B1
6646939 Kwak Nov 2003 B2
6650588 Yamagata Nov 2003 B2
6650594 Lee et al. Nov 2003 B1
6657634 Sinclair et al. Dec 2003 B1
6657918 Foss et al. Dec 2003 B2
6657919 Foss et al. Dec 2003 B2
6658016 Dai et al. Dec 2003 B1
6658530 Robertson et al. Dec 2003 B1
6659512 Harper et al. Dec 2003 B1
6664625 Hiruma Dec 2003 B2
6665224 Lehmann et al. Dec 2003 B1
6665227 Fetzer Dec 2003 B2
6668242 Reynov et al. Dec 2003 B1
6674154 Minamio et al. Jan 2004 B2
6683372 Wong et al. Jan 2004 B1
6684292 Piccirillo et al. Jan 2004 B2
6690191 Wu et al. Feb 2004 B2
6697295 Farmwald et al. Feb 2004 B2
6701446 Tsern et al. Mar 2004 B2
6705877 Li et al. Mar 2004 B1
6708144 Merryman et al. Mar 2004 B1
6710430 Minamio et al. Mar 2004 B2
6711043 Friedman et al. Mar 2004 B2
6713856 Tsai et al. Mar 2004 B2
6714891 Dendinger Mar 2004 B2
6724684 Kim Apr 2004 B2
6731527 Brown May 2004 B2
6742098 Halbert et al. May 2004 B1
6744687 Koo et al. Jun 2004 B2
6747887 Halbert et al. Jun 2004 B2
6751113 Bhakta et al. Jun 2004 B2
6751696 Farmwald et al. Jun 2004 B2
6754129 Khatri et al. Jun 2004 B2
6754132 Kyung Jun 2004 B2
6757751 Gene Jun 2004 B1
6762948 Kyun et al. Jul 2004 B2
6765812 Anderson Jul 2004 B2
6766469 Larson et al. Jul 2004 B2
6771526 LaBerge Aug 2004 B2
6772359 Kwak et al. Aug 2004 B2
6779097 Gillingham et al. Aug 2004 B2
6785767 Coulson Aug 2004 B2
6791877 Miura et al. Sep 2004 B2
6795899 Dodd et al. Sep 2004 B2
6799241 Kahn et al. Sep 2004 B2
6801989 Johnson et al. Oct 2004 B2
6807598 Farmwald et al. Oct 2004 B2
6807655 Rehani et al. Oct 2004 B1
6816991 Sanghani Nov 2004 B2
6819602 Seo et al. Nov 2004 B2
6819617 Hwang et al. Nov 2004 B2
6820163 McCall et al. Nov 2004 B1
6820169 Wilcox et al. Nov 2004 B2
6826104 Kawaguchi et al. Nov 2004 B2
6839290 Ahmad et al. Jan 2005 B2
6844754 Yamagata Jan 2005 B2
6845027 Mayer et al. Jan 2005 B2
6845055 Koga et al. Jan 2005 B1
6847582 Pan Jan 2005 B2
6850449 Takahashi Feb 2005 B2
6862202 Schaefer Mar 2005 B2
6862249 Kyung Mar 2005 B2
6862653 Dodd et al. Mar 2005 B1
6873534 Bhakta et al. Mar 2005 B2
6878570 Lyu et al. Apr 2005 B2
6894933 Kuzmenka et al. May 2005 B2
6898683 Nakamura May 2005 B2
6908314 Brown Jun 2005 B2
6912778 Ahn et al. Jul 2005 B2
6914786 Paulsen et al. Jul 2005 B1
6917219 New Jul 2005 B2
6922371 Takahashi et al. Jul 2005 B2
6930900 Bhakta et al. Aug 2005 B2
6930903 Bhakta et al. Aug 2005 B2
6938119 Kohn et al. Aug 2005 B2
6943450 Fee et al. Sep 2005 B2
6944748 Sanches et al. Sep 2005 B2
6947341 Stubbs et al. Sep 2005 B2
6951982 Chye et al. Oct 2005 B2
6952794 Lu Oct 2005 B2
6961281 Wong et al. Nov 2005 B2
6968416 Moy Nov 2005 B2
6968419 Holman Nov 2005 B1
6970968 Holman Nov 2005 B1
6980021 Srivastava et al. Dec 2005 B1
6986118 Dickman Jan 2006 B2
6992501 Rapport Jan 2006 B2
6992950 Foss et al. Jan 2006 B2
7000062 Perego et al. Feb 2006 B2
7003618 Perego et al. Feb 2006 B2
7003639 Tsern et al. Feb 2006 B2
7007095 Chen et al. Feb 2006 B2
7007175 Chang et al. Feb 2006 B2
7010642 Perego et al. Mar 2006 B2
7010736 Teh et al. Mar 2006 B1
7024518 Halbert et al. Apr 2006 B2
7026708 Cady et al. Apr 2006 B2
7028215 Depew et al. Apr 2006 B2
7028234 Huckaby et al. Apr 2006 B2
7033861 Partridge et al. Apr 2006 B1
7035150 Streif et al. Apr 2006 B2
7043599 Ware et al. May 2006 B1
7045396 Crowley et al. May 2006 B2
7045901 Lin et al. May 2006 B2
7046538 Kinsley et al. May 2006 B2
7053470 Sellers et al. May 2006 B1
7053478 Roper et al. May 2006 B2
7058776 Lee Jun 2006 B2
7058863 Kouchi et al. Jun 2006 B2
7061784 Jakobs et al. Jun 2006 B2
7061823 Faue et al. Jun 2006 B2
7066741 Burns et al. Jun 2006 B2
7075175 Kazi et al. Jul 2006 B2
7079396 Gates et al. Jul 2006 B2
7079441 Partsch et al. Jul 2006 B1
7079446 Murtagh et al. Jul 2006 B2
7085152 Ellis et al. Aug 2006 B2
7085941 Li Aug 2006 B2
7089438 Raad Aug 2006 B2
7093101 Aasheim et al. Aug 2006 B2
7103730 Saxena et al. Sep 2006 B2
7119428 Tanie et al. Oct 2006 B2
7120727 Lee et al. Oct 2006 B2
7126399 Lee Oct 2006 B1
7127567 Ramakrishnan et al. Oct 2006 B2
7133960 Thompson et al. Nov 2006 B1
7136978 Miura et al. Nov 2006 B2
7149145 Kim et al. Dec 2006 B2
7149824 Johnson Dec 2006 B2
7173863 Conley et al. Feb 2007 B2
7200021 Raghuram Apr 2007 B2
7205789 Karabatsos Apr 2007 B1
7210059 Jeddoloh Apr 2007 B2
7215561 Park et al. May 2007 B2
7218566 Totolos, Jr. et al. May 2007 B1
7224595 Dreps et al. May 2007 B2
7228264 Barrenscheen et al. Jun 2007 B2
7231562 Ohlhoff et al. Jun 2007 B2
7233541 Yamamoto et al. Jun 2007 B2
7234081 Nguyen et al. Jun 2007 B2
7243185 See et al. Jul 2007 B2
7245541 Janzen Jul 2007 B2
7254036 Pauley et al. Aug 2007 B2
7266639 Raghuram Sep 2007 B2
7269042 Kinsley et al. Sep 2007 B2
7269708 Ware Sep 2007 B2
7274583 Park et al. Sep 2007 B2
7277333 Schaefer Oct 2007 B2
7286436 Bhakta et al. Oct 2007 B2
7289386 Bhakta et al. Oct 2007 B2
7296754 Nishizawa et al. Nov 2007 B2
7299330 Gillingham et al. Nov 2007 B2
7302598 Suzuki et al. Nov 2007 B2
7307863 Yen et al. Dec 2007 B2
7317250 Koh et al. Jan 2008 B2
7363422 Perego et al. Apr 2008 B2
7366947 Gower et al. Apr 2008 B2
7379316 Rajan May 2008 B2
7386656 Rajan et al. Jun 2008 B2
7392338 Rajan et al. Jun 2008 B2
7408393 Jain et al. Aug 2008 B1
7409492 Tanaka et al. Aug 2008 B2
7414917 Ruckerbauer et al. Aug 2008 B2
7428644 Jeddeloh et al. Sep 2008 B2
7437579 Jeddeloh et al. Oct 2008 B2
7441064 Gaskins Oct 2008 B2
7457122 Lai et al. Nov 2008 B2
7464225 Tsern Dec 2008 B2
7472220 Rajan et al. Dec 2008 B2
7474576 Co et al. Jan 2009 B2
7480147 Hoss et al. Jan 2009 B2
7480774 Ellis et al. Jan 2009 B2
7496777 Kapil Feb 2009 B2
7515453 Rajan Apr 2009 B2
7532537 Solomon et al. May 2009 B2
7539800 Dell et al. May 2009 B2
7573136 Jiang et al. Aug 2009 B2
7580312 Rajan et al. Aug 2009 B2
7581121 Barth et al. Aug 2009 B2
7581127 Rajan et al. Aug 2009 B2
7590796 Rajan et al. Sep 2009 B2
7599205 Rajan Oct 2009 B2
7606245 Ma et al. Oct 2009 B2
7609567 Rajan et al. Oct 2009 B2
7613880 Miura et al. Nov 2009 B2
7619912 Bhakta et al. Nov 2009 B2
7724589 Rajan et al. May 2010 B2
7730338 Rajan et al. Jun 2010 B2
7761724 Rajan et al. Jul 2010 B2
20010000822 Dell et al. May 2001 A1
20010003198 Wu Jun 2001 A1
20010011322 Stolt et al. Aug 2001 A1
20010021106 Weber et al. Sep 2001 A1
20010021137 Kai et al. Sep 2001 A1
20010046129 Broglia et al. Nov 2001 A1
20010046163 Yanagawa Nov 2001 A1
20020002662 Olarig et al. Jan 2002 A1
20020004897 Kao et al. Jan 2002 A1
20020015340 Batinovich Feb 2002 A1
20020019961 Blodgett Feb 2002 A1
20020034068 Weber et al. Mar 2002 A1
20020038405 Leddige et al. Mar 2002 A1
20020041507 Woo et al. Apr 2002 A1
20020051398 Mizugaki May 2002 A1
20020060945 Ikeda May 2002 A1
20020064073 Chien May 2002 A1
20020064083 Ryu et al. May 2002 A1
20020089831 Forthun Jul 2002 A1
20020089970 Asada et al. Jul 2002 A1
20020094671 Distefano et al. Jul 2002 A1
20020121650 Minamio et al. Sep 2002 A1
20020121670 Minamio et al. Sep 2002 A1
20020124195 Nizar Sep 2002 A1
20020129204 Leighnor et al. Sep 2002 A1
20020145900 Schaefer Oct 2002 A1
20020165706 Raynham Nov 2002 A1
20020167092 Fee et al. Nov 2002 A1
20020172024 Hui et al. Nov 2002 A1
20020174274 Wu et al. Nov 2002 A1
20020184438 Usui Dec 2002 A1
20030002262 Benisek et al. Jan 2003 A1
20030011993 Summers et al. Jan 2003 A1
20030016550 Yoo et al. Jan 2003 A1
20030021175 Tae Kwak Jan 2003 A1
20030026155 Yamagata Feb 2003 A1
20030026159 Frankowsky et al. Feb 2003 A1
20030035312 Halbert et al. Feb 2003 A1
20030039158 Horiguchi et al. Feb 2003 A1
20030041295 Hou et al. Feb 2003 A1
20030061458 Wilcox et al. Mar 2003 A1
20030061459 Aboulenein et al. Mar 2003 A1
20030093614 Kohn et al. May 2003 A1
20030101392 Lee May 2003 A1
20030105932 David et al. Jun 2003 A1
20030117875 Lee et al. Jun 2003 A1
20030123389 Russell et al. Jul 2003 A1
20030126338 Dodd et al. Jul 2003 A1
20030127737 Takahashi Jul 2003 A1
20030131160 Hampel et al. Jul 2003 A1
20030145163 Seo et al. Jul 2003 A1
20030158995 Lee et al. Aug 2003 A1
20030164539 Yau Sep 2003 A1
20030164543 Kheng Lee Sep 2003 A1
20030182513 Dodd et al. Sep 2003 A1
20030183934 Barrett Oct 2003 A1
20030189868 Riesenman et al. Oct 2003 A1
20030189870 Wilcox Oct 2003 A1
20030191888 Klein Oct 2003 A1
20030191915 Saxena et al. Oct 2003 A1
20030200382 Wells et al. Oct 2003 A1
20030200474 Li Oct 2003 A1
20030205802 Segaram et al. Nov 2003 A1
20030206476 Joo Nov 2003 A1
20030217303 Chua-Eoan et al. Nov 2003 A1
20030223290 Park et al. Dec 2003 A1
20030227798 Pax Dec 2003 A1
20030229821 Ma Dec 2003 A1
20030230801 Jiang et al. Dec 2003 A1
20030231540 Lazar et al. Dec 2003 A1
20030231542 Zaharinova-Papazova et al. Dec 2003 A1
20030234664 Yamagata Dec 2003 A1
20040016994 Huang Jan 2004 A1
20040027902 Ooishi et al. Feb 2004 A1
20040034732 Valin et al. Feb 2004 A1
20040034755 LaBerge et al. Feb 2004 A1
20040037133 Park et al. Feb 2004 A1
20040044808 Salmon et al. Mar 2004 A1
20040047228 Chen Mar 2004 A1
20040057317 Schaefer Mar 2004 A1
20040064647 DeWhitt et al. Apr 2004 A1
20040064767 Huckaby et al. Apr 2004 A1
20040083324 Rabinovitz et al. Apr 2004 A1
20040088475 Streif et al. May 2004 A1
20040100837 Lee May 2004 A1
20040117723 Foss Jun 2004 A1
20040123173 Emberling et al. Jun 2004 A1
20040125635 Kuzmenka Jul 2004 A1
20040133736 Kyung Jul 2004 A1
20040139359 Samson et al. Jul 2004 A1
20040145963 Byon Jul 2004 A1
20040151038 Ruckerbauer et al. Aug 2004 A1
20040174765 Seo et al. Sep 2004 A1
20040177079 Gluhovsky et al. Sep 2004 A1
20040178824 Pan Sep 2004 A1
20040184324 Pax Sep 2004 A1
20040186956 Perego et al. Sep 2004 A1
20040188704 Halbert et al. Sep 2004 A1
20040196732 Lee Oct 2004 A1
20040205433 Gower et al. Oct 2004 A1
20040208173 Di Gregorio Oct 2004 A1
20040225858 Brueggen Nov 2004 A1
20040228166 Braun et al. Nov 2004 A1
20040228196 Kwak et al. Nov 2004 A1
20040228203 Koo Nov 2004 A1
20040230932 Dickmann Nov 2004 A1
20040236877 Burton Nov 2004 A1
20040250989 Im et al. Dec 2004 A1
20040256638 Perego et al. Dec 2004 A1
20040257847 Matsui et al. Dec 2004 A1
20040260957 Jeddeloh et al. Dec 2004 A1
20040264255 Royer Dec 2004 A1
20040268161 Ross Dec 2004 A1
20050018495 Bhakta et al. Jan 2005 A1
20050021874 Georgiou et al. Jan 2005 A1
20050024963 Jakobs et al. Feb 2005 A1
20050027928 Avraham et al. Feb 2005 A1
20050028038 Pomaranski et al. Feb 2005 A1
20050034004 Bunker et al. Feb 2005 A1
20050036350 So et al. Feb 2005 A1
20050041504 Perego et al. Feb 2005 A1
20050044303 Perego et al. Feb 2005 A1
20050044305 Jakobs et al. Feb 2005 A1
20050047192 Matsui et al. Mar 2005 A1
20050071543 Ellis et al. Mar 2005 A1
20050078532 Ruckerbauer et al. Apr 2005 A1
20050081085 Ellis et al. Apr 2005 A1
20050099834 Funaba et al. May 2005 A1
20050102590 Norris et al. May 2005 A1
20050105318 Funaba et al. May 2005 A1
20050108460 David May 2005 A1
20050127531 Tay et al. Jun 2005 A1
20050132158 Hampel et al. Jun 2005 A1
20050135176 Ramakrishnan et al. Jun 2005 A1
20050138267 Bains et al. Jun 2005 A1
20050138304 Ramakrishnan et al. Jun 2005 A1
20050139977 Nishio et al. Jun 2005 A1
20050141199 Chiou et al. Jun 2005 A1
20050149662 Perego et al. Jul 2005 A1
20050152212 Yang et al. Jul 2005 A1
20050156934 Perego et al. Jul 2005 A1
20050166026 Ware et al. Jul 2005 A1
20050193163 Perego et al. Sep 2005 A1
20050194676 Fukuda et al. Sep 2005 A1
20050194991 Dour et al. Sep 2005 A1
20050195629 Leddige et al. Sep 2005 A1
20050201063 Lee et al. Sep 2005 A1
20050204111 Natarajan Sep 2005 A1
20050207255 Perego et al. Sep 2005 A1
20050210196 perego et al. Sep 2005 A1
20050223179 Perego et al. Oct 2005 A1
20050224948 Lee et al. Oct 2005 A1
20050232049 Park Oct 2005 A1
20050235119 Sechrest et al. Oct 2005 A1
20050235131 Ware Oct 2005 A1
20050237838 Kwak et al. Oct 2005 A1
20050243635 Schaefer Nov 2005 A1
20050249011 Maeda Nov 2005 A1
20050259504 Murtugh et al. Nov 2005 A1
20050263312 Bolken et al. Dec 2005 A1
20050265506 Foss et al. Dec 2005 A1
20050269715 Yoo Dec 2005 A1
20050278474 Perersen et al. Dec 2005 A1
20050281096 Bhakta et al. Dec 2005 A1
20050281123 Bell et al. Dec 2005 A1
20050283572 Ishihara Dec 2005 A1
20050285174 Saito et al. Dec 2005 A1
20050289292 Morrow et al. Dec 2005 A1
20050289317 Liou et al. Dec 2005 A1
20060002201 Janzen Jan 2006 A1
20060010339 Klein Jan 2006 A1
20060026484 Hollums Feb 2006 A1
20060038597 Becker et al. Feb 2006 A1
20060039204 Cornelius Feb 2006 A1
20060039205 Cornelius Feb 2006 A1
20060041711 Miura et al. Feb 2006 A1
20060041730 Larson Feb 2006 A1
20060044909 Kinsley et al. Mar 2006 A1
20060044913 Klein et al. Mar 2006 A1
20060049502 Goodwin et al. Mar 2006 A1
20060050574 Streif et al. Mar 2006 A1
20060056244 Ware Mar 2006 A1
20060062047 Bhakta et al. Mar 2006 A1
20060067141 Perego et al. Mar 2006 A1
20060085616 Zeighami et al. Apr 2006 A1
20060087900 Bucksch et al. Apr 2006 A1
20060090031 Kirshenbaum et al. Apr 2006 A1
20060090054 Choi et al. Apr 2006 A1
20060106951 Bains May 2006 A1
20060112214 Yeh May 2006 A1
20060112219 Chawla et al. May 2006 A1
20060117152 Amidi et al. Jun 2006 A1
20060117160 Jackson et al. Jun 2006 A1
20060118933 Haba Jun 2006 A1
20060120193 Casper Jun 2006 A1
20060123265 Ruckerbauer et al. Jun 2006 A1
20060126369 Raghuram Jun 2006 A1
20060129712 Raghuram Jun 2006 A1
20060129740 Ruckerbauer et al. Jun 2006 A1
20060129755 Raghuram Jun 2006 A1
20060133173 Jain et al. Jun 2006 A1
20060136791 Nierle Jun 2006 A1
20060149982 Vogt Jul 2006 A1
20060174082 Bellows et al. Aug 2006 A1
20060176744 Stave Aug 2006 A1
20060179333 Brittain et al. Aug 2006 A1
20060179334 Brittain et al. Aug 2006 A1
20060180926 Mullen et al. Aug 2006 A1
20060181953 Rotenberg et al. Aug 2006 A1
20060195631 Rajamani Aug 2006 A1
20060198178 Kinsley et al. Sep 2006 A1
20060203590 Mori et al. Sep 2006 A1
20060206738 Jeddeloh et al. Sep 2006 A1
20060233012 Sekiguchi et al. Oct 2006 A1
20060236165 Cepulis et al. Oct 2006 A1
20060236201 Gower et al. Oct 2006 A1
20060248261 Jacob et al. Nov 2006 A1
20060248387 Nicholson et al. Nov 2006 A1
20060262586 Solomon et al. Nov 2006 A1
20060294295 Fukuzo Dec 2006 A1
20070005998 Jain et al. Jan 2007 A1
20070050530 Rajan Mar 2007 A1
20070058471 Rajan et al. Mar 2007 A1
20070070669 Tsern Mar 2007 A1
20070088995 Tsern et al. Apr 2007 A1
20070091696 Niggemeier et al. Apr 2007 A1
20070106860 Foster, Sr. et al. May 2007 A1
20070136537 Doblar et al. Jun 2007 A1
20070162700 Fortin et al. Jul 2007 A1
20070188997 Hockanson et al. Aug 2007 A1
20070192563 Rajan et al. Aug 2007 A1
20070195613 Rajan et al. Aug 2007 A1
20070204075 Rajan et al. Aug 2007 A1
20070216445 Raghavan et al. Sep 2007 A1
20070247194 Jain Oct 2007 A1
20070279084 Oh et al. Dec 2007 A1
20070288683 Panabaker et al. Dec 2007 A1
20070288686 Arcedera et al. Dec 2007 A1
20070288687 Panabaker et al. Dec 2007 A1
20080002447 Gulachenski et al. Jan 2008 A1
20080010435 Smith et al. Jan 2008 A1
20080025108 Rajan et al. Jan 2008 A1
20080025122 Schakel et al. Jan 2008 A1
20080025136 Rajan et al. Jan 2008 A1
20080025137 Rajan et al. Jan 2008 A1
20080027697 Rajan et al. Jan 2008 A1
20080027702 Rajan et al. Jan 2008 A1
20080027703 Rajan et al. Jan 2008 A1
20080028135 Rajan et al. Jan 2008 A1
20080028136 Schakel et al. Jan 2008 A1
20080028137 Schakel et al. Jan 2008 A1
20080031030 Rajan et al. Feb 2008 A1
20080031072 Rajan et al. Feb 2008 A1
20080037353 Rajan et al. Feb 2008 A1
20080056014 Rajan et al. Mar 2008 A1
20080062773 Rajan et al. Mar 2008 A1
20080065820 Gillingham et al. Mar 2008 A1
20080082763 Rajan et al. Apr 2008 A1
20080086588 Danilak et al. Apr 2008 A1
20080089034 Hoss et al. Apr 2008 A1
20080098277 Hazelzet Apr 2008 A1
20080103753 Rajan et al. May 2008 A1
20080104314 Rajan et al. May 2008 A1
20080109206 Rajan et al. May 2008 A1
20080109595 Rajan et al. May 2008 A1
20080109597 Schakel et al. May 2008 A1
20080109598 Schakel et al. May 2008 A1
20080115006 Smith et al. May 2008 A1
20080120443 Rajan et al. May 2008 A1
20080120458 Gillingham et al. May 2008 A1
20080123459 Rajan et al. May 2008 A1
20080126687 Rajan et al. May 2008 A1
20080126688 Rajan et al. May 2008 A1
20080126689 Rajan et al. May 2008 A1
20080126690 Rajan et al. May 2008 A1
20080126692 Rajan et al. May 2008 A1
20080133825 Rajan et al. Jun 2008 A1
20080159027 Kim Jul 2008 A1
20080170425 Rajan Jul 2008 A1
20080195894 Schreck et al. Aug 2008 A1
20080239857 Rajan et al. Oct 2008 A1
20080239858 Rajan et al. Oct 2008 A1
20090024789 Rajan et al. Jan 2009 A1
20090024790 Rajan et al. Jan 2009 A1
20090109613 Legen et al. Apr 2009 A1
20090216939 Smith et al. Aug 2009 A1
20090285031 Rajan et al. Nov 2009 A1
20090290442 Rajan Nov 2009 A1
20100005218 Gower et al. Jan 2010 A1
20100020585 Rajan Jan 2010 A1
20100257304 Rajan et al. Oct 2010 A1
20100271888 Rajan Oct 2010 A1
20100281280 Rajan et al. Nov 2010 A1
Foreign Referenced Citations (25)
Number Date Country
102004051345 May 2006 DE
102004053316 May 2006 DE
102005036528 Feb 2007 DE
0644547 Mar 1995 EP
62121978 Jun 1987 JP
01-171047 Jul 1989 JP
03-29357 Feb 1991 JP
03-276487 Dec 1991 JP
03-286234 Dec 1991 JP
07-141870 Jun 1995 JP
08-77097 Mar 1996 JP
11-149775 Jun 1999 JP
22025255 Jan 2002 JP
3304893 May 2002 JP
2006236388 Sep 2006 JP
1020040062717 Jul 2004 KR
WO9505676 Feb 1995 WO
WO9900734 Jan 1999 WO
WO0190900 Nov 2001 WO
WO0197160 Dec 2001 WO
WO2007002324 Jan 2007 WO
WO2007028109 Mar 2007 WO
WO2007038225 Apr 2007 WO
WO2007095080 Aug 2007 WO
WO2008063251 May 2008 WO
Related Publications (1)
Number Date Country
20110095783 A1 Apr 2011 US
Provisional Applications (1)
Number Date Country
61185585 Jun 2009 US