The present invention is generally related to digital computer systems.
One of the important features of integrated circuits deigned for portable applications is their ability to efficiently utilize the limited capacity of the battery power source. Typical applications include cellular telephones and personal digital assistants (PDAs), which might have a Lithium ion battery or two AAA alkaline batteries as the power source. Users have come to expect as much as three to four weeks of standby operation using these devices. Standby operation refers to the situation where the cellular phone, handheld device, etc. is powered on but not being actively used (e.g., actively involved in a call). Generally, it is estimated that the integrated circuits providing the functionality of the device is only performing useful work approximately 2% of the time while the device is in standby mode.
Removing the power supply from selected circuits of a device during standby is a technique employed by designers for battery powered applications. The technique is generally applied only to circuit blocks outside of the central processing unit (CPU). A primary reason for not applying this technique to CPUs, has been the difficulty in being able to restore the current processor state information necessary to continue execution after coming out of the standby mode. One solution for this limitation involves saving the current processor state information to external storage mechanisms (e.g., such as flash memory, a hard disk drive, etc.). In such a case there is the overhead required in transferring the state to and from the external storage mechanism. Even if the battery powered device had a hard disk drive, and many don't, the time consuming state transfer may not meet the real time response requirements of the application when the device needs to wake up to respond to a new event.
Other issues are presented when the functionality of a device is implemented by a system-on-a-chip (SOC) integrated circuit. For example, when the core of a system-on-a-chip CPU is temporarily powered down (e.g., deep sleep mode), some of the outputs that connect to assorted peripherals (e.g. LCD display, SPI interface, SDIO, Hard-disk, etc.) should be held in an idle state to avoid having to reprogram the peripheral or lose existing context in the peripheral. This causes a problem since some peripherals need particular values to be set at their inputs (which are connected to the outputs of the SOC) to hold a safely inactive state. For example, if a device is connected to a SOC that is clocked on the falling edge of a clock signal, and the SOC is powered down with that signal as a logic 1, but the power down state is a logic 0 (e.g., ground), it will cause a spurious clock on that signal.
This problem is further exacerbated by the heavy use of pin-muxing or sharing, in which a single pin can have multiple functions in different designs by different customers. In one design a pin may be set to act as part of an SPI interface that wants to be held low when in sleep mode, while the same pin in another design, perhaps by a different customer may be used as a UART pin which would need to be held high when the CPU is put to deep sleep mode. While pin-muxing provides a way to put more features in each chip and allows the chip to be more suitable for a wide range of designs, it precludes knowing exactly at IC design time what each pin will be used for. A more flexible method of configuring the power down states is needed.
One solution to this problem would be to have a register for each pin that drives the pin to any one of the allowed number of states, such as: Input, output 0, output 1, output Hi-Z, open drain, etc. This is a workable solution, but has a problem that since normally the signals that control these functions come from the core of the SOC, they will not be present when the core is powered down in deep sleep mode. To overcome this, a second set of registers on the SOC on a special power domain (AO) which remains powered when the rest of the core is powered down in deep sleep mode is used to control the pins.
The special power domain allows the state information of these IO pads to be preserved. However the big problem is that it requires many signals from the portion of the chip that is in the special power domain to be routed to each pad. For example, with 300 signal pads and 3 wires per pad, as many as 900 traces have to be routed on the integrated circuit die, which is a large number at the top level of an integrated circuit die layout. These pad control signals must also be powered by the AO rail, which complicates the distribution of this AO rail or the routing of these pad control signals. The peripherals must be able to wale the processor from Deep Sleep mode when they assert an interrupt to be serviced.
Thus, what is needed is a solution for powering down a digital integrated circuit device for reduced standby power consumption while retaining the integrity of the operating state. What is further needed is a solution for powering down the device without imposing burdensome trace routing requirements on the integrated circuit die layout.
Embodiments of the present invention provides a method and system for powering down an integrated circuit device for reduced standby power consumption while retaining the integrity of the operating state. Embodiments of the present invention further provide a solution for powering down the integrated circuit device without imposing burdensome trace routing requirements on the integrated circuit die layout.
In one embodiment, the present invention is implemented as an integrated circuit device having a power circuit for maintaining asserted values on input output pins of the device when one or more functional blocks of the device are placed in a low-power sleep mode (e.g., deep sleep, etc.). The integrated circuit device includes a power circuit, or power ring, disposed along the periphery of the device. This power circuit is configured to maintain power when the device is placed in the low-power mode, where, for example, the core of the device is shut down. A plurality of input output blocks are included in the integrated circuit device and are for receiving and sending external inputs and outputs for the device. When the integrated circuit device enters the low-power mode, the core of the device is shut down and those input output blocks which are not needed are also shut down. The power circuit is coupled to provide power to at least one of the input output blocks, thereby allowing the block to maintain state when the rest of the device may be shut down. This allows the device to maintain state and to detect signals via at least one of the input output blocks, thereby allowing the device to receive a wake-up signal and wake up from the low-power mode.
In one embodiment, the integrated circuit device further includes a signal routing path disposed along the periphery of the device. The signal routing path is coupled to receive power from the power circuit and to route signals from the input output blocks. The power from the power circuit enables the reception of a wake-up signal from an external source when the integrated circuit device is in the low-power mode.
In one embodiment, the power circuit further comprises a plurality of segments. Each of the segments are disposed along the periphery of the integrated circuit device. A first set of the segments are powered segments and a second set of the segments can be unpowered segments, wherein the unpowered segments do not receive power when the integrated circuit device is in the low-power mode. Accordingly, for example, those input output blocks that are coupled to unpowered segments are shut down when the device is in the low-power mode.
In this manner, the signal state of the input output pins can be maintained as the core functional blocks of the integrated circuit device are powered down. Upon exit from sleep mode (e.g., wake up), the input output pins can resume being driven by the one or more functional blocks. Additionally, this invention minimizes the routing of multiple signals from a special power domain to the input output pin, which greatly reduces signal trace routing requirements.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements.
Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with the preferred embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following detailed description of embodiments of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be recognized by one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the embodiments of the present invention.
Some portions of the detailed descriptions, which follow, are presented in terms of procedures, steps, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These 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. A procedure, computer executed step, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions 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 in a computer system. 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 following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “processing” or “accessing” or “executing” or “storing” or “rendering” or the like, refer to the action and processes of a computer system, or similar electronic computing device (e.g., system 100 of
The SOC 110 includes an architecture that is optimized along multiple power domains to enable an optimized power consumption versus performance profile. In the
Each of the power domains 121-122 includes at least one power island. The power islands 131-135 are shown. The power islands are configured to receive power from the particular power domain in which they reside. Power islands are distinguished from power domains, in part, by the characteristic that power islands are not supplied their own dedicated voltage rail.
A power island typically comprises a set of components (e.g., sequential logic, storage, interconnects, etc.) that can be power gated with respect to the power domain. As used herein, power gating refers to the connecting or disconnecting of a power island to or from the power circuits of a power domain. The connecting and disconnecting in power gating is typically implemented using CMOS gating logic. It should be noted, however, that there exists a variety of different power optimizations that could be utilized. Such optimizations could exist independently per island with respect to other optimizations (e.g., foreword or back biasing, etc.).
Each of the power islands 131-135 includes one or more functional blocks. The multiple functional blocks 101-109 comprising the non-power gated functions island are shown as an example. The functional blocks 101-109 show the attribute where more than one functional block can reside within a given power island. The functional blocks draw their power from the circuits of the power island in which they reside. When a power island is shut down, each of the functional blocks that are within that power island are also shut down.
Each functional block typically comprises special-purpose logic, storage, hardware resources, and the like that is configured to provide a specific device functionality. Each of the functional blocks are purposely designed and optimized to excel at accomplishing a block specific intended task. The intended tasks are sufficiently granular such that particularly demanding tasks can be performed by using a greater number of functional blocks, while comparatively simple tasks can be performed by using a lesser number of functional blocks. For example, some tasks may only require a single functional block for implementation.
The integrated circuit device 100 optimizes performance versus power consumption by intelligently adjusting power consumption in relation to a requested device functionality. Typical requested device functionality can include, for example, applications such as MP3 playing, video playing, 3-D gaming, GPS navigation, and the like. To provide the requested device functionality, only those functional blocks that are needed are turned on and used. Those functional blocks that are needed will consume power from their respective power islands, which in turn will consume power from their respective power domains. Unneeded functional blocks are shut down.
As depicted in
The
The always on power island 131 of the domain 121 includes functionality for waking up the SOC 110 from a sleep mode. For example, in one embodiment, the always on domain 121, is configured to consistently have power applied to its constituent circuits. For example, the constituent circuits of the power domain 121 can be configured to draw power from the voltage rail 161 and to receive a clock signal in an uninterrupted manner. This enables the power domain 121 to execute sequential state machine logic, instructions, etc. while the rest of the SOC 110 is powered down. This can allow, for example, an internal state machine within the power domain 130 to detect wake event signals, the signals indicating a wale up from the sleep mode. For example, in a deep sleep mode, the voltage rail 162 and the domain 122 can be shut down. The components of the always on domain 121 will remain active, waiting for a wake-up signal.
The CPU power island 132 is within the domain 122. The CPU power island 132 provides the computational hardware resources to execute the more complex software-based functionality for the SOC 110. Such software functionality includes executing the operating system software, specific application software, and the like. Additionally, the CPU power island 132 executes special interrupt handling software that helps the SOC 110 respond to external events.
The GPU power island 133 is also within the domain 122. The GPU power island 133 provides the graphics processor hardware functionality for executing 3-D rendering functions. The three rendering functions include rendering real-time 3-D images as produced by a gaming application, rendering 3-D symbology as used by a mapping application, and the like.
The video processor island 135 is also within the domain 122. The video processor island 135 provides specialized video processing hardware for the encoding of images and video. The hardware components of the video processor island 135 are specifically optimized for performing real-time video encoding, which can be a computationally intensive task. Additionally, the video processor island 135 can also incorporate hardware specifically tailored for decompressing and rendering high-definition video. In the present embodiment, all modules that are used for video capture are included in the video processor island 135, including the image processing functional blocks that convert the data received from an image capture sensor (e.g., image capture device 507 of
The non-power gated functions island 134 is also within the domain 122. In the present embodiment, the term “non-power gated functions” refers to the characteristic that the island 134 does not include any power gating logic or components for turning off the island 134 when the domain 122 is on. Consequently, whenever the domain 122 is on, the non-power gated functions island 134 is also on. This characteristic allows the non-power gated functions island 134 to consolidate those hardware functions that tend to be common across the different use case scenarios of the SOC 110. For example, across the range of intended device functions, certain components will tend to always be needed. These components can be concentrated within the non-power gated functions island 134, and thereby simplify the implementation of the other islands 132, 133, and 135.
The memory 130 is an external memory that is coupled to the SOC 110. The memory 130 provides the execution environment for the CPU island 132. In typical usage scenarios, the operating system software and/or application software is instantiated within the memory 130. In one embodiment, the memory 130 is implemented as a specialized DRAM that can enter a self refresh mode. In such an embodiment, the volatile memory 130 can be set to self refresh and thereby maintain its content independent of the memory controller as the SOC 110 is placed into sleep mode.
As shown in
As shown in the
As shown in
In one embodiment, the power circuit further comprises a plurality of segments. Instead of one continuous ring that provides power to input output blocks along the entire periphery of the SOC device, the power circuit can include numerous segments, some of which can be powered in low-power state and some of which can be shut down. Each of the segments are disposed along the periphery of the integrated circuit device. For example, in an exemplary embodiment, a first set of the segments are powered segments and a second set of the segments can be unpowered segments. The unpowered segments do not receive power when the integrated circuit device is in the low-power mode.
Accordingly, for example, consider a case where the input output block 312 comprises an unpowered segment. The input output block 312 is not coupled to the power ring 200. Those input output pins of the block 312 are typically shut down when the device enters the low-power mode. Such segments are generally configured in HW to always be shut down during Deep Sleep. It should be noted, however, that there can also be certain IO rails that may be programmatically shut down relative to a particular use case scenario during sleep mode. In such a case, there is a portion of the block 312 that is on the AO rail and is maintained. It is the portion of the block 312 that is powered by the IO rail that is shut down.
In this manner, the signal state of certain selected input output pins can be maintained as the core functional blocks of the integrated circuit device are powered down. Upon exit from sleep mode (e.g., wake up), the input output pins can resume being driven by the one or more functional blocks. Additionally, this invention minimizes the routing of multiple signals from a special power domain to the input output pin, which greatly reduces signal trace routing requirements.
It should be noted that in general, to minimize current in low-power mode, the input output blocks, power ring, and signal routing ring comprising the always on powered regions are minimized in area and optimized to use the lowest leakage/power cells. For example, depending upon the particular application, these regions can be as small as the logic around a single IO, a series of IOs common to an interface, or a set of “branches” that surround the core as opposed to a ring.
One advantage of a powered ring surrounding the core is that it greatly simplifies the routing of sleep/wake controls to all input output blocks that will remain active during deep sleep. The power ring is a more readily implementable architecture since buffers can be used to repeat signals around the periphery of the chip. As described above, for those regions of IOs that do not need to be active during sleep mode, the ring is broken into segments which are separated by regions of unpowered logic/IOs. The powered buffers are used to repeat signals across particularly long unpowered regions.
It should be noted that in one embodiment, level shifters can be implemented between power domains that are At different voltages. For example, in one embodiment, the always on voltage and core voltage are required to closely track to one another in order to minimize leakage between the domains on signals that pass between them. In an alternative embodiment, level shifters can be used to transfer signals between the domains when they are at different voltages.
The RF transceiver 501 enables two-way cell phone communication and RF wireless modem communication functions. The keyboard 502 is for accepting user input via button pushes, pointer manipulations, scroll wheels, jog dials, touch pads, and the like. The one or more displays 503 are for providing visual output to the user via images, graphical user interfaces, full-motion video, text, or the like. The audio output component 504 is for providing audio output to the user (e.g., audible instructions, cell phone conversation, MP3 song playback, etc.). The GPS component 505 provides GPS positioning services via received GPS signals. The GPS positioning services enable the operation of navigation applications and location applications, for example. The removable storage peripheral component 506 enables the attachment and detachment of removable storage devices such as flash memory, SD cards, smart cards, and the like. The image capture component 507 enables the capture of still images or full motion video. The handheld device 500 can be used to implement a smart phone having cellular communications technology, a personal digital assistant, a mobile video playback device, a mobile audio playback device, a navigation device, or a combined functionality device including characteristics and functionality of all of the above.
The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents.
Number | Name | Date | Kind |
---|---|---|---|
4868832 | Marrington et al. | Sep 1989 | A |
5109494 | Ehlig et al. | Apr 1992 | A |
5142690 | McMullan, Jr. et al. | Aug 1992 | A |
5220660 | Yoshizawa et al. | Jun 1993 | A |
5230067 | Buch | Jul 1993 | A |
5274828 | McAdams | Dec 1993 | A |
5305443 | Franzo | Apr 1994 | A |
5339445 | Gasztonyi | Aug 1994 | A |
5386552 | Garney | Jan 1995 | A |
5388265 | Volk | Feb 1995 | A |
5396635 | Fung | Mar 1995 | A |
5402492 | Goodman et al. | Mar 1995 | A |
5408668 | Tornai | Apr 1995 | A |
5446904 | Belt et al. | Aug 1995 | A |
5471189 | Dietz et al. | Nov 1995 | A |
5510740 | Farrell et al. | Apr 1996 | A |
5517441 | Dietz et al. | May 1996 | A |
5524249 | Suboh | Jun 1996 | A |
5528610 | Edler et al. | Jun 1996 | A |
5530845 | Hiatt et al. | Jun 1996 | A |
5535398 | Biggs et al. | Jul 1996 | A |
5557777 | Culbert | Sep 1996 | A |
5586308 | Hawkins et al. | Dec 1996 | A |
5588099 | Mogilevsky et al. | Dec 1996 | A |
5594367 | Trimberger et al. | Jan 1997 | A |
5594874 | Narayanan et al. | Jan 1997 | A |
5649222 | Mogilevsky | Jul 1997 | A |
5659687 | Kim et al. | Aug 1997 | A |
5687382 | Kojima et al. | Nov 1997 | A |
5737613 | Mensch, Jr. | Apr 1998 | A |
5752050 | Hernandez et al. | May 1998 | A |
5758133 | Envoy | May 1998 | A |
5790877 | Nishiyama et al. | Aug 1998 | A |
5862368 | Miller et al. | Jan 1999 | A |
5869979 | Bocchino | Feb 1999 | A |
5898879 | Kim | Apr 1999 | A |
5951689 | Evoy et al. | Sep 1999 | A |
5963219 | Choi | Oct 1999 | A |
6029170 | Garger et al. | Feb 2000 | A |
6034544 | Agrawal et al. | Mar 2000 | A |
6040845 | Melo et al. | Mar 2000 | A |
6057705 | Wojewoda et al. | May 2000 | A |
6061679 | Bournas et al. | May 2000 | A |
6134167 | Atkinson | Oct 2000 | A |
6163583 | Lin et al. | Dec 2000 | A |
6169546 | Bogdan | Jan 2001 | B1 |
6169984 | Bogdan | Jan 2001 | B1 |
6178523 | Klein | Jan 2001 | B1 |
6191969 | Pereira | Feb 2001 | B1 |
6191970 | Pereira | Feb 2001 | B1 |
6212645 | Tjandrasuwita | Apr 2001 | B1 |
6216234 | Sager et al. | Apr 2001 | B1 |
6243280 | Wong et al. | Jun 2001 | B1 |
6249284 | Bogdan | Jun 2001 | B1 |
6266776 | Sakai | Jul 2001 | B1 |
6347370 | Grimsrud | Feb 2002 | B1 |
6380764 | Katoh et al. | Apr 2002 | B1 |
6397340 | Watts, Jr. et al. | May 2002 | B2 |
6493856 | Usami et al. | Dec 2002 | B2 |
6523128 | Stapleton et al. | Feb 2003 | B1 |
6538947 | Ahmed et al. | Mar 2003 | B2 |
6552596 | Cowles et al. | Apr 2003 | B2 |
6584003 | Kim et al. | Jun 2003 | B1 |
6600575 | Kohara | Jul 2003 | B1 |
6678831 | Mustafa et al. | Jan 2004 | B1 |
6694451 | Atkinson | Feb 2004 | B2 |
6717435 | Mitsumori et al. | Apr 2004 | B1 |
6728959 | Merkey | Apr 2004 | B1 |
6754837 | Helms | Jun 2004 | B1 |
6760850 | Atkinson et al. | Jul 2004 | B1 |
6762768 | Dilliplane | Jul 2004 | B2 |
6765958 | Dowling | Jul 2004 | B1 |
6768659 | Gillingham et al. | Jul 2004 | B2 |
6775776 | Vogt et al. | Aug 2004 | B1 |
6804267 | Long et al. | Oct 2004 | B1 |
6804763 | Stockdale et al. | Oct 2004 | B1 |
6816809 | Circenis | Nov 2004 | B2 |
6845434 | Lin | Jan 2005 | B2 |
6845456 | Menezes et al. | Jan 2005 | B1 |
6901298 | Govindaraj et al. | May 2005 | B1 |
6990594 | Kim | Jan 2006 | B2 |
7007247 | Wang et al. | Feb 2006 | B1 |
7043649 | Terrell, II | May 2006 | B2 |
7058834 | Woods et al. | Jun 2006 | B2 |
7100013 | de Waal | Aug 2006 | B1 |
7174472 | Hill | Feb 2007 | B2 |
7187205 | Ramaraju | Mar 2007 | B2 |
7243318 | Mirza et al. | Jul 2007 | B1 |
7256232 | Lamaze et al. | Aug 2007 | B2 |
7285980 | Bansal et al. | Oct 2007 | B2 |
7372298 | Chu et al. | May 2008 | B2 |
7401240 | Heller, Jr. et al. | Jul 2008 | B2 |
7414550 | Sudharsanan | Aug 2008 | B1 |
7426647 | Fleck et al. | Sep 2008 | B2 |
7428644 | Jeddeloh et al. | Sep 2008 | B2 |
7432921 | Oshima et al. | Oct 2008 | B2 |
7434072 | Peirson et al. | Oct 2008 | B2 |
7518399 | Santurkar | Apr 2009 | B1 |
7529958 | Roth et al. | May 2009 | B2 |
7583104 | Simmons et al. | Sep 2009 | B2 |
7590815 | de Waal | Sep 2009 | B1 |
7599317 | Schaap | Oct 2009 | B2 |
7624215 | Axford et al. | Nov 2009 | B2 |
7631117 | Aida et al. | Dec 2009 | B2 |
7698586 | Kim et al. | Apr 2010 | B2 |
7730248 | Goss et al. | Jun 2010 | B2 |
7739533 | Rauschmayer et al. | Jun 2010 | B2 |
7945875 | Anand et al. | May 2011 | B2 |
7954078 | Wang et al. | May 2011 | B1 |
8327173 | Hendin et al. | Dec 2012 | B2 |
20010044909 | Oh et al. | Nov 2001 | A1 |
20020172008 | Michael | Nov 2002 | A1 |
20030023825 | Woo et al. | Jan 2003 | A1 |
20030093702 | Luo et al. | May 2003 | A1 |
20030204757 | Flynn | Oct 2003 | A1 |
20030204761 | D'Alessio | Oct 2003 | A1 |
20030206164 | Juenger | Nov 2003 | A1 |
20030233525 | Reeves | Dec 2003 | A1 |
20040128574 | Ricci et al. | Jul 2004 | A1 |
20050015321 | Vindekilde | Jan 2005 | A1 |
20050125705 | Cheng et al. | Jun 2005 | A1 |
20060184808 | Chua-Eoan et al. | Aug 2006 | A1 |
20060226895 | Hoshi et al. | Oct 2006 | A1 |
20070300092 | Kurita | Dec 2007 | A1 |
20080155282 | Gammie et al. | Jun 2008 | A1 |
20080307240 | Dahan et al. | Dec 2008 | A1 |
20090049220 | Conti et al. | Feb 2009 | A1 |
20090054075 | Boejer et al. | Feb 2009 | A1 |
20090070621 | Yanagi | Mar 2009 | A1 |
20090204831 | Cousson et al. | Aug 2009 | A1 |
20090204835 | Smith et al. | Aug 2009 | A1 |
20090210831 | Correale et al. | Aug 2009 | A1 |
20090256607 | Smith | Oct 2009 | A1 |
20090271167 | Zhu et al. | Oct 2009 | A1 |
20100064271 | Chen | Mar 2010 | A1 |
20100308895 | Koushanfar | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
2457170 | Aug 2009 | GB |
2004102623 | Nov 2004 | WO |
Entry |
---|
Application as Filed; U.S. Appl. No. 12/029,442; Brian Smith; et al., filed Feb. 11, 2008. |
Application as Filed; U.S. Appl. No. 12/029,404; Brian Smith; et al., filed Feb. 11, 2008. |
Application as Filed; U.S. Appl. No. 12/101,055; Tom Verveure; filed Apr. 10, 2008. |
IEEE Journal of Solid-State Circuits, vol. 42, No. 1 Jan. 2007. |
Number | Date | Country | |
---|---|---|---|
20090256607 A1 | Oct 2009 | US |