System and method for adjusting trip points within a storage device

Information

  • Patent Grant
  • 9263156
  • Patent Number
    9,263,156
  • Date Filed
    Thursday, December 19, 2013
    11 years ago
  • Date Issued
    Tuesday, February 16, 2016
    9 years ago
Abstract
The embodiments described herein include a method and device for adjusting trip points within a storage device. The method includes: obtaining one or more configuration parameters; and based on the one or more configuration parameters, determining a trip voltage. The method also includes comparing the trip voltage with an input voltage. The method further includes triggering a power fail condition in accordance with a determination that the input voltage is less than the trip voltage.
Description
TECHNICAL FIELD

The disclosed embodiments relate generally to memory systems, and in particular, to adjusting trip points in a storage device.


BACKGROUND

Semiconductor memory devices, including flash memory, typically utilize memory cells to store data as an electrical value, such as an electrical charge or voltage. A flash memory cell, for example, includes a single transistor with a floating gate that is used to store a charge representative of a data value. Flash memory is a non-volatile data storage device that can be electrically erased and reprogrammed. More generally, non-volatile memory (e.g., flash memory, as well as other types of non-volatile memory implemented using any of a variety of technologies) retains stored information even when not powered, as opposed to volatile memory, which requires power to maintain the stored information.


SUMMARY

Various implementations of systems, methods and devices within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the attributes described herein. Without limiting the scope of the appended claims, after considering this disclosure, and particularly after considering the section entitled “Detailed Description” one will understand how the aspects of various implementations are used to adjust trip points for triggering a power fail process based on one or more configuration parameters (e.g., input or supply voltage) of a data storage device.





BRIEF DESCRIPTION OF THE DRAWINGS

So that the present disclosure can be understood in greater detail, a more particular description may be had by reference to the features of various implementations, some of which are illustrated in the appended drawings. The appended drawings, however, merely illustrate the more pertinent features of the present disclosure and are therefore not to be considered limiting, for the description may admit to other effective features.



FIG. 1 is a block diagram illustrating an implementation of a data storage system in accordance with some embodiments.



FIG. 2A is a block diagram illustrating an implementation of a supervisory controller in accordance with some embodiments.



FIG. 2B is a block diagram illustrating an implementation of a storage controller in accordance with some embodiments.



FIG. 2C is a block diagram illustrating an implementation of a non-volatile memory (NVM) controller in accordance with some embodiments.



FIG. 3 is a block diagram illustrating a portion of a data storage device in accordance with some embodiments.



FIG. 4A is a block diagram illustrating an implementation of a portion of voltage monitoring circuitry in accordance with some embodiments.



FIG. 4B is a block diagram illustrating an implementation of a portion of voltage monitoring circuitry in accordance with some embodiments.



FIG. 5 is a block diagram illustrating an implementation of a data hardening module in accordance with some embodiments.



FIGS. 6A-6C illustrate a flowchart representation of a method of adjusting trip points in a data storage device in accordance with some embodiments.





In accordance with common practice the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method or device. Finally, like reference numerals may be used to denote like features throughout the specification and figures.


DETAILED DESCRIPTION

The various implementations described herein include systems, methods and/or devices for adjusting trip points that trigger a power fail process based on one or more configuration parameters of a storage device. For example, in accordance with some embodiments, in a storage device configured to be compatible with an interface standard (e.g., DDR3) that allows a host system to provide one of a plurality of supply voltages to the storage device, the storage device is configured to adjust trip points that trigger a power fail process in accordance with the supply voltage(s) provided by the host system.


More specifically, some embodiments include a method of adjusting trip points in a storage device. In some embodiments, the method is performed within a storage device operatively coupled with a host system. The method includes: obtaining one or more configuration parameters; and based on the one or more configuration parameters, determining a trip voltage. The method also includes comparing the trip voltage with an input voltage. The method further includes triggering a power fail condition in accordance with a determination that the input voltage is less than the trip voltage (or, in some circumstances, greater than the trip voltage).


Some embodiments include a storage device comprising: a host interface configured to couple the storage device with a host system; a supervisory controller with one or more processors and memory; a power fail module for detecting a power fail condition; and a plurality of controller for managing one or more non-volatile memory devices. The storage device is configured to perform the operations of any of the methods described herein.


Some embodiments include a storage device comprising: a host interface configured to couple the storage device with a host system; and means for performing the operations of any of the methods described herein.


Some embodiments include a non-transitory computer readable storage medium, storing one or more programs for execution by one or more processors of a storage device, the one or more programs including instructions for performing the operations any of the methods described herein.


Numerous details are described herein in order to provide a thorough understanding of the example implementations illustrated in the accompanying drawings. However, some embodiments may be practiced without many of the specific details, and the scope of the claims is only limited by those features and aspects specifically recited in the claims. Furthermore, well-known methods, components, and circuits have not been described in exhaustive detail so as not to unnecessarily obscure more pertinent aspects of the implementations described herein.



FIG. 1 is a block diagram illustrating an implementation of data storage system 100 in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, data storage system 100 includes storage device 120, which includes host interface 122, supervisory controller 124, power fail module 126, power control 127, storage controller 128 (sometimes called a memory controller), one or more non-volatile memory (NVM) controllers 130 (e.g., NVM controller 130-1 through NVM controller 130-m), and non-volatile memory (NVM) (e.g., one or more NVM device(s) 140, 142 such as one or more flash memory devices), and is used in conjunction with computer system 110.


Computer system 110 is coupled with storage device 120 through data connections 101. However, in some embodiments, computer system 110 includes storage device 120 as a component and/or sub-system. Computer system 110 may be any suitable computing device, such as a personal computer, a workstation, a computer server, or any other computing device. Computer system 110 is sometimes called a host or host system. In some embodiments, computer system 110 includes one or more processors, one or more types of memory, optionally includes a display and/or other user interface components such as a keyboard, a touch screen display, a mouse, a track-pad, a digital camera and/or any number of supplemental devices to add functionality. Further, in some embodiments, computer system 110 sends one or more host commands (e.g., read commands and/or write commands) on control line 111 to storage device 120. In some embodiments, computer system 110 is a server system, such as a server system in a data center, and does not have a display and other user interface components.


In some embodiments, storage device 120 includes a single NVM device while in other implementations storage device 120 includes a plurality of NVM devices. In some embodiments, NVM devices 140, 142 include NAND-type flash memory or NOR-type flash memory. Further, in some embodiments, NVM controller 130 is a solid-state drive (SSD) controller. However, one or more other types of storage media may be included in accordance with aspects of a wide variety of implementations. In some embodiments, storage device 120 is or includes a dual in-line memory module (DIMM) device. In some embodiments, storage device 120 is compatible with a DIMM memory slot. For example, storage device 120 is compatible with a 240-pin DIMM memory slot and is compatible with signaling in accordance with a DDR3 interface specification.


In some embodiments, storage device 120 includes NVM devices 140, 142 (e.g., NVM devices 140-1 through 140-n and NVM devices 142-1 through 142-k) and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m). In some embodiments, each NVM controller of NVM controllers 130 include one or more processing units (sometimes called CPUs or processors) configured to execute instructions in one or more programs (e.g., in NVM controllers 130). In some embodiments, the one or more processors are shared by one or more components within, and in some cases, beyond the function of NVM controllers 130. NVM devices 140, 142 are coupled with NVM controllers 130 through connections that typically convey commands in addition to data, and, optionally, convey metadata, error correction information and/or other information in addition to data values to be stored in NVM devices 140, 142 and data values read from NVM devices 140, 142. For example, NVM devices 140, 142 can be configured for enterprise storage suitable for applications such as cloud computing, or for caching data stored (or to be stored) in secondary storage, such as hard disk drives. Additionally and/or alternatively, flash memory (e.g., NVM devices 140, 142) can also be configured for relatively smaller-scale applications such as personal flash drives or hard-disk replacements for personal, laptop and tablet computers. Although flash memory devices and flash controllers are used as an example here, in some embodiments storage device 120 includes other non-volatile memory device(s) and corresponding non-volatile storage controller(s).


In some embodiments, storage device 120 also includes host interface 122, supervisory controller 124, power fail module 126, power control 127, and storage controller 128. Storage device 120 may include various additional features that have not been illustrated for the sake of brevity and so as not to obscure more pertinent features of the example implementations disclosed herein, and a different arrangement of features may be possible. Host interface 122 provides an interface to computer system 110 through data connections 101.


Supervisory controller 124 is coupled with host interface 122, power fail module 126, power control 127, storage controller 128, and NVM controllers 130 (connection not shown) in order to coordinate the operation of these components, including supervising and controlling functions such as power up, power down, data hardening, charging energy storage device(s), data logging, and other aspects of managing functions on storage device 120. Supervisory controller 124 is coupled with host interface 122 via serial presence detect (SPD) bus 154 and receives supply voltage line VSPD 156 from the host interface 122. VSPD 156 is a standardized voltage (e.g., typically 3.3 V). Serial presence detect (SPD) refers to a standardized way to automatically access information about a computer memory module (e.g., storage device 120). In some embodiments, if the memory module has a failure, the failure can be communicated with a host system (e.g., computer system 110) via SPD bus 154.


Power fail module 126 is coupled with host interface 122, supervisory controller 124, and power control 127. Power fail module 126 is configured to monitor one or more input voltages (e.g., Vdd 152 and, optionally, VSPD 156) provided to storage device 120 by a host system (e.g., computer system 110). In response to detecting a power fail condition (e.g., an under or over voltage event) as to an input voltage, power fail module 126 is configured to provide a PFAIL signal to supervisory controller 124 and, in some circumstances, discharge an energy storage device to provide power to storage controller 128 and NVM controllers 130. For a more detailed description of power fail module 126, see the description of FIGS. 3-5. In response to receiving the PFAIL signal indicating a power fail condition from power fail module 126, supervisory controller 124 performs one or more operations of a power fail process including, but not limited to, signaling the power fail condition to a plurality of controllers on storage device 120 (e.g., storage controller 128 and NVM controllers 130) via control lines 162.


Power control 127 is coupled with supervisory controller 124, power fail module 126, storage controller 128, and NVM controllers 130 (connection not shown) in order to provide power to these components. In some embodiments, power control 127 includes one or more voltage regulators controlled by supervisory controller 124 via control line 162. Furthermore, in some implementations, power control 127 is configured to remove power from a specified NVM controller 130 in response to a command from supervisory controller 124 via control line 162.


Storage controller 128 is coupled with host interface 122, supervisory controller 124, power control 127, and NVM controllers 130. In some embodiments, during a write operation, storage controller 128 receives data via data bus 158 from computer system 110 through host interface 122 and during a read operation, storage controller 128 sends data to computer system 110 through host interface 122 via data bus 158. Further, host interface 122 provides additional data, signals, voltages, and/or other information needed for communication between storage controller 128 and computer system 110. In some embodiments, storage controller 128 and host interface 122 use a defined interface standard for communication, such as double data rate type three synchronous dynamic random access memory (DDR3). In some embodiments, storage controller 128 and NVM controllers 130 use a defined interface standard for communication, such as serial advance technology attachment (SATA). In some other implementations, the device interface used by storage controller 128 to communicate with NVM controllers 130 is SAS (serial attached SCSI), or other storage interface. In some embodiments, storage controller 128 maps DDR interface commands from the host system (e.g., computer system 1120) to SATA or SAS interface commands for the plurality of controllers (e.g., storage controller 128 and NVM controllers 130).



FIG. 2A is a block diagram illustrating an implementation of supervisory controller 124 in accordance with some embodiments. Supervisory controller 124 includes one or more processors 202 (sometimes called CPUs or processing units) for executing modules, programs and/or instructions stored in memory 206 and thereby performing processing operations, serial presence detect (SPD) module 205 (e.g., non-volatile memory) storing information related to storage device 120 (e.g., a serial number, memory type, supported communication protocol, etc.), memory 206, optionally a digital-to-analog converter (DAC) 204 for converting digital values to an analog signal (e.g., a portion of an integrated or partially integrated DAC/ADC), and one or more communication buses 208 for interconnecting these components. Communication buses 208, optionally, include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Supervisory controller 124 is coupled with host interface 122, power fail module 126, power control 127, storage controller 128, and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m) by communication buses 208.


Memory 206 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 206, optionally, includes one or more storage devices remotely located from processor(s) 202. Memory 206, or alternately the non-volatile memory device(s) within memory 206, comprises a non-transitory computer readable storage medium. In some embodiments, memory 206, or the computer readable storage medium of memory 206, stores the following programs, modules, and data structures, or a subset or superset thereof:

    • obtaining module 210 for obtaining one or more configuration parameters, including:
      • optionally, a receiving module 212 for receiving one or more configuration parameters from computer system 110; and
      • sampling module 214 for sampling Vdd 152 (connection not shown) to determine one or more configuration parameters (e.g., a default input voltage (Vdd) supplied by computer system 110);
    • determination module 216 for determining a trip voltage (sometimes called a “trip point”) based on the one or more configuration parameters, optionally including:
      • selection module 218 for selecting a trip voltage from trip voltage table 220 based on the one or more configuration parameters, where trip voltage table 220 includes a plurality of predefined trip voltages;
    • optionally, a modification module 222 for modifying one or more timing parameters 224 based on the one or more configuration parameters and for modifying one or more trip voltages in trip voltage table 220 in response to a request from computer system 110;
    • power fail module 226 for performing one or more operations of a power fail process in response to detecting (or the triggering of) a power fail condition, including:
      • latching module 228 for latching, unlatching, or forcing the power fail condition (e.g., by controlling latching mechanism 412, FIG. 4A);
      • power switch module 230 for controlling Vswitched 160 (FIGS. 1 and 5);
      • discharge module 232 for discharging an energy storage device 510 (e.g., one or more hold-up capacitors) (see FIG. 5);
      • signal module 234 for signaling a power fail condition to a plurality of controllers on storage device 120 (e.g., storage controller 128 and NVM controllers 130, FIG. 1);
      • power removal module 236 for removing power from the plurality of controllers on storage device 120 (e.g., by controlling power control 127, FIG. 1); and
      • reset module 238 for resetting one or more of the plurality of controllers on storage device 120 (e.g., storage controller 128 and NVM controllers 130, FIG. 1);
    • control module 240 for coordinating the operations of storage device 120, including supervisory, control, and power fail functions; and
    • non-volatile memory 242 for storing information related to the operations of storage device 120, optionally including:
      • event log 244 for storing the time and occurrence of events (e.g., the occurrence of a power fail condition).


Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 206 may store a subset of the modules and data structures identified above. Furthermore, memory 206 may store additional modules and data structures not described above. In some embodiments, the programs, modules, and data structures stored in memory 206, or the computer readable storage medium of memory 206, provide instructions for implementing any of the methods described below with reference to FIGS. 6A-6C.


Although FIG. 2A shows supervisory controller 124, FIG. 2A is intended more as a functional description of the various features which may be present in supervisory controller 124 than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated.



FIG. 2B is a block diagram illustrating an implementation of a storage controller 128 in accordance with some embodiments. Storage controller 128, typically, includes one or more processors 252 (sometimes called CPUs or processing units) for executing modules, programs and/or instructions stored in memory 256 and thereby performing processing operations, memory 256, and one or more communication buses 258 for interconnecting these components. Communication buses 258, optionally, include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Storage controller 128 is coupled with host interface 122, supervisory controller 124, power control 127, and NVM controllers 130 (e.g., NVM controllers 130-1 through 130-m) by communication buses 258.


Memory 256 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 256, optionally, includes one or more storage devices remotely located from processor(s) 252. Memory 256, or alternately the non-volatile memory device(s) within memory 256, comprises a non-transitory computer readable storage medium. In some embodiments, memory 256, or the computer readable storage medium of memory 256, stores the following programs, modules, and data structures, or a subset or superset thereof:

    • interface module 260 for communicating with other components, such as host interface 122, supervisory controller 124, power control 127, and NVM controllers 130;
    • reset module 262 for resetting storage controller 128; and
    • power fail module 264 for performing a power fail operation in response to a signal of a power fail condition from supervisory controller 124.


In some embodiments, the power fail module 264, optionally, includes a transfer module 266 for transferring data held in volatile memory 268 to non-volatile memory.


Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 256 may store a subset of the modules and data structures identified above. Furthermore, memory 256 may store additional modules and data structures not described above.


Although FIG. 2B shows storage controller 128, FIG. 2B is intended more as a functional description of the various features which may be present in storage controller 128 than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated.



FIG. 2C is a block diagram illustrating an implementation of representative NVM controller 130-1 in accordance with some embodiments. NVM controller 130-1 typically includes one or more processors 272 (sometimes called CPUs or processing units) for executing modules, programs and/or instructions stored in memory 276 and thereby performing processing operations, memory 276, and one or more communication buses 278 for interconnecting these components. Communication buses 278 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. NVM controller 130-1 is coupled with supervisory controller 124, power control 127, storage controller 128, and NVM devices 140 (e.g., NVM devices 140-1 through 140-n) by communication buses 278.


Memory 276 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 276, optionally, includes one or more storage devices remotely located from processor(s) 272. Memory 276, or alternately the non-volatile memory device(s) within memory 276, comprises a non-transitory computer readable storage medium. In some embodiments, memory 276, or the computer readable storage medium of memory 276, stores the following programs, modules, and data structures, or a subset or superset thereof:

    • interface module 280 for communicating with other components, such as supervisory controller 124, power control 127, storage controller 128, and NVM devices 140;
    • reset module 282 for resetting NVM controller 130-1; and
    • power fail module 284 for performing a power fail operation in response to a signal of a power fail condition from supervisory controller 124.


In some embodiments, power fail module 284, optionally, includes a transfer module 286 for transferring data held in volatile memory 288 to non-volatile memory.


Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 276 may store a subset of the modules and data structures identified above. Furthermore, memory 276 may store additional modules and data structures not described above.


Although FIG. 2C shows NVM controller 130-1, FIG. 2C is intended more as a functional description of the various features which may be present in NVM controller 130-1 than as a structural schematic of the embodiments described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. Further, although FIG. 2C shows representative NVM controller 130-1, the description of FIG. 2C similarly applies to other NVM controllers (e.g., NVM controllers 130-2 through 130-m) in storage device 120, as shown in FIG. 1.



FIG. 3 is a block diagram illustrating an implementation of a portion of storage device 120 in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, supervisory controller 124 includes one or more processors 202 and DAC 204, and power fail module 126 includes voltage monitoring circuitry 302 and data hardening module 308. In some embodiments, DAC 204 is a component of one or more processors 202. In some embodiments, Vdd 152 is a voltage supplied by the host system (e.g., computer system 110, FIG. 1) and has a target value of 1.5 V or less (e.g., 1.25 V, 1.35 V, or 1.5 V). For example, for a double data rate type three (DDR3) interface specification, the input (or supply) voltage is 1.25 V, 1.35 V or 1.5 V. In some embodiments, VSPD 156 is a voltage supplied by the host system for a serial presence detect (SPD) functionality and has a target value of 3.3 V.


In some embodiments, voltage monitoring circuitry 302 is configured to detect a power fail condition (e.g., an under or over voltage event) as to an input voltage (e.g., Vdd 152 or VSPD 156) supplied by a host system (e.g., computer system 110, FIG. 1) and signal the power fail condition to supervisory controller 124. In some embodiments, voltage monitoring circuitry 302 includes Vdd monitoring circuitry 304 configured to detect an under or over voltage event as to Vdd 152 and VSPD monitoring circuitry 306 configured to detect an under or over voltage event as to VSPD 156. For a more detailed description of Vdd monitoring circuitry 304, see the description of FIG. 4A. For a more detailed description of VSPD monitoring circuitry 306, see the description of FIG. 4B.


In some embodiments, data hardening module 308 is configured to interconnect an energy storage device to provide power to storage controller 128 and NVM controllers 130. For a more detailed description of data hardening module 308, see the description of FIG. 5. For further description of data hardening module 308, see U.S. Provisional Patent Application No. 61/887,910 entitled “Power Sequencing and Data Hardening Circuitry Architecture,” which is herein incorporated by reference.



FIG. 4A is a block diagram illustrating an implementation of a portion of voltage monitoring circuitry 302 (Vdd monitoring circuitry 304) in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, Vdd monitoring circuitry 304 includes reference signal conditioning module 402, input signal conditioning module 404, comparator 406, and transistor 408.


In some embodiments, as shown in FIG. 3, the reference signal is DAC output 312 from supervisory controller 124. For example, supervisory controller 124 or a component thereof (e.g., obtaining module 210, FIG. 2A) obtains one or more configuration parameters including an indication of the default value for Vdd (e.g., 1.25 V, 1.35 V, or 1.5 V) that is supplied to storage device 120 by the host system. In this example, supervisory controller 124 or a component thereof (e.g., determination module 216, FIG. 2A) determines a trip voltage for Vdd by selecting one of a plurality of predefined trip voltages from trip voltage table 220 based on the indication of the default value for Vdd (e.g., included in the one or more configuration parameters). DAC 204 converts the digital value for the trip voltage to an analog value, and supervisory controller 124 provides DAC output 312 to Vdd monitoring circuitry 304.


Referring once again to FIG. 4A, in some embodiments reference signal conditioning module 402 is configured to condition DAC output 312 (sometimes called a “reference signal,” “trip voltage,” or “trip point”) prior to a comparison operation with this reference signal. In some embodiments, the conditioning includes one or more of buffering, filtering, scaling, and level shifting DAC output 312 to produce a reference comparison signal 418. In some embodiments, conditioning module 402 is implemented using well-known circuitry components (e.g., unity gain amplifier, low-pass RC filter, voltage divider, etc.), the exact configuration of which depends on the particular conditioning applied to DAC output 312. For example, the conditioning adjusts the trip voltage so that the full range of DAC values map to the practical range of trip voltages. In some embodiments, Vref 414 is a voltage-supply independent reference voltage supplied by comparator 406 and used by reference signal conditioning module 402 to level shift DAC output 312. For example, DAC output 312 starts as a low value (e.g., 1 V) and is raised to the proper trip voltage (e.g., 1.125 V, 1.215 V, or 1.35 V) by reference signal conditioning module 402.


In some embodiments, input signal conditioning module 404 is configured to condition Vdd 152 (sometimes called an “input signal,” “input voltage,” or “supply voltage”) supplied by the host system prior to a comparison operation with this input signal. In some embodiments, the conditioning includes one or more of buffering, filtering, and scaling Vdd 152 to produce a comparison input signal 416 corresponding to Vdd 152. In some embodiments, input signal conditioning module 404 is implemented using well-known circuitry components (e.g., unity gain amplifier, low-pass RC filter, voltage divider, etc.), the exact configuration of which depends on the particular conditioning applied to the Vdd 152.


In some embodiments, comparator 406 is configured to perform a comparison operation between the conditioned reference signal (e.g., the output of reference signal conditioning module 402) and the conditioned input signal (e.g., the output of input signal conditioning module 404). If the conditioned input signal is less than (or, alternatively, greater than) the conditioned reference signal, comparator 406 is configured to output PFAIL signal 314 to supervisory controller 124 (e.g., logic high). For example, in FIG. 4A, PFAIL signal 314 indicates the occurrence of a power fail condition (e.g., an under or over voltage event) as to Vdd 152. Additionally, comparator 406 is configured to provide hysteresis 410 of the result of the comparison operation for subsequent comparisons (e.g., 3 to 10 mV of feedback). In some embodiments, comparator 406 is also configured to provide Vref 414 to one or more other components of storage device 120 (e.g., supervisory controller 124 and VSPD monitoring circuitry 306).


In some embodiments, latching mechanism 412 is configured to latch, unlatch, or force (e.g., simulate) the power fail condition. In some embodiments, when comparator 406 indicates the occurrence of a power fail condition as to Vdd 152, PFAIL signal 314 (e.g., logic high) is provided to latching mechanism 412. PFAIL signal 314 enables transistor 408 (closed state) which shorts the input signal (e.g., a level adjusted and scaled comparison input signal 416 corresponding to Vdd 152) to ground, which latches the power fail condition.


In addition to having a mechanism for latching the power fail condition, in some embodiments, supervisory controller 124 or a component thereof (e.g., latching module 228, FIG. 2A) is configured to unlatch the power fail condition by providing a PFAIL control signal 316 (e.g., logic low) that disables transistor 408 (open state), which unlatches the power fail condition—by allowing the comparison input signal 416 to reach the comparator 406 without being shorted to ground. In some embodiments, supervisory controller 124 or a component thereof (e.g., latching module 228, FIG. 2A) is also configured to force the power fail condition to occur by providing PFAIL control signal 316 (e.g., logic high) that enables transistor 408 (closed state) which shorts the comparison input signal 416 to ground, which forces the comparator 406 to generate PFAIL signal 314. Furthermore, in some implementations, PFAIL control signal 316 is tristated (e.g., put into a high impedance state) by supervisory controller 124 when supervisory controller 124 is neither unlatching the power fail condition nor forcing a power fail condition, which disables transistor 408 unless PFAIL 314 is asserted (e.g., logic high). For further information concerning forcing or simulating the power fail condition, see U.S. Provisional Patent Application No. 61/903,895, filed Nov. 13, 2013, entitled “Simulated Power Failure and Data Hardening Circuitry Architecture,” which is herein incorporated by reference in its entirety.



FIG. 4B is a block diagram illustrating an implementation of a portion of voltage monitoring circuitry 302 (VSPD monitoring circuitry 306) in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, VSPD monitoring circuitry 306 includes reference signal conditioning module 422, input signal conditioning module 424, and comparator 426. In some embodiments, the reference signal is Vref 414 from comparator 406 of Vdd monitoring circuitry 304, as shown in FIG. 4A. For example, Vref 414 is a voltage-supply independent reference voltage (e.g., a predetermined voltage such as 1.23 V). In some embodiments, the input signal is VSPD 156 supplied by the host system (e.g., with a target voltage of 3.3V).


In some embodiments, reference signal conditioning module 422 is configured to condition Vref 414 (sometimes called a “reference signal,” “trip voltage,” or “trip point”) prior to a comparison operation with this reference signal. In some embodiments, the conditioning includes one or more of buffering and filtering Vref 414 with a plurality of well-known circuitry components (e.g., unity gain amplifier, low-pass RC filter, etc.) to produce a conditioned Vref comparison signal 430. In some embodiments, input signal conditioning module 424 is configured to condition VSPD 156 (sometimes called an “input signal,” “input voltage,” or “supply voltage”) supplied by the host system prior to a comparison operation with this input signal. In some embodiments, the conditioning includes one or more of buffering, filtering, and scaling VSPD 156 with a plurality of well-known circuitry components (e.g., unity gain amplifier, low-pass RC filter, voltage divider, etc.) to produce a conditioned VSPD comparison signal 432. For example, if Vref 414 is 1.23 V and the target voltage for VSPD 156 is 3.3 V, input signal conditioning module 424 includes a low-pass RC filter to filter out any ripples or glitches in VSPD 156 and, also, a voltage divider to scale down VSPD 156 (e.g., by approximately 73% or a factor of 2.7).


In some embodiments, comparator 426 is configured to perform a comparison operation between the conditioned reference signal 430 (e.g., the output of reference signal conditioning module 422) and the conditioned input signal 432 (e.g., the output of input signal conditioning module 424). If the conditioned input signal 432 is less than (or, alternatively, greater than) the conditioned reference signal 430, comparator 426 is configured to output PFAIL signal 314 to supervisory controller 124 (e.g., logic high). For example, in FIG. 4B, PFAIL signal 314 indicates the occurrence of a power fail condition (e.g., an under or over voltage event) as to VSPD 156. Additionally, comparator 426 is configured to provide hysteresis 428 of the result of the comparison operation for subsequent comparisons.



FIG. 5 is a block diagram illustrating an implementation of data hardening module 308 in accordance with some embodiments. While some example features are illustrated, various other features have not been illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, as a non-limiting example, data hardening module 308 includes transistors 502 and 504, boost circuitry 506, energy storage device 510, keeper circuitry 512, and logic block 514.


In some embodiments, Vholdup 508 is a boosted voltage, higher than Vdd 152, and has a target value of 5.7 V. In some embodiments, Vholdup 508 is used to charge an energy storage device 510 (e.g., one or more hold-up capacitors). Further, in some embodiments, only one of transistors 502, 504 is enabled at any one time. In some embodiments, data hardening circuit 308's energy storage device 510 stores, immediately prior to a power fail condition being detected, at least approximately 30 to 70 mJ of energy per NVM controller 130 in storage device 120.


In some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) monitors and manages the functionality of data hardening module 308. For example, in response to receiving PFAIL signal 314 from voltage monitoring circuitry 302 indicating the power fail condition, supervisory controller 124 or a component thereof (e.g., processor 202) is configured to perform one or more operations of a power fail process including controlling transistors 502 and 504 so that Vswitched 160 is the voltage from energy storage device 510, and energy storage device 510 is used (sometimes said to be “discharged”) to provide power to storage device 120.


In some embodiments, during regular operation of storage device 120, Vdd 152 is used to supply power to storage device 120. However, during the power fail process, energy storage device 510 is used to provide power to storage device 120. In some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) controls transistors 502 and 504 via control lines 318 to control Vswitched 160 to be voltage from Vdd 152 (e.g., during regular operation) or voltage from energy storage device 510 (e.g., during the power fail process). For example, during regular operation of storage device 120, transistor 502 is turned on (e.g., to complete the connection between Vdd 152 and Vswitched 160) and transistor 504 is turned off (e.g., to disable the connection between energy storage device 510 and Vswitched 160) so that Vdd 152 is used to supply power to storage device 120. However, during the power fail process, transistor 502 is turned off (e.g., to disable the connection between Vdd 152 and Vswitched 160) and transistor 504 is turned on (e.g., to enable the connection between energy storage device 510 and Vswitched 160) so that energy storage device 510 is used to provide power to storage device 120. Although a single energy storage device 510 is shown in FIG. 5, any energy storage device, including one or more capacitors, one or more inductors, or one or more other passive elements that store energy, may be used to store energy to be used during the power fail process.


In some embodiments, energy storage device 510 is charged using Vholdup 508, a voltage higher than Vdd 152. In some embodiments, Vdd 152 is boosted up to Vholdup 508 using boost circuitry 506 (e.g., 1.35 V or 1.5 V is boosted up to 5.7 V). In some embodiments, boost circuitry 506 is controlled and enabled by supervisory controller 124 (e.g., via processor 202).


Further, in some embodiments, Vswitched 160 is used as an input to keeper circuitry 512, which along with VSPD 156 provides power to processor 202. During the power fail process, Vswitched 160 is provided via keeper circuitry 512 to processor 202 so as to provide power to processor 202. In some embodiments, VSPD 156 provides power to keeper circuitry 512. In some embodiments, logic block 514 (e.g., OR or XOR) determines which of keeper circuitry 512 or VSPD 156 provides power to supervisory controller 124 (e.g., processor 202).


Furthermore, in some embodiments, during a power up sequence, VSPD 156 is provided to storage device 120 before Vdd 152 is provided to storage device 120. This allows devices in storage device 120 (e.g., supervisory controller 124 and, in turn, processor 202) to operate before main power Vdd 152 is provided to storage device 120. In some embodiments, supervisory controller 124 or a component thereof (e.g., processor 202) includes one or more connections 162 used to monitor and control other functions within storage device 120.



FIGS. 6A-6C illustrate a flowchart representation of a method 600 of adjusting trip points (e.g., a trip voltage that triggers a power fail process) in a data storage device in accordance with some embodiments. At least in some embodiments, method 600 is performed by a storage device (e.g., storage device 120, FIG. 1) or one or more components of the storage device (e.g., supervisory controller 124, power fail module 126, storage controller 128, and/or NVM controllers 130, FIG. 1), where the storage device is operatively coupled with a host system (e.g., computer system 110, FIG. 1). In some embodiments, method 600 is governed by instructions that are stored in a non-transitory computer readable storage medium and that are executed by one or more processors of a device, such as the one or more processors 202 of supervisory controller 124, the one or more processors 252 of storage controller 128, and/or the one or more processors 272 of NVM controllers 130, as shown in FIGS. 2A-2C.


A storage device (e.g., storage device 120, FIG. 1) obtains (602) one or more configuration parameters. In some embodiments, supervisory controller 124 or a component thereof (e.g., obtaining module 210, FIG. 2A) is configured to obtain one or more configuration parameters associated with storage device 120.


In some embodiments, the one or more configuration parameters include (604) an indication of a default input voltage and configuration information of the storage device. For example, the one or more configuration parameters include an indication of the default input voltage (e.g., Vdd) supplied by the host system (e.g., computer system 110, FIG. 1) to storage device 120 or voltage class of storage device 120 (e.g., 1.25 V, 1.35 V, or 1.5 V) and information associated with the current configuration of storage device 120.


In some embodiments, information identifying the default input voltage is obtained (606) from the host system. In some embodiments, supervisory controller 124 or a component thereof (e.g., receiving module 212, FIG. 2A) is configured to receive an indication of the default input (or supply) voltage (e.g., Vdd) from the host system (e.g., computer system 110, FIG. 1). For example, receiving module 212 receives an indication of the default input voltage via SPD Bus 154 from the host system.


In some embodiments, the storage device samples (608) the input voltage to determine the default input voltage. In some embodiments, supervisory controller 124 or a component thereof (e.g., sampling module 214, FIG. 2A) is configured to sample the input voltage (e.g., Vdd) to determine the default input voltage. For example, sampling module 214 samples Vdd upon power-on and/or restart of storage device 120 to determine the default input voltage. In another example, sampling module 214 determines the default input voltage by averaging a plurality of sample measurements of Vdd.


In some embodiments, the storage device modifies (610) one or more timing parameters associated with a communication bus that operatively couples the storage device and the host system based on the one or more configuration parameters. In some embodiments, supervisory controller 124 or a component thereof (e.g., modification module 222, FIG. 2A) is configured to modify one or more timing parameters 224 stored in non-volatile memory 242 based on the one or more configuration parameters. For example, modification module 222 modifies skew and timing parameters associated with the communication bus (e.g., DDR3) that operatively couples storage device 120 and the host system (e.g., computer system 110, FIG. 1) based on the default input voltage (e.g., Vdd) provided to storage device 120 or voltage class of storage device 120 (e.g., 1.25 V, 1.35 V, or 1.5 V).


The storage device determines (612) a trip voltage based on the one or more configuration parameters. In some embodiments, supervisory controller 124 or a component thereof (e.g., determination module 216, FIG. 2A) is configured to determine a trip voltage based on the one or more configuration parameters. For example, determination module 216 determines the trip voltage based on the default input voltage (e.g., Vdd) provided to storage device 120 or voltage class of storage device 120 (e.g., 1.25 V, 1.35 V, or 1.5 V). In some embodiments, the trip voltage varies depending on the target value of the voltage. For example, if the target value of the input voltage is 1.5 V, the trip voltage may be 1.5 V minus 5 percent (i.e., 1.425 V) or minus 10 percent (i.e., 1.35 V).


In some embodiments, determining the trip voltage includes selecting (614) one of a plurality of stored predefined trip voltages based on the one or more configuration parameters. In some embodiments, supervisory controller or a component thereof (e.g., selection module 218, FIG. 2A) is configured to select a trip voltage from a plurality of predefined trip voltages stored in trip voltage table 220 based on the one or more configuration parameters. In some embodiments, trip voltage table 220 includes a predefined trip voltage for each of a plurality potential default input voltages supplied by a host system or voltage classes of storage device 120 (e.g., 1.25 V, 1.35 V, or 1.5 V). For example, if the one or more configuration parameters indicate that the default input voltage (e.g., Vdd) is 1.5 V, selection module 218 selects a trip voltage from trip voltage table 220 that corresponds to a default input voltage of 1.5 V.


In some embodiments, prior to the comparing, the storage device conditions (616) the trip voltage by buffering the trip voltage and, after the buffering, level shifting and scaling the trip voltage. In some embodiments, after determining the trip voltage, an analog reference signal (e.g., DAC output 312, FIGS. 3 and 4A) corresponding to the determined trip voltage is generated by supervisory controller 124 or a component thereof (e.g., DAC 204, FIGS. 2A and 3) and input to power fail module 126 or a component thereof (e.g., Vdd monitoring circuitry 304, FIG. 4A). Prior to comparing the reference signal (e.g., DAC output 312, FIGS. 3 and 4A) with an input signal (e.g., Vdd 152), reference signal conditioning module 402 is configured to condition the reference signal. In some embodiments, the conditioning includes one or more of buffering, filtering, scaling, and level shifting to adjust the trip voltage so that the full range of DAC values map to the practical range of voltage trip points. For example (circuit details not shown in Figures), first, a unity gain operation amplifier buffers the reference signal (e.g., DAC output 312) to stabilize the impedance; second, a filter filters noise out of the reference signal; third, the reference signal is scaled; and fourth, the reference signal is level shifted by utilizing a voltage-supply independent voltage source (e.g., Vref 414).


In some embodiments, prior to comparing, the storage device conditions (618) the input voltage (e.g., Vdd 152 or VSPD 156) by scaling the input voltage and filtering the input voltage. Prior to comparing the reference signal (e.g., DAC output 312 or Vref 414) with the input signal (e.g., Vdd 152 or VSPD 156), power fail module 126 or a component thereof conditions the input signal by scaling and filtering the input signal. For example, in FIG. 4A, Vdd 152 (e.g., the input signal) is conditioned by input signal conditioning module 404. In this example, Vdd 152 is scaled by voltage divider circuitry and noise is filtered out of Vdd 152 with a low-pass (e.g., RC) filter (circuit details not shown in Figures). In another example, in FIG. 4B, VSPD 156 (e.g., the input signal) is conditioned by input signal conditioning module 424. In this example, VSPD 156 is scaled down to the value of Vref 414 and noise is filtered out of VSPD 156 with a low-pass (e.g., RC) filter.


The storage device compares (620) the trip voltage to an input voltage. For example, in FIG. 4A, comparator 306 performs a comparison operation between the conditioned reference signal (e.g., the output of reference signal conditioning module 402) and the conditioned input signal (e.g., the output of input signal conditioning module 404).


The storage device triggers (622) the power fail condition in accordance with a determination that the input voltage is less than the trip voltage. For example, in FIG. 4A, if the conditioned input signal is less than the conditioned reference signal, comparator 406 is configured to output PFAIL signal 314 to supervisory controller 124 (e.g., logic high). In this example, in FIG. 4A, PFAIL signal 314 indicates the occurrence of a power fail condition (e.g., an under voltage event) as to Vdd 152. For example, in response to receiving PFAIL signal 314 from comparator 406 indicating the power fail condition as to Vdd 152, supervisory controller 124 or a component thereof (e.g., processor 202) is configured to perform one or more operations of a power fail process including signaling the power fail condition to a plurality of controllers on storage device 120 (e.g., storage controller 128 and NVM controllers 130, FIG. 1) via control lines 162, controlling transistors 502, 504 so that Vswitched 160 is the voltage from energy storage device 510.


In another example, in response to detecting a power fail condition (e.g., an under or over voltage event) as to Vdd 152, Vdd Monitoring Circuitry 304 or a component thereof (e.g., comparator 406) asserts output PFAIL signal 314 to the plurality of controllers in storage device 120 (e.g., storage controller 128 and NVM controllers 130, FIG. 1). Continuing with this example, Vdd Monitoring Circuitry 304 also controls transistors 502, 504 so that Vswitched 160 is the voltage from energy storage device 510. In this example, Vdd Monitoring Circuitry 304 directly asserts the PFAIL signal so as to reduce the latency of the PFAIL transition which provides power to the controllers via energy storage device 510.


In some embodiments, the trip voltage is a first trip voltage and the input voltage is a supply voltage provided by the host system, the storage device compares (624) a second trip voltage to a serial presence detect (SPD) voltage provided by the host system, and, in accordance with a determination that the SPD voltage is less than the second trip voltage, the storage device triggers the power fail condition. In some embodiments, the second trip voltage is not determined because VSPD is a standardized value (e.g., 3.3 V). For example, in FIG. 4B, comparator 426 performs a comparison operation between the conditioned reference signal (e.g., the output of reference signal conditioning module 422) and the conditioned input signal (e.g., the output of input signal conditioning module 424). In this example, in FIG. 4B, if the conditioned input signal is less than the conditioned reference signal, comparator 426 is configured to output PFAIL signal 314 to supervisory controller 124 (e.g., logic high). In this example, in FIG. 4B, PFAIL signal 314 indicates the occurrence of a power fail condition as to VSPD 156. For example, optionally, in some circumstances, in response to receiving PFAIL signal 314 from comparator 426 indicating the power fail condition as to VSPD 156, supervisory controller 124 or a component thereof (e.g., processor 202) is configured to perform one or more operations of a power fail process including signaling the power fail condition to a plurality of controllers on storage device 120 (e.g., storage controller 128 and NVM controllers 130, FIG. 1) via control lines 162 and causing back up power to be provided to supervisory controller 124 (e.g., Vswitched 160 via keeper circuitry 512, as shown in FIG. 5).


In another example, in response to detecting a power fail condition (e.g., an under or over voltage event) as to VSPD 156, VSPD Monitoring Circuitry 306 or a component thereof (e.g., comparator 426) asserts output PFAIL signal 314 to the plurality of controllers in storage device 120 (e.g., storage controller 128 and NVM controllers 130, FIG. 1). Continuing with this example, VSPD Monitoring Circuitry 306 also controls transistors 502, 504 so that Vswitched 160 is the voltage from energy storage device 510. In this example, VSPD Monitoring Circuitry 306 directly asserts the PFAIL signal so as to reduce the latency of the PFAIL transition which provides power to the controllers via energy storage device 510.


In some embodiments, comparing the second trip voltage to the SPD voltage provided by the host system includes comparing (626) a voltage-supply independent voltage with a voltage derived from the SPD voltage. For example, Vref 414 is a voltage-supply independent voltage provided by comparator 406, as shown in FIG. 4A. For example, in FIG. 4B, comparator 426 compares Vref 414 with a scaled version of VSPD 156. In this example, if Vref 414 is 1.23 V and the target voltage for VSPD 156 is 3.3 V, input signal conditioning module 424 is configured to scale down VSPD 156 (e.g., by approximately 73% or a factor of 2.7).


In some embodiments, the storage device provides (628) hysteresis with respect to subsequent comparisons using feedback of the comparison of the trip voltage with the input voltage. For example, in FIG. 4A, comparator 406 is configured to provide hysteresis 410 of the result of the comparison operation of DAC output 312 and Vdd 152 for subsequent comparisons (e.g., 3 to 10 mV of feedback). In another example, in FIG. 4B, comparator 426 is configured to provide hysteresis 428 of the result of the comparison operation of Vref 414 and VSPD 156 for subsequent comparisons.


In some embodiments, the storage device latches (630) the power fail condition. For example, in FIG. 4A, when comparator 406 indicates the occurrence of a power fail condition as to Vdd 152, PFAIL signal 314 (e.g., logic high) is provided to latching mechanism 412. In this example, PFAIL signal 314 enables transistor 408 (closed state) which shorts the input signal (e.g., Vdd 152) to ground and, in turn, latches the power fail condition.


In some embodiments, after latching the power fail condition and completion of a power fail process, the storage device clears (632) the latched power fail condition. In some embodiments, supervisory controller 124 or a component thereof (e.g., latching module 228, FIG. 2A) is configured to unlatch the power condition upon completion of the power fail process by providing a PFAIL control signal 316 (e.g., logic low) that disables transistor 408 (open state) which opens the circuit from Vdd 152 to ground and, in turn, unlatches the power fail condition. In some embodiments, the power fail process is complete once the plurality of controllers (e.g., storage controller 128 and NVM controller 130, FIG. 1) has transferred data held in volatile memory to non-volatile memory.


In some embodiments, the storage device triggers (634) the power fail condition in accordance with a condition determined by execution of one or more procedures by a controller within the storage device. In some embodiments, supervisory controller 124 or a component thereof (e.g., latching module 228, FIG. 2A) is configured to force the power fail condition by providing PFAIL control signal 316 (e.g., logic high) that enables transistor 408 (closed state) which shorts the input signal (e.g., Vdd 152) to ground and, in turn, forces the power fail condition to occur. For example, the forced or simulated power fail condition is utilized to test one or more operations of the power fail process.


In some embodiments, the storage device modifies (636) one of a plurality of stored predefined trip voltages in response to a command from the host system. In some embodiments, supervisory controller 124 or a component thereof (e.g., modification module 222, FIG. 2A) is configured to modify one or more trip voltages stored in trip voltage table 220 in response to a request or command from the host system (e.g., computer system 110). In some embodiments, supervisory controller 124 is configured to receive commands (or requests) from the host system (e.g., computer system 110) via SPD bus 154. In some embodiments, storage device 120 includes a data controller coupled between host interface 122 and storage controller 128 that is configured to control the input and output of data to the one or more NVM devices. For example, the data controller is configured to receive commands (or requests) from the host system (e.g., computer system 110) and communicate the command to supervisory controller 124 (e.g., via a semaphore register or I2C).


It will be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first NVM controller could be termed a second NVM controller, and, similarly, a second NVM controller could be termed a first NVM controller, without changing the meaning of the description, so long as all occurrences of the “first NVM controller” are renamed consistently and all occurrences of the “second NVM controller” are renamed consistently. The first NVM controller and the second NVM controller are both NVM controllers, but they are not the same NVM controller.


The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. As used in the description of the embodiments and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.


As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined [that a stated condition precedent is true]” or “if [a stated condition precedent is true]” or “when [a stated condition precedent is true]” may be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.


The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain principles of operation and practical applications, to thereby enable others skilled in the art.

Claims
  • 1. A method of triggering a power fail condition in a storage device operatively coupled with a host system, comprising:
  • 2. The method of claim 1, wherein the input voltage is a supply voltage provided by the host system, the method further comprising: comparing a second trip voltage to a serial presence detect (SPD) voltage provided by the host system, wherein the SPD voltage is distinct from the supply voltage provided by the host system; andin accordance with a determination that the SPD voltage is less than the second trip voltage, triggering the power fail condition.
  • 3. The method of claim 2, wherein comparing the second trip voltage to the SPD voltage provided by the host system includes comparing a voltage-supply independent voltage with a voltage derived from the SPD voltage.
  • 4. The method of claim 1, wherein the one or more configuration parameters include configuration information of the storage device.
  • 5. The method of claim 1, wherein information identifying the default input voltage is obtained from the host system.
  • 6. The method of claim 1, further comprising: sampling the input voltage to determine the default input voltage.
  • 7. The method of claim 1, further comprising: based on the one or more configuration parameters, modifying one or more timing parameters associated with a communication bus that operatively couples the storage device and the host system.
  • 8. The method of claim 1, wherein determining the first trip voltage includes: selecting one of a plurality of predefined trip voltages from the table of predefined trip voltage as the first trip voltage based on the one or more configuration parameters.
  • 9. The method of claim 1, further comprising: in response to a modification command from the host system, modifying a predefined trip voltage within the table of predefined trip voltages.
  • 10. The method of claim 1, further comprising: prior to the comparing, conditioning the first trip voltage including: buffering the first trip voltage; andafter the buffering, level shifting and scaling the first trip voltage.
  • 11. The method of claim 1, further comprising: prior to the comparing, conditioning the input voltage including: scaling the input voltage; andfiltering the input voltage.
  • 12. The method of claim 1, further comprising: providing hysteresis with respect to subsequent comparisons using feedback of the comparison of the first trip voltage with the input voltage.
  • 13. The method of claim 1, further comprising: latching the power fail condition.
  • 14. The method of claim 13, further comprising: after latching the power fail condition and completion of a power fail process, clearing the latched power fail condition.
  • 15. The method of claim 1, further comprising: triggering the power fail condition in accordance with a condition determined by execution of one or more procedures by a controller within the storage device.
  • 16. A storage device, comprising: an interface for operatively coupling the storage device with a host system;a supervisory controller with one or more processors and memory;a power fail module for detecting a power fail condition; anda plurality of controllers for managing one or more non-volatile memory devices, the storage device configured to: obtain one or more configuration parameters, the one or more configuration parameters including an indication of a default input voltage;access a table of predefined trip voltages;based on the one or more configuration parameters and the table of predefined trip voltages, determine a first trip voltage;compare the first trip voltage with an input voltage; andin accordance with a determination that the input voltage is less than the first trip voltage, trigger the power fail condition.
  • 17. The storage device of claim 16, wherein the input voltage is a supply voltage provided by the host system, and the storage device is further configured to: compare a second trip voltage to a serial presence detect (SPD) voltage provided by the host system, wherein the SPD voltage is distinct from the supply voltage provided by the host systemin accordance with a determination that the SPD voltage is less than the second trip voltage, trigger the power fail condition.
  • 18. The storage device of claim 17, wherein comparing the second trip voltage to the SPD voltage provided by the host system includes comparing a voltage-supply independent voltage with a voltage derived from the SPD voltage.
  • 19. The storage device of claim 16, wherein the one or more configuration parameters include configuration information of the storage device.
  • 20. A non-transitory computer readable storage medium, storing one or more programs for execution by one or more processors of a storage device, the one or more programs including instructions that when executed by the one or more processors cause the storage device to: obtain one or more configuration parameters, the one or more configuration parameters including an indication of a default input voltage;access a table of predefined trip voltages;based on the one or more configuration parameters and the table of predefined trip voltages, determine a first trip voltage;compare the first trip voltage with an input voltage; andin accordance with a determination that the input voltage is less than the first trip voltage, trigger the power fail condition.
  • 21. The non-transitory computer readable storage medium of claim 20, wherein the input voltage is a supply voltage provided by the host system, and the one or more programs further include instructions, that when executed by the one or more processors cause the storage device to: compare a second trip voltage to a serial presence detect (SPD) voltage provided by the host system, wherein the SPD voltage is distinct from the supply voltage provided by the host system; andin accordance with a determination that the SPD voltage is less than the second trip voltage, trigger the power fail condition.
  • 22. The non-transitory computer readable storage medium of claim 21, wherein comparing the second trip voltage to the SPD voltage provided by the host system includes comparing a voltage-supply independent voltage with a voltage derived from the SPD voltage.
  • 23. The non-transitory computer readable storage medium of claim 20, wherein the one or more configuration parameters include configuration information of the storage device.
RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 61/901,266, filed Nov. 7, 2013, which is hereby incorporated by reference in its entirety.

US Referenced Citations (379)
Number Name Date Kind
4173737 Skerlos et al. Nov 1979 A
4888750 Kryder et al. Dec 1989 A
4916652 Schwarz et al. Apr 1990 A
5129089 Nielsen Jul 1992 A
5270979 Harari et al. Dec 1993 A
5329491 Brown et al. Jul 1994 A
5381528 Brunelle Jan 1995 A
5519847 Fandrich et al. May 1996 A
5530705 Malone, Sr. Jun 1996 A
5537555 Landry et al. Jul 1996 A
5551003 Mattson et al. Aug 1996 A
5636342 Jeffries Jun 1997 A
5657332 Auclair et al. Aug 1997 A
5666114 Brodie et al. Sep 1997 A
5708849 Coke et al. Jan 1998 A
5765185 Lambrache et al. Jun 1998 A
5890193 Chevallier Mar 1999 A
5936884 Hasbun et al. Aug 1999 A
5943692 Marberg et al. Aug 1999 A
5982664 Watanabe Nov 1999 A
6000006 Bruce et al. Dec 1999 A
6006345 Berry, Jr. Dec 1999 A
6016560 Wada et al. Jan 2000 A
6018304 Bessios Jan 2000 A
6044472 Crohas Mar 2000 A
6070074 Perahia et al. May 2000 A
6119250 Nishimura et al. Sep 2000 A
6138261 Wilcoxson et al. Oct 2000 A
6182264 Ott Jan 2001 B1
6192092 Dizon et al. Feb 2001 B1
6295592 Jeddeloh Sep 2001 B1
6311263 Barlow et al. Oct 2001 B1
6408394 Vander Kamp et al. Jun 2002 B1
6412042 Paterson et al. Jun 2002 B1
6442076 Roohparvar Aug 2002 B1
6449625 Wang Sep 2002 B1
6484224 Robins et al. Nov 2002 B1
6516437 Van Stralen et al. Feb 2003 B1
6564285 Mills et al. May 2003 B1
6678788 O'Connell Jan 2004 B1
6757768 Potter et al. Jun 2004 B1
6775792 Ulrich et al. Aug 2004 B2
6810440 Micalizzi, Jr. et al. Oct 2004 B2
6836808 Bunce et al. Dec 2004 B2
6836815 Purcell et al. Dec 2004 B1
6842436 Moeller Jan 2005 B2
6865650 Morley et al. Mar 2005 B1
6871257 Conley et al. Mar 2005 B2
6895464 Chow et al. May 2005 B2
6966006 Pacheco et al. Nov 2005 B2
6978343 Ichiriu Dec 2005 B1
6980985 Amer-Yahia et al. Dec 2005 B1
6981205 Fukushima et al. Dec 2005 B2
6988171 Beardsley et al. Jan 2006 B2
7020017 Chen et al. Mar 2006 B2
7028165 Roth et al. Apr 2006 B2
7032123 Kane et al. Apr 2006 B2
7043505 Teague et al. May 2006 B1
7076598 Wang Jul 2006 B2
7100002 Shrader Aug 2006 B2
7102860 Wenzel Sep 2006 B2
7111293 Hersh et al. Sep 2006 B1
7126873 See et al. Oct 2006 B2
7133282 Sone Nov 2006 B2
7162678 Saliba Jan 2007 B2
7173852 Gorobets et al. Feb 2007 B2
7184446 Rashid et al. Feb 2007 B2
7275170 Suzuki Sep 2007 B2
7328377 Lewis et al. Feb 2008 B1
7516292 Kimura et al. Apr 2009 B2
7523157 Aguilar, Jr. et al. Apr 2009 B2
7527466 Simmons May 2009 B2
7529466 Takahashi May 2009 B2
7533214 Aasheim et al. May 2009 B2
7546478 Kubo et al. Jun 2009 B2
7566987 Black et al. Jul 2009 B2
7571277 Mizushima Aug 2009 B2
7574554 Tanaka et al. Aug 2009 B2
7596643 Merry, Jr. et al. Sep 2009 B2
7681106 Jarrar et al. Mar 2010 B2
7685494 Varnica et al. Mar 2010 B1
7707481 Kirschner et al. Apr 2010 B2
7761655 Mizushima et al. Jul 2010 B2
7765454 Passint Jul 2010 B2
7774390 Shin Aug 2010 B2
7840762 Oh et al. Nov 2010 B2
7870326 Shin et al. Jan 2011 B2
7890818 Kong et al. Feb 2011 B2
7913022 Baxter Mar 2011 B1
7925960 Ho et al. Apr 2011 B2
7934052 Prins et al. Apr 2011 B2
7945825 Cohen et al. May 2011 B2
7954041 Hong et al. May 2011 B2
7971112 Murata Jun 2011 B2
7974368 Shieh et al. Jul 2011 B2
7978516 Olbrich et al. Jul 2011 B2
7996642 Smith Aug 2011 B1
8006161 Lestable et al. Aug 2011 B2
8032724 Smith Oct 2011 B1
8041884 Chang Oct 2011 B2
8042011 Nicolaidis et al. Oct 2011 B2
8069390 Lin Nov 2011 B2
8190967 Hong et al. May 2012 B2
8250380 Guyot Aug 2012 B2
8254181 Hwang et al. Aug 2012 B2
8259506 Sommer et al. Sep 2012 B1
8312349 Reche et al. Nov 2012 B2
8412985 Bowers et al. Apr 2013 B1
8429436 Fillingim et al. Apr 2013 B2
8438459 Cho et al. May 2013 B2
8453022 Katz May 2013 B2
8627117 Johnston Jan 2014 B2
8634248 Sprouse et al. Jan 2014 B1
8694854 Dar et al. Apr 2014 B1
8724789 Altberg et al. May 2014 B2
8885434 Kumar Nov 2014 B2
8898373 Kang et al. Nov 2014 B1
8910030 Goel Dec 2014 B2
8923066 Subramanian et al. Dec 2014 B1
9128690 Lotzenburger et al. Sep 2015 B2
20010050824 Buch Dec 2001 A1
20020024846 Kawahara et al. Feb 2002 A1
20020036515 Eldridge et al. Mar 2002 A1
20020083299 Van Huben et al. Jun 2002 A1
20020122334 Lee et al. Sep 2002 A1
20020152305 Jackson et al. Oct 2002 A1
20020162075 Talagala et al. Oct 2002 A1
20020165896 Kim Nov 2002 A1
20030041299 Kanazawa et al. Feb 2003 A1
20030043829 Rashid et al. Mar 2003 A1
20030088805 Majni et al. May 2003 A1
20030093628 Matter et al. May 2003 A1
20030163594 Aasheim et al. Aug 2003 A1
20030163629 Conley et al. Aug 2003 A1
20030188045 Jacobson Oct 2003 A1
20030189856 Cho et al. Oct 2003 A1
20030198100 Matsushita et al. Oct 2003 A1
20030204341 Guliani et al. Oct 2003 A1
20030212719 Yasuda et al. Nov 2003 A1
20040024957 Lin et al. Feb 2004 A1
20040024963 Talagala et al. Feb 2004 A1
20040057575 Zhang et al. Mar 2004 A1
20040062157 Kawabe Apr 2004 A1
20040073829 Olarig Apr 2004 A1
20040114265 Talbert Jun 2004 A1
20040143710 Walmsley Jul 2004 A1
20040148561 Shen et al. Jul 2004 A1
20040153902 Machado et al. Aug 2004 A1
20040167898 Margolus et al. Aug 2004 A1
20040181734 Saliba Sep 2004 A1
20040199714 Estakhri et al. Oct 2004 A1
20040237018 Riley Nov 2004 A1
20050060456 Shrader et al. Mar 2005 A1
20050060501 Shrader Mar 2005 A1
20050073884 Gonzalez et al. Apr 2005 A1
20050108588 Yuan May 2005 A1
20050114587 Chou et al. May 2005 A1
20050172065 Keays Aug 2005 A1
20050172207 Radke et al. Aug 2005 A1
20050193161 Lee et al. Sep 2005 A1
20050201148 Chen et al. Sep 2005 A1
20050231765 So et al. Oct 2005 A1
20050249013 Janzen et al. Nov 2005 A1
20050251617 Sinclair et al. Nov 2005 A1
20050257120 Gorobets et al. Nov 2005 A1
20050273560 Hulbert et al. Dec 2005 A1
20050289314 Adusumilli et al. Dec 2005 A1
20060010174 Nguyen et al. Jan 2006 A1
20060039196 Gorobets et al. Feb 2006 A1
20060039227 Lai et al. Feb 2006 A1
20060053246 Lee Mar 2006 A1
20060085671 Majni et al. Apr 2006 A1
20060087893 Nishihara et al. Apr 2006 A1
20060107181 Dave et al. May 2006 A1
20060136570 Pandya Jun 2006 A1
20060136681 Jain et al. Jun 2006 A1
20060156177 Kottapalli et al. Jul 2006 A1
20060195650 Su et al. Aug 2006 A1
20060244049 Yaoi et al. Nov 2006 A1
20060259528 Dussud et al. Nov 2006 A1
20060291301 Ziegelmayer Dec 2006 A1
20070011413 Nonaka et al. Jan 2007 A1
20070058446 Hwang et al. Mar 2007 A1
20070061597 Holtzman et al. Mar 2007 A1
20070076479 Kim et al. Apr 2007 A1
20070081408 Kwon et al. Apr 2007 A1
20070083697 Birrell et al. Apr 2007 A1
20070088716 Brumme et al. Apr 2007 A1
20070091677 Lasser et al. Apr 2007 A1
20070113019 Beukema et al. May 2007 A1
20070133312 Roohparvar Jun 2007 A1
20070147113 Mokhlesi et al. Jun 2007 A1
20070150790 Gross et al. Jun 2007 A1
20070156842 Vermeulen et al. Jul 2007 A1
20070157064 Falik et al. Jul 2007 A1
20070174579 Shin Jul 2007 A1
20070180188 Fujibayashi et al. Aug 2007 A1
20070180346 Murin Aug 2007 A1
20070201274 Yu et al. Aug 2007 A1
20070208901 Purcell et al. Sep 2007 A1
20070234143 Kim Oct 2007 A1
20070245061 Harriman Oct 2007 A1
20070245099 Gray et al. Oct 2007 A1
20070263442 Cornwall et al. Nov 2007 A1
20070277036 Chamberlain et al. Nov 2007 A1
20070279988 Nguyen Dec 2007 A1
20070291556 Kamei Dec 2007 A1
20070294496 Goss et al. Dec 2007 A1
20070300130 Gorobets Dec 2007 A1
20080013390 Zipprich-Rasch Jan 2008 A1
20080019182 Yanagidaira et al. Jan 2008 A1
20080022163 Tanaka et al. Jan 2008 A1
20080028275 Chen et al. Jan 2008 A1
20080043871 Latouche et al. Feb 2008 A1
20080052446 Lasser et al. Feb 2008 A1
20080056005 Aritome Mar 2008 A1
20080071971 Kim et al. Mar 2008 A1
20080077841 Gonzalez et al. Mar 2008 A1
20080077937 Shin et al. Mar 2008 A1
20080086677 Yang et al. Apr 2008 A1
20080112226 Mokhlesi May 2008 A1
20080141043 Flynn et al. Jun 2008 A1
20080144371 Yeh et al. Jun 2008 A1
20080147714 Breternitz et al. Jun 2008 A1
20080147964 Chow et al. Jun 2008 A1
20080147998 Jeong Jun 2008 A1
20080148124 Zhang et al. Jun 2008 A1
20080163030 Lee Jul 2008 A1
20080168191 Biran et al. Jul 2008 A1
20080168319 Lee et al. Jul 2008 A1
20080170460 Oh et al. Jul 2008 A1
20080229000 Kim Sep 2008 A1
20080229003 Mizushima et al. Sep 2008 A1
20080229176 Arnez et al. Sep 2008 A1
20080270680 Chang Oct 2008 A1
20080282128 Lee et al. Nov 2008 A1
20080285351 Shlick et al. Nov 2008 A1
20080313132 Hao et al. Dec 2008 A1
20090003058 Kang Jan 2009 A1
20090019216 Yamada et al. Jan 2009 A1
20090031083 Willis et al. Jan 2009 A1
20090037652 Yu et al. Feb 2009 A1
20090070608 Kobayashi Mar 2009 A1
20090116283 Ha et al. May 2009 A1
20090125671 Flynn et al. May 2009 A1
20090144598 Yoon et al. Jun 2009 A1
20090168525 Olbrich et al. Jul 2009 A1
20090172258 Olbrich et al. Jul 2009 A1
20090172259 Prins et al. Jul 2009 A1
20090172260 Olbrich et al. Jul 2009 A1
20090172261 Prins et al. Jul 2009 A1
20090172262 Olbrich et al. Jul 2009 A1
20090172308 Prins et al. Jul 2009 A1
20090172335 Kulkarni et al. Jul 2009 A1
20090172499 Olbrich et al. Jul 2009 A1
20090193058 Reid Jul 2009 A1
20090207660 Hwang et al. Aug 2009 A1
20090213649 Takahashi et al. Aug 2009 A1
20090222708 Yamaga Sep 2009 A1
20090228761 Perlmutter et al. Sep 2009 A1
20090249160 Gao et al. Oct 2009 A1
20090268521 Ueno et al. Oct 2009 A1
20090292972 Seol et al. Nov 2009 A1
20090296466 Kim et al. Dec 2009 A1
20090296486 Kim et al. Dec 2009 A1
20090310422 Edahiro et al. Dec 2009 A1
20090319864 Shrader Dec 2009 A1
20100002506 Cho et al. Jan 2010 A1
20100008175 Sweere et al. Jan 2010 A1
20100011261 Cagno et al. Jan 2010 A1
20100020620 Kim et al. Jan 2010 A1
20100037012 Yano et al. Feb 2010 A1
20100061151 Miwa et al. Mar 2010 A1
20100091535 Sommer et al. Apr 2010 A1
20100103737 Park Apr 2010 A1
20100110798 Hoei et al. May 2010 A1
20100118608 Song et al. May 2010 A1
20100138592 Cheon Jun 2010 A1
20100153616 Garratt Jun 2010 A1
20100161936 Royer et al. Jun 2010 A1
20100174959 No et al. Jul 2010 A1
20100199125 Reche Aug 2010 A1
20100199138 Rho Aug 2010 A1
20100202196 Lee et al. Aug 2010 A1
20100208521 Kim et al. Aug 2010 A1
20100262889 Bains Oct 2010 A1
20100281207 Miller et al. Nov 2010 A1
20100281342 Chang et al. Nov 2010 A1
20100332858 Trantham et al. Dec 2010 A1
20110010514 Benhase et al. Jan 2011 A1
20110051513 Shen et al. Mar 2011 A1
20110066597 Mashtizadeh et al. Mar 2011 A1
20110078407 Lewis Mar 2011 A1
20110083060 Sakurada et al. Apr 2011 A1
20110099460 Dusija et al. Apr 2011 A1
20110113281 Zhang et al. May 2011 A1
20110122691 Sprouse May 2011 A1
20110131444 Buch et al. Jun 2011 A1
20110173378 Filor et al. Jul 2011 A1
20110179249 Hsiao Jul 2011 A1
20110199825 Han et al. Aug 2011 A1
20110205823 Hemink et al. Aug 2011 A1
20110213920 Frost et al. Sep 2011 A1
20110222342 Yoon et al. Sep 2011 A1
20110225346 Goss et al. Sep 2011 A1
20110228601 Olbrich et al. Sep 2011 A1
20110231600 Tanaka et al. Sep 2011 A1
20110264843 Haines et al. Oct 2011 A1
20110271040 Kamizono Nov 2011 A1
20110283119 Szu et al. Nov 2011 A1
20120023144 Rub Jan 2012 A1
20120054414 Tsai et al. Mar 2012 A1
20120063234 Shiga et al. Mar 2012 A1
20120072639 Goss et al. Mar 2012 A1
20120096217 Son et al. Apr 2012 A1
20120110250 Sabbag et al. May 2012 A1
20120151124 Baek et al. Jun 2012 A1
20120151253 Horn Jun 2012 A1
20120151294 Yoo et al. Jun 2012 A1
20120173797 Shen Jul 2012 A1
20120185750 Hayami Jul 2012 A1
20120195126 Roohparvar Aug 2012 A1
20120203951 Wood et al. Aug 2012 A1
20120216079 Fai et al. Aug 2012 A1
20120233391 Frost et al. Sep 2012 A1
20120236658 Byom et al. Sep 2012 A1
20120239858 Melik-Martirosian Sep 2012 A1
20120239976 Cometti et al. Sep 2012 A1
20120259863 Bodwin et al. Oct 2012 A1
20120275466 Bhadra et al. Nov 2012 A1
20120278564 Goss et al. Nov 2012 A1
20120284574 Avila et al. Nov 2012 A1
20120284587 Yu et al. Nov 2012 A1
20130007073 Varma Jan 2013 A1
20130007343 Rub et al. Jan 2013 A1
20130007543 Goss et al. Jan 2013 A1
20130024735 Chung et al. Jan 2013 A1
20130031438 Hu et al. Jan 2013 A1
20130036418 Yadappanavar et al. Feb 2013 A1
20130047045 Hu et al. Feb 2013 A1
20130073924 D'Abreu et al. Mar 2013 A1
20130079942 Smola et al. Mar 2013 A1
20130086131 Hunt et al. Apr 2013 A1
20130086132 Hunt et al. Apr 2013 A1
20130094288 Patapoutian et al. Apr 2013 A1
20130111279 Jeon et al. May 2013 A1
20130111298 Seroff et al. May 2013 A1
20130121084 Jeon et al. May 2013 A1
20130124888 Tanaka et al. May 2013 A1
20130128666 Avila et al. May 2013 A1
20130132652 Wood et al. May 2013 A1
20130176784 Cometti et al. Jul 2013 A1
20130179646 Okubo et al. Jul 2013 A1
20130191601 Peterson et al. Jul 2013 A1
20130194874 Mu et al. Aug 2013 A1
20130232289 Zhong et al. Sep 2013 A1
20130258738 Barkon et al. Oct 2013 A1
20130265838 Li Oct 2013 A1
20130282955 Parker et al. Oct 2013 A1
20130290611 Biederman et al. Oct 2013 A1
20130301373 Tam Nov 2013 A1
20130304980 Nachimuthu et al. Nov 2013 A1
20130343131 Wu et al. Dec 2013 A1
20140013188 Wu et al. Jan 2014 A1
20140063905 Ahn et al. Mar 2014 A1
20140075133 Li et al. Mar 2014 A1
20140082261 Cohen et al. Mar 2014 A1
20140082456 Liu Mar 2014 A1
20140095775 Talagala et al. Apr 2014 A1
20140122818 Hayasaka et al. May 2014 A1
20140136883 Cohen May 2014 A1
20140136927 Li et al. May 2014 A1
20140143505 Sim et al. May 2014 A1
20140201596 Baum et al. Jul 2014 A1
20140223084 Lee et al. Aug 2014 A1
20140258755 Stenfort Sep 2014 A1
20140269090 Flynn et al. Sep 2014 A1
20140359381 Takeuchi et al. Dec 2014 A1
20150153799 Lucas et al. Jun 2015 A1
Foreign Referenced Citations (17)
Number Date Country
1 299 800 Apr 2003 EP
1465203 Oct 2004 EP
1 990 921 Nov 2008 EP
2 386 958 Nov 2011 EP
2 620 946 Jul 2013 EP
2002-532806 Oct 2002 JP
WO 2007036834 Apr 2007 WO
WO 2007080586 Jul 2007 WO
WO 2008075292 Jun 2008 WO
WO 2008121553 Oct 2008 WO
WO 2008121577 Oct 2008 WO
WO 2009028281 Mar 2009 WO
WO 2009032945 Mar 2009 WO
WO 2009058140 May 2009 WO
WO 2009084724 Jul 2009 WO
WO 2009134576 Nov 2009 WO
WO 2011024015 Mar 2011 WO
Non-Patent Literature Citations (59)
Entry
Barr, Introduction to Watchdog Timers, Oct. 2001, 3 pgs.
Canim, Buffered Bloom ilters on Solid State Storage, ADMS*10, Singapore, Sep. 13-17, 2010, 8 pgs.
Kang, A Multi-Channel Architecture for High-Performance NAND Flash-Based Storage System, J. Syst. Archit., 53, 9, Sep. 2007, 15 pgs.
Kim, A Space-Efficient Flash Translation Layer for CompactFlash Systems, May 2002, 10 pgs.
Lu, A Forest-structured Bloom Filter with Flash Memory, MSST 2011, Denver, CO, May 23-27, 2011, article, 6 pgs.
Lu, A Forest-structured Bloom Filter with Flash Memory, MSST 2011, Denver, CO, May 23-27, 2011, presentation slides, 25 pgs.
McLean, Information Technology—AT Attachment with Packet Interface Extension, Aug. 19, 1998, 339 pgs.
Park, A High Performance Controller for NAND Flash-Based Solid State Disk (NSSD), Feb. 12-16, 2006, 4 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88133, Mar. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88136, Mar. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88146, Feb. 26, 2009, 10 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88154, Feb. 27, 2009, 8 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88164, Feb. 13, 2009, 6 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88206, Feb. 18, 2009, 8 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88217, Feb. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88229, Feb. 13, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88232, Feb. 19, 2009, 8 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US08/88236, Feb. 19, 2009, 7 pgs.
Pliant Technology, International Search Report / Written Opinion, PCT/US2011/028637, Oct. 27, 2011, 11 pgs.
Pliant Technology, Supplementary ESR, 08866997.3, Feb. 23, 2012, 6 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/042764, Aug. 31, 2012, 12 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/042771, Mar. 4, 2013, 14 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/042775, Sep. 26, 2012, 8 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/059447, Jun. 6, 2013, 12 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/059453, Jun. 6, 2013, 12 pgs.
Sandisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/059459, Feb. 14, 2013, 9 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/065914, May 23, 2013, 7 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/065916, Apr. 5, 2013, 7 pgs.
SanDisk Enterprise IP LLC, International Search Report / Written Opinion, PCT/US2012/065919, Jun. 17, 2013, 8 pgs.
SanDisk Enterprise IP LLC, Notification of the Decision to Grant a Patent Right for Patent for Invention, CN 200880127623.8, Jul. 4, 2013, 1 pg.
SanDisk Enterprise IP LLC, Office Action, CN 200880127623.8, Apr. 18, 2012, 12 pgs.
SanDisk Enterprise IP LLC, Office Action, CN 200880127623.8, Dec. 31, 2012, 9 pgs.
SanDisk Enterprise IP LLC, Office Action, JP 2010-540863, Jul. 24, 2012, 3 pgs.
Watchdog Timer and Power Savin Modes, Microchip Technology Inc., 2005, 14 pgs.
Zeidman, 1999 Verilog Designer's Library, 9 pgs.
Invitation to Pay Additional Fees dated Feb. 13, 2015, received in International Patent Application No. PCT/US2014/063949, which corresponds to U.S. Appl. No. 14/135,433, 6 pages (Delpapa).
International Search Report and Written Opinion dated Jan. 21, 2015, received in International Application No. PCT/US2014/059746, which corresponds to U.S. Appl. No. 14/137,511, 13 pages (Dancho).
lntemational Search Report and Written Opinion dated Feb. 18, 2015, received in International Appication No. PCT/US2014/066921, which corresponds to U.S. Appl. No. 14/135,260, 13 pages (Fitzpatrick).
Ashkenazi et al., “Platform independent overall security architecture in multi-processor system-on-chip integrated circuits for use in mobile phones and handheld devices,” ScienceDirect, Computers and Electrical Engineering 33 (2007), 18 pages.
Lee et al., “A Semi-Preemptive Garbage Collector for Solid State Drives,” Apr. 2011, IEEE, pp. 12-21.
Office Action dated Feb. 17, 2015, received in Chinese Patent Application No. 201210334987.1, which corresponds to U.S. Appl. No. 12/082,207, 9 pages (Prins).
International Search Report and Written Opinion dated May 4, 2015, received in International Patent Application No. PCT/US2014/065987, which corresponds to U.S. Appl. No. 14/135,400, 12 pages (George).
International Search Report and Written Opinion dated Mar. 17, 2015, received in International Patent Application No. PCT/US2014/067467, which corresponds to U.S. Appl. No. 14/135,420, 13 pages (Lucas).
International Search Report and Written Opinion dated Apr. 20, 2015, received in International Patent Application No. PCT/US2014/063949, which corresponds to U.S. Appl. No. 14/135,433, 21 pages (Delpapa).
International Search Report and Written Opinion dated Mar. 9, 2015, received in International Patent Application No. PCT/US2014/059747, which corresponds to U.S. Appl. No. 14/137,440, 9 pages (Fitzpatrick).
International Search Report and Written Opinion dated Jul. 25, 2014, received in International Patent Application No. PCT/US2014/029453, which corresponds to U.S. Appl. No. 13/963,444, 9 pages (Frayer).
International Search Report and Written Opinion dated Mar. 7, 2014, received in International Patent Application No. PCT/US2013/074772, which corresponds to U.S. Appl. No. 13/831,218, 10 pages (George).
International Search Report and Written Opinion dated Mar. 24, 2014, received in International Patent Application No. PCT/US2013/074777, which corresponds to U.S. Appl. No. 13/831,308, 10 pages (George).
International Search Report and Written Opinion dated Mar. 7, 2014, received in International Patent Application No. PCT/US2013/074779, which corresponds to U.S. Appl. No. 13/831,374, 8 pages (George).
Bayer, “Prefix B-Trees”, IP.COM Journal, IP.COM Inc., West Henrietta, NY, Mar. 30, 2007, 29 pages.
Bhattacharjee et al., “Efficient Index Compression in DB2 LUW”, IBM Research Report, Jun. 23, 2009, http://domino.research.ibm.com/library/cyberdig.nsf/papers/40B2C45876D0D747852575E100620CE7/$File/rc24815.pdf, 13 pages.
Oracle, “Oracle9i: Database Concepts”, Jul. 2001, http://docs.oracle.com/cd/A91202—01/901—doc/server.901/288856.pdf, 49 pages.
International Search Report and Written Opinion dated Jun. 8, 2015, received in International Patent Application No. PCT/US2015/018252, which corresponds to U.S. Appl. No. 14/339,072, 9 pages (Busch).
International Search Report and Written Opinion dated Jun. 2, 2015, received in International Patent Application No. PCT/US2015/018255, which corresponds to U.S. Appl. No. 14/336,967, 14 pages (Chander).
International Search Report and Written Opinion dated Jun. 30, 2015, received in International Patent Application No. PCT/US2015/023927, which corresponds to U.S. Appl. No. 14/454,687, 11 pages (Kadayam).
International Search Report and Written Opinion dated Jul. 23, 2015, received in International Patent Application No. PCT/US2015/030850, which corresponds to U.S. Appl. No. 14/298,843, 12 pages (Ellis).
Office Action dated Dec. 8, 2014, received in Chinese Patent Application No. 201180021660.2, which corresponds to U.S. Appl. No. 12/726,200, 7 pages (Olbrich).
Office Action dated Jul. 31, 2015, received in Chinese Patent Application No. 201180021660.2, which corresponds to U.S. Appl. No. 12/726,200, 9 pages (Olbrich).
International Search Report and Written Opinion dated Sep. 14, 2015, received in International Patent Application No. PCT/US2015/036807, which corresponds to U.S. Appl. No. 14/311,152, 9 pages (Higgins).
Related Publications (1)
Number Date Country
20150127999 A1 May 2015 US
Provisional Applications (1)
Number Date Country
61901266 Nov 2013 US