The present embodiments generally relate to integrated circuit memory devices, controller devices and memory systems. More specifically, the present embodiments relate to the design of a protocol for refresh operations between an integrated circuit controller device and an integrated circuit memory device.
The disclosed embodiments provide a memory system that facilitates efficient self-refreshing operations, wherein the system may be configured to shut off power and/or shut down clocking to a high-speed interface, but leaves circuitry operating to self-time refreshing operations to maintain the contents of memory cells. In several embodiments, protocols for operating in this self-refresh state may decrease power consumption, which may be attractive in applications such as notebook computers or other portable computing devices for which battery life is important.
In some of the disclosed embodiments, progress information regarding the refresh operation is sent from the memory device to the memory controller during the self-refresh state through a (e.g., uncalibrated, low-power) sideband link. In this way, the uncertainty associated with the timing of the self-refresh operation may be eliminated. For example, in a conventional self-refresh operation, the self-refresh exit delay must account for the worst-case timing of an in-process internal refresh operation (controlled by an internally generated clock that may not be accurate) plus some margin. In contrast, in the disclosed embodiments, the controller can use the progress information received from the memory device to determine when the refresh operation actually completes and can immediately issue a new command to that bank. This enables the memory controller to more optimally control the sequencing of subsequent memory operations to significantly reduce the exit delay from the self-refresh state.
More specifically, referring to the exemplary embodiment depicted in
For example, the progress information can be used to determine whether a self-refreshing operation is in process or will occur in the near future. If not, the memory controller can immediately initiate one or more subsequent memory accesses without having to wait for a self-refreshing operation to complete. Additionally, the progress information can be used by the memory controller to determine that a given bank is presently being refreshed. This enables the memory controller to perform memory operations to other banks in the memory device while the self-refreshing operation completes for the given bank.
In one embodiment, the system enters a deep power-down state, wherein the system shuts off power and/or shuts down clocking to a high-speed interface. However, the memory device does not enter a self-refresh state. Instead, the memory controller continues to coordinate refreshing operations through a sideband link. This enables the memory controller to know whether a given bank is being refreshed and to schedule refreshing operations for other banks.
More specifically, referring to
These operations are described in more detail below, but first we describe some details of the memory system.
Memory Controller and Memory Device
DRAM 304 includes two sets of memory banks. The first set includes Bank 0a, Bank 1a, Bank 2a, Bank 3a, Bank 4a, Bank 5a, Bank 6a and Bank 7a, and the second set includes Bank 0b, Bank 1b, Bank 2b, Bank 3b, Bank 4b, Bank 5b, Bank 6b and Bank 7b. During the self-refresh state, refreshing operations for the first set of memory banks are controlled by control circuitry 340 on DRAM 304, and refreshing operations for the second set of memory banks are controlled by control circuitry 350 on DRAM 304.
The memory controller logic on controller chip 302 communicates with the memory banks on DRAM 304 through a number of different interfaces and communications links. More specifically, communications take place between memory controller logic 310 on controller chip 302 and the first set of memory banks on DRAM 304 through (1) interfaces DQ 314, DM 315, CA0 316, CA1 317 and CK 318 on controller chip 302, (2) differential links 306, and (3) interfaces DQ 341, DM 342, CA0 343, CA1 344 and CK 345 on DRAM 304. Similarly, communications take place between memory controller logic 320 on controller chip 302 and the second set of memory banks on DRAM 304 through (1) interfaces DQ 324, DM 325, CA0 326, CA1 327 and CK 328 on controller chip 302, (2) differential links 308, and (3) interfaces DQ 351, DM 352, CA0 353, CA1 354 and CK 355 on DRAM 304.
In this embodiment, controller chip 302 and DRAM 304 additionally communicate refreshing information through an uncalibrated, low-power sideband link which comprises (1) interface SL 330 in controller chip 302, (2) uncalibrated links 370, and (3) interface SL 360 on DRAM 304.
This interface circuitry of
In an alternative embodiment which is illustrated in
Although the exemplary embodiment disclosed in
Timing Diagrams
Next, at a time tPM-RAS after the PM transition, the memory device starts performing a self-refresh operation, which involves activating the row of memory cells located in the bank as specified by the {B,R} address. The memory device also asserts the refresh (RF) signal on signal line SL[0] to let the memory controller know that the memory device is performing the self-refresh operation (operation D). Next, at a time tRAs after the RF assertion, the memory device precharges the memory cells located in the row in the bank as specified by the {B,R} address, and increments the {B,R} address in bank-fast or row-fast order, depending upon the mode selected by the PR command. The memory device also deasserts the RF signal (operation E). Next, at a time tIREF (the refresh interval) after the previous RF assertion, the memory device starts performing a subsequent self-refresh operation. This involves incrementing the bank and row counters on the memory device to point to the next {B,R} address to be refreshed before commencing the next self-refresh operation. It also involves reasserting the RF signal (operation F).
In an alternative embodiment illustrated in
In the foregoing description and in the accompanying drawings, specific terminology and drawing symbols are set forth to provide a thorough understanding of the present invention. In some instances, the terminology and symbols may imply specific details that are not required to practice the invention. Consequently, these embodiments may include fewer components or additional components. Moreover, components may be combined into a single component and/or the position of one or more components may be changed.
While the preceding embodiments used a memory system implemented on separate integrated circuits or chips as an illustration, in other embodiments at least portions of either of these chips may be implemented on another integrated circuit. For example, controller chip 302 (
An output of a process for designing an integrated circuit, or a portion of an integrated circuit, comprising one or more of the circuits described herein may be a computer-readable medium such as, for example, a magnetic tape or an optical or magnetic disk. The computer-readable medium may be encoded with data structures or other information describing circuitry that may be physically instantiated as an integrated circuit or portion of an integrated circuit. Although various formats may be used for such encoding, these data structures are commonly written in Caltech Intermediate Form (CIF), Calma GDS II Stream Format (GDSII) or Electronic Design Interchange Format (EDIF). Those of skill in the art of integrated circuit design can develop such data structures from schematics of the type detailed above and the corresponding descriptions, and can encode the data structures on a computer-readable medium. Those of skill in the art of integrated circuit fabrication can use such encoded data to fabricate integrated circuits comprising one or more of the circuits described herein.
While the present invention has been described in connection with specific embodiments, the claims are not limited to what is shown. For example, in some embodiments the links between controller chip 302 and DRAM 304 in
Moreover, some components are shown directly connected to one another, while others are shown connected via intermediate components. In each instance, the method of communication establishes some desired electrical communication between two or more circuit nodes, or terminals. Such coupling may often be accomplished using a number of circuit configurations, as will be understood by those of skill in the art. For example, the foregoing embodiments support AC-coupled links, DC-coupled links, or both. Therefore, the spirit and scope of the appended claims should not be limited to the foregoing description. Only those claims specifically reciting “means for” or “step for” should be construed in the manner required under the sixth paragraph of 35 U.S.C. § 112.
This application is a continuation of U.S. Utility patent application Ser. No. 17/115,538, filed on behalf of first-named inventor Frederick A. Ware on Dec. 8, 2020, for “Protocol For Refresh Between A Memory Controller And A Memory Device,” which in turn is a continuation of U.S. Utility patent application Ser. No. 16/692,069, filed on behalf of first-named inventor Frederick A. Ware on Nov. 22, 2019, for “Protocol For Refresh Between A Memory Controller And A Memory Device” (now U.S. Pat. No. 10,892,001), which in turn is a continuation of U.S. Utility patent application Ser. No. 16/032,575, filed on behalf of first-named inventor Frederick A. Ware on Jul. 11, 2018, for “Protocol For Refresh Between A Memory Controller And A Memory Device” (now U.S. Pat. No. 10,510,395), which in turn is a continuation of U.S. Utility patent application Ser. No. 13/257,412, filed on behalf of first-named inventor Frederick A. Ware on Sep. 19, 2011, for “Protocol For Refresh Between A Memory Controller And A Memory Device” (abandoned), which in turn is a national state filing under 35 U.S.C. § 371 into the United States of Patent Cooperation Treaty Application No. PCT/US2010/030166, filed Apr. 7, 2010, which in turn claims priority to U.S. Provisional Patent Application No. 61/171,576, filed on Apr. 22, 2009. Priority is hereby claimed to the aforementioned patent applications, which are each hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4818932 | Odenheimer | Apr 1989 | A |
5261068 | Gaskins et al. | Nov 1993 | A |
5713006 | Shigeeda | Jan 1998 | A |
6118719 | Dell et al. | Sep 2000 | A |
6233192 | Tanaka | May 2001 | B1 |
6378018 | Tsern et al. | Apr 2002 | B1 |
7155623 | Lefurgy et al. | Dec 2006 | B2 |
20030065884 | Lu et al. | Apr 2003 | A1 |
20030084235 | Mizuki | May 2003 | A1 |
20050071543 | Ellis et al. | Mar 2005 | A1 |
20050259493 | Walker | Nov 2005 | A1 |
20050265103 | Remaklus, Jr. et al. | Dec 2005 | A1 |
20060087904 | Pyo et al. | Apr 2006 | A1 |
20060212651 | Ashmore | Sep 2006 | A1 |
20060239096 | Chu et al. | Oct 2006 | A1 |
20080037353 | Rajan et al. | Feb 2008 | A1 |
20090150621 | Lee | Jun 2009 | A1 |
20100095058 | Proebsting | Apr 2010 | A1 |
20120033519 | Confalonieri et al. | Feb 2012 | A1 |
20140297939 | Perego et al. | Oct 2014 | A1 |
Entry |
---|
Information Disclosure Statement dated Sep. 27, 2011 re U.S. Appl. No. 13/257,412. 6 Pages. |
PCT Preliminary Report on Patentability dated Nov. 3, 2011 (Chapter I) in International Application No. PCT/US2010/030166. 8 pages. |
Number | Date | Country | |
---|---|---|---|
20230223067 A1 | Jul 2023 | US |
Number | Date | Country | |
---|---|---|---|
61171576 | Apr 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17115538 | Dec 2020 | US |
Child | 18078934 | US | |
Parent | 16692069 | Nov 2019 | US |
Child | 17115538 | US | |
Parent | 16032575 | Jul 2018 | US |
Child | 16692069 | US | |
Parent | 13257412 | US | |
Child | 16032575 | US |