The present invention relates to the disabling of unused and/or inactive blocks in a programmable logic device to achieve lower static power consumption.
Technology scaling of transistor geometry has resulted in a rapid increase of static power consumption in semiconductor devices. At the current rate of increase, static power consumption will become the dominant source of power consumption in the near future. In many applications, such as those powered by batteries, low static power consumption is a property of great importance, for example, due to the desirability of a long battery life.
Programmable logic devices (PLDs), such as field programmable gate arrays (FPGAs), have a significantly higher static power consumption than dedicated logic devices, such as standard-cell application specific integrated circuits (ASICs). A reason for this high static power consumption is that for any given design, a PLD only uses a subset of the available resources. The unused resources are necessary for providing greater mapping flexibility to the PLD. However, these unused resources still consume static power in the form of leakage current. Consequently, PLDs are generally not used in applications where low static power is required.
It would therefore be desirable to have a PLD having a reduced static power consumption.
In accordance with one embodiment of the present invention, unused and/or inactive resources in a PLD are disabled to achieve lower static power consumption.
One embodiment of the present invention provides a method of operating a PLD, which includes the steps of enabling the resources of the PLD that are used in a particular circuit design, and disabling the resources of the PLD that are unused or inactive. The step of disabling can include de-coupling the unused or inactive resources from one or more power supply terminals. Alternately, the step of disabling can include regulating (e.g., reducing) a supply voltage applied to the unused or inactive resources.
In accordance with one embodiment, the step of disabling can be performed in response to configuration data bits stored by the PLD. These configuration data bits can be determined during the design of the circuit to be implemented by the PLD. That is, during the design, the design software is able to identify unused resources of the PLD, and select the configuration data bits to disable these unused resources.
The step of disabling can also be performed in response to user-controlled signals. These user-controlled signals can be generated in response to observable operating conditions of the PLD. For example, if certain resources of the operating PLD are inactive for a predetermined time period, then the user-controlled signals may be activated, thereby causing the inactive resources to be disabled.
In accordance with another embodiment, a PLD includes a first voltage supply terminal that receives a first supply voltage, a plurality of programmable logic blocks, and a plurality of switch elements, wherein each switch element is coupled between one of the programmable logic blocks and the first voltage supply terminal. A control circuit coupled to the switch elements provides a plurality of control signals that selectively enable or disable the switch elements. The control circuit can be controlled by a plurality of configuration data values stored by the PLD and/or a plurality of user-controlled signals. In an alternate embodiment, each of the switch elements can be replaced by a switching regulator.
The present invention will be more fully understood in view of the following description and drawings.
In accordance with one embodiment of the present invention, unused and inactive resources in a programmable logic device (PLD), such as a field programmable gate array (FPGA), are disabled to achieve lower static power consumption. The present invention includes both an enabling software flow and an enabling hardware architecture, which are described in more detail below. Unused resources of the PLD can be disabled when designing a particular circuit to be implemented by the PLD (hereinafter referred to as “design time”). In addition, resources of the PLD that are temporarily inactive can be disabled during operation of the PLD (hereinafter referred to as “run time”).
In accordance with the present invention, unused resources of the PLD are identified during the design time, following the place and route process (Step 103). These unused resources are then selectively disabled during the design time. As described below, there are several ways to disable the unused resources. By selectively disabling the unused resources at design time, significant static power reduction may be achieved with no performance penalty.
In another embodiment, further power savings are obtained by disabling temporarily inactive resources of the configured PLD during run time. Often, the entire design or parts of the design are temporarily inactive for some period of time. If the inactive period is sufficiently long, it is worthwhile to disable the inactive resources to reduce static power consumption. In a preferred embodiment, the decision of when to disable a temporarily inactive resource is made by the designer. In this embodiment, the user logic is provided access to a disabling mechanism, which enables the inactive resources to be disabled dynamically.
There are a number of techniques to disable resources in a PLD. In accordance with one embodiment, the PLD is logically subdivided into a plurality of separate programmable logic blocks. As described below, each programmable logic block may comprise one or more of the resources available on the programmable logic device. Switch elements are used to couple each of the programmable logic blocks to one or more associated voltage supply terminals (e.g., VDD or ground). The switch elements are controlled to perform a power-gating function, wherein unused and/or inactive programmable logic blocks are disabled (e.g., prevented from receiving power or receiving a reduced power). Preferably, only one of the voltage supply terminals (VDD or ground) is power-gated, thereby reducing the speed and area penalties associated with the switch elements. When the switch elements are controlled to de-couple the associated programmable logic blocks from the associated supply voltage, these programmable logic blocks are effectively disabled, thereby dramatically reducing the static power consumption of these blocks.
NOR gates 421-424 and inverters 411-414 are configured to generate power-gating control signals SLEEP1-SLEEP4 and SLEEP#1-SLEEP#4 in response to the configuration data values CD1-CD4 stored in configuration memory cells 431-434, respectively, and the user control signals UC1-UC4 provided on user logic input terminals 441-444, respectively.
For example, NOR gate 421 is coupled to receive configuration data value CD1 from configuration memory cell 431 and user control signal UC1 from user logic input terminal 441. If either the configuration data value CD1 or the user control signal UC1 is activated to a logic high state, then NOR gate 421 provides an output signal (SLEEP#1) having a logic “0” state. In response, inverter 411, which is coupled to the output terminal of NOR gate 421, provides an output signal (SLEEP1) having a logic “1” state.
The SLEEP1 signal is applied to the gate of PMOS power-gating transistor 451, which is coupled between block 301 and the VDD voltage supply terminal. The SLEEP#1 signal is applied to the gate of NMOS power-gating transistor 455, which is coupled between block 301 and the ground voltage supply terminal. The logic “0” state of the SLEEP#1 signal causes NMOS power-gating transistor 455 to turn off, thereby de-coupling block 301 from the ground supply voltage terminal. Similarly, the logic “1” state of the SLEEP1 signal causes PMOS power-gating transistor 451 to turn off, thereby de-coupling block 301 from the VDD supply voltage terminal. De-coupling block 301 from the VDD and ground supply voltage terminals effectively disables block 301, thereby minimizing the static leakage current in this block.
If both the configuration data value CD1 and the user control signal UC1 are de-activated to a logic low state, then NOR gate 421 provides a SLEEP#1 signal having a logic “1” state, and inverter 411 provides a SLEEP1 signal having a logic “0” state. The logic “1” state of the SLEEP#1 signal causes NMOS power-gating transistor 455 to turn on, thereby coupling block 301 to the ground supply voltage terminal. Similarly, the logic “0” state of the SLEEP1 signal causes PMOS power-gating transistor 451 to turn on, thereby coupling block 301 to the VDD supply voltage terminal. Coupling block 301 to the VDD and ground supply voltage terminals effectively enables block 301.
Programmable logic block 302 may be enabled and disabled in response to configuration data value CD2 and user control signal UC2, in the same manner as block 301. Similarly, programmable logic block 303 may be enabled and disabled in response to configuration data value CD3 and user control signal UC3, in the same manner as block 301. Programmable logic block 304 may be enabled and disabled in response to configuration data value CD4 and user control signal UC4, in the same manner as block 301.
As described above, when a programmable logic block is used and active, the associated power-gating transistors are turned on. Conversely, when a programmable logic block is unused or inactive, the associated power gating transistors are turned off. The SLEEP1-SLEEP4 and SLEEP#1-SLEEP#4 signals can be controlled by the configuration data values CD1-CD4 stored by configuration memory cells 431-434, which are best suited for disabling the associated blocks at design time. If a block is not disabled at design time, this block can be disabled at run time by the user control signals UC1-UC4, which may be generated by the user logic, or by other means.
In accordance with another embodiment of the present invention, some blocks have multiple supply voltages. In this case all of the supply rails should be power-gated to achieve maximum power reduction. In accordance with another embodiment, only one switch element may be associated with each block. That is, the blocks are power-gated by de-coupling the block from only one power supply terminal, and not both the VDD and ground supply voltage terminals, thereby conserving layout area.
The granularity of the power-gated programmable logic blocks can range from arbitrarily small circuits to significant portions of the PLD. The decision concerning the size of each programmable logic block is made by determining the desired trade-off between power savings, layout area overhead of the switch elements and the control circuit, and speed penalty. In a FPGA, each programmable logic block may be selected to include one or more configuration logic blocks (CLBs), input/output blocks (IOBs), and/or other resources of the FPGA (such as block RAM, processors, multipliers, adders, transceivers).
Another way to disable a programmable logic block is by scaling down the local supply voltage to the block as low as possible, which dramatically reduces the static power consumption of the block. To scale down the local supply voltage in this manner, each independently controlled programmable logic block is powered by a separate switching regulator.
Switching regulators 501-504 are controlled in response to the configuration data values C1-C4 stored in configuration memory cells 511-514, respectively, and the user control signals U1-U4 provided on user control terminals 521-524, respectively. A configuration data value (e.g., C1) having an activated state will cause the associated switching regulator (e.g., switching regulator 501) to provide a reduced voltage to the associated programmable logic block (e.g., block 301). Similarly, a user control signal (e.g., U2) having an activated state will cause the associated switching regulator (e.g., switching regulator 502) to provide a reduced voltage to the associated programmable logic block (e.g., block 502). A configuration data value (e.g., C3) and an associated user control signal (e.g., U3) both having have deactivated states will cause the associated switching regulator (e.g., switching regulator 503) to provide the full VDD supply voltage to the associated programmable logic block (e.g., block 503).
In accordance with one embodiment, configuration data values C1-C4 may be selected at design time, such that reduced voltages are subsequently applied to unused blocks during run time. User control signals U1-U4 may be selected during run time, such that reduced voltages are dynamically applied to inactive blocks at run time. Techniques for distributing multiple programmable down-converted voltages using on-chip switching voltage regulators are described in more detail in U.S. patent application Ser. No. 10/606,619, “Integrated Circuit with High-Voltage, Low-Current Power Supply Distribution and Methods of Using the Same” by Bernard J. New, et al., which is hereby incorporated by reference.
In the embodiment of
Although the invention has been described in connection with several embodiments, it is understood that this invention is not limited to the embodiments disclosed, but is capable of various modifications, which would be apparent to a person skilled in the art. For example, although the described embodiments included four programmable logic blocks, it is understood that other numbers of blocks can be used in other embodiments. Thus, the invention is limited only by the following claims.
The present application is a divisional of U.S. patent application Ser. No. 10/666,669, filed Sep. 19, 2003 (now U.S. Pat. No. 7,098,689).
Number | Name | Date | Kind |
---|---|---|---|
4962341 | Schoeff | Oct 1990 | A |
5303390 | Little | Apr 1994 | A |
5362989 | Hennedy | Nov 1994 | A |
5519663 | Harper et al. | May 1996 | A |
5568062 | Kaplinsky | Oct 1996 | A |
5583457 | Horiguchi et al. | Dec 1996 | A |
5612892 | Almulla | Mar 1997 | A |
5615162 | Houston | Mar 1997 | A |
5671149 | Brown | Sep 1997 | A |
5682107 | Tavana et al. | Oct 1997 | A |
5712790 | Ditlow | Jan 1998 | A |
5801548 | Lee et al. | Sep 1998 | A |
5811962 | Ceccherelli | Sep 1998 | A |
5825662 | Trimberger | Oct 1998 | A |
5832286 | Yoshida | Nov 1998 | A |
5914873 | Blish | Jun 1999 | A |
5946257 | Keeth | Aug 1999 | A |
5958026 | Goetting et al. | Sep 1999 | A |
6038386 | Jain | Mar 2000 | A |
6114843 | Olah | Sep 2000 | A |
6148390 | MacArthur et al. | Nov 2000 | A |
6160418 | Burnham | Dec 2000 | A |
6169419 | De et al. | Jan 2001 | B1 |
6172518 | Jenkins, IV. et al. | Jan 2001 | B1 |
6208171 | Kumagai et al. | Mar 2001 | B1 |
6384626 | Tsai et al. | May 2002 | B2 |
6466049 | Diba et al. | Oct 2002 | B1 |
6489804 | Burr | Dec 2002 | B1 |
6583645 | Bennett et al. | Jun 2003 | B1 |
6631502 | Buffet et al. | Oct 2003 | B2 |
6710612 | Farnworth et al. | Mar 2004 | B2 |
6711719 | Cohn et al. | Mar 2004 | B2 |
6747478 | Madurawe | Jun 2004 | B2 |
6839888 | Gupta | Jan 2005 | B2 |
6885563 | Panella | Apr 2005 | B2 |
6920627 | Blodget et al. | Jul 2005 | B2 |
6936917 | Lopata et al. | Aug 2005 | B2 |
6950998 | Tuan | Sep 2005 | B1 |
6960934 | New | Nov 2005 | B2 |
6968467 | Inoue et al. | Nov 2005 | B2 |
7003620 | Avraham et al. | Feb 2006 | B2 |
7078932 | Swami | Jul 2006 | B2 |
7080341 | Eisenstadt et al. | Jul 2006 | B2 |
7098689 | Tuan et al. | Aug 2006 | B1 |
7109748 | Liu et al. | Sep 2006 | B1 |
7112997 | Liang et al. | Sep 2006 | B1 |
7135886 | Schlacter | Nov 2006 | B2 |
7170315 | Bakker et al. | Jan 2007 | B2 |
7313706 | Williams et al. | Dec 2007 | B2 |
7345944 | Jenkins | Mar 2008 | B1 |
20030030326 | Shenai et al. | Feb 2003 | A1 |
20030218478 | Sani et al. | Nov 2003 | A1 |
20040145955 | Mizuno et al. | Jul 2004 | A1 |
20050091547 | Hanrieder et al. | Apr 2005 | A1 |
20050201174 | Klein | Sep 2005 | A1 |
20060053246 | Lee | Mar 2006 | A1 |
20060069851 | Chung et al. | Mar 2006 | A1 |
20060202713 | Shumarayev | Sep 2006 | A1 |
20070001720 | Li et al. | Jan 2007 | A1 |
20070164785 | He | Jul 2007 | A1 |
Number | Date | Country | |
---|---|---|---|
Parent | 10666669 | Sep 2003 | US |
Child | 11502939 | US |