Patent Grant
9653079
Technical Field
Embodiments disclosed herein are related to the field of mobile devices and, more particularly, to voice/audio control of mobile devices.
Description of the Related Art
Mobile devices have become ubiquitous. Mobile devices may include any electronic device that is designed to operate on portable power (e.g. a battery) and to be easily carried by a user. Mobile devices may include cell phones, “smart” phones, personal digital assistants (PDAs) such as the iTouch™, entertainment devices such as the iPod™ and MP3 players, laptop computers, net top computers, tablet devices such as the iPad™ and Windows® based tablets, etc. Most of these devices include wireless connectivity (e.g. WiFi, cell connection, etc.) and thus can be used as an information source in addition to providing various local applications that can be run on the device directly.
Mobile devices can be controlled through a user interface such as a touch screen, a keyboard that is part of the device or connected to the device, various pointing devices (e.g. mice, touchpads, etc.), etc. More recently, voice control has started to become more common. For example, some of Apple's i-devices (iPhone™, iPad™, etc.) have adopted voice control via the Siri™ application. The user can pick up the device, press and hold a button, and wait for Siri™ to respond. When Siri™ responds, the user can verbally ask a question or provide a command, which Siri™ will interpret and attempt to satisfy. The act of holding down the button until Siri™ responds serves to wake up the device (if it is in an idle state), initialize the operating system, and activate the Siri™ application so that it is ready to accept input.
Some mobile devices have begun to implement a limited voice command activation function when the device is idle. A device can be idle if it appears to the user to be “off” (even though the user knows the device is on because it may accept an electronic communication such as an email, a phone call, or a text message). The idle device generally does not have the display screen turned on, and many internal components can be powered down and need to be initialized for full function of the device. In mobile devices with the limited voice command activation function, the user may say a key word or phrase to cause the device to turn “on” and accept further voice control. For example, one such phrase is “hey Google now” used for Android smart phones.
With the limited command activation, the user must pause after uttering the key phrase and await a visual and/or audio indication that the device is ready for further input. While the device is idle, the device has a microphone turned on and is listening with a discrete digital signal processor (DSP) for the key word/phrase. Once the key word/phrase has been recognized, the DSP may signal the rest of the device to initialize (or boot) and then respond to the user when ready. The delay between uttering the key word/phrase and then the desired question/command makes the interface unwieldy. Therefore, the limited command activation is only a small improvement over picking up the device and pressing/holding the button as described above.
In an embodiment, an integrated circuit (e.g. a system on a chip, or SOC) may include one or more central processing units (CPUs), a memory controller, and a circuit configured to remain powered on when the rest of the SOC is powered down. The circuit may be configured to receive audio samples corresponding to sound sensed by a microphone, and further configured to match those audio samples against a predetermined pattern to detect a possible command from a user of the device that includes the SOC. The predetermined pattern may represent the user's voice uttering a key word or phrase, for example. The circuit may operate according to a first clock during the time that the rest of the SOC is powered down. The first clock may be a low power clock, and may have various characteristics that are lower power and lower performance than other clocks (e.g. high phase noise, a duty cycle that is not very symmetrical, high jitter, etc.). In response to detecting the predetermined pattern in the samples, the circuit may cause the memory controller and processors to power up so that audio samples may be stored in the memory to which the memory controller is coupled and processed by the processors. During the power up process, a second clock having one or more better characteristics than the first clock may become available. The circuit may switch to the second clock while preserving the samples. In an embodiment, the circuit may lose or corrupt fewer than a threshold number of samples. The threshold number of samples may be few enough that the speech recognition implemented in the system is capable of accurately recognizing the phrase uttered by the user. For example, up to 4 or 5 samples may be lost/corrupted while still permitting correct recognition. In an embodiment, at most one sample may be lost, thus meeting the threshold. In another embodiment, no samples may be lost.
The following detailed description makes reference to the accompanying drawings, which are now briefly described.
While embodiments described in this disclosure may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the embodiments to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the appended claims. The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description. As used throughout this application, the word “may” is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including, but not limited to.
Various units, circuits, or other components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the unit/circuit/component can be configured to perform the task even when the unit/circuit/component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits and/or memory storing program instructions executable to implement the operation. The memory can include volatile memory such as static or dynamic random access memory and/or nonvolatile memory such as optical or magnetic disk storage, flash memory, programmable read-only memories, etc. Similarly, various units/circuits/components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a unit/circuit/component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation for that unit/circuit/component.
This specification includes references to “one embodiment” or “an embodiment.” The appearances of the phrases “in one embodiment” or “in an embodiment” do not necessarily refer to the same embodiment, although embodiments that include any combination of the features are generally contemplated, unless expressly disclaimed herein. Particular features, structures, or characteristics may be combined in any suitable manner consistent with this disclosure.
Turning now to
As implied by the name, the components of the SOC 10 may be integrated onto a single semiconductor substrate as an integrated circuit “chip.” In some embodiments, the components may be implemented on two or more discrete chips in a system. Additionally, various components may be integrated on any integrated circuit (i.e. it need not be an SOC). However, the SOC 10 will be used as an example herein. In the illustrated embodiment, the components of the SOC 10 include a central processing unit (CPU) complex 14, peripheral components 18A-18B (more briefly, “peripherals”), a memory controller 22, an audio filter circuit 24, a power manager circuit (PMGR) 28, an on-chip oscillator 36, a phase-lock loop (PLL) 38, and a communication fabric 27. The components 14, 18A-18B, 22, 24, and 28 may all be coupled to the communication fabric 27. The memory controller 22 may be coupled to the memory 12 during use. Similarly, the peripheral 18A may be an interface unit (IFU) coupled to the audio codec 16 during use, which is further coupled to the audio sensors 26 during use. The IFU 18A is further coupled to the audio filter circuit 24. The oscillator 36 and the PLL 38 are coupled to the audio filter circuit 24, and the PLL 38 may be coupled to a remainder of the SOC 10 as well.
The device 5 may be any type of portable electronic device, such as a cell phone, a smart phone, a PDA, a laptop computer, a net top computer, a tablet device, an entertainment device, etc. In some embodiments, the device 5 may be a non-portable electronic device such as a desktop computer as well. Such non-portable devices may also benefit from the audio device control features described herein.
During times that the device 5 is idle, portions of the SOC 10 may be powered down. Particularly, the CPU complex 14, the memory controller 22, the peripheral 18B, the interconnect 27, the PLL 38, and a portion of the PMGR 28 may be powered down. If the device 5 is idle but not completely powered down, on the other hand, the audio filter circuit 24 may remain powered, as may the IFU 18A and the oscillator 36. Components external to the SOC 10 may be powered up or down as desired when the device 5 is idle. Particularly, the memory 12 may remain powered and thus capable of retaining the data stored therein. In an embodiment in which the memory 12 is a DRAM of one of various types, the memory 12 may be placed in self-refresh mode to retain the stored data during times that the device 5 is idle.
The PLL 38 and the oscillator 36 may each be a clock source in the illustrated embodiment, providing the clocks for the digital logic in the SOC 10. The PLL 38 may be a clock source during operation when portions of the SOC 10 besides the audio filter circuit 24, the IFU 18A, and the oscillator 36 are powered on. The PLL 38 may provide a high performance, high quality clock to the audio filter circuit 24. The PLL 38 may also provide high performance, high quality clocks to other parts of the SOC 10. One or more clocks may be provided, and in some cases clocks to different components in the SOC 10 may have different frequencies. The PLL 38 may thus be multiple PLLs, or various clock dividers/multipliers may be used to generate the clocks from a PLL, or any combination of PLLs and clock dividers/multipliers may be used. On the other hand, during idle times when portions of the SOC 10 are powered down, the oscillator 36 may provide a low power clock to the audio filter circuit 24. The oscillator 36 may be a relatively simple, low power circuit such as a ring oscillator. The oscillator 36 may be powered during the idle times and also at times that other components of the SOC 10 are powered up, or may be powered off when other components are powered up (since the PLL 38 may be providing the clock during such times).
Generally, a clock may be viewed as higher or lower quality or performance based on its closeness to an ideal clock. An ideal clock may be a square wave having a fixed frequency and 50% duty cycle. The fixed frequency may be selectable, but may be invariant with regard to noise, temperature, voltage variation, etc. In other words, the frequency may be certain and the rising and falling edges may be invariant from clock cycle to clock cycle. Real clocks differ from the ideal clock by varying degrees, and higher quality/performance clocks may differ from the ideal clock by lesser amounts than lower quality clocks.
Various characteristics of a clock may be indicative of its quality or performance. For example, the phase noise of the clock may be a characteristic. Phase noise may be the frequency domain representation of rapid, short-term, random fluctuations in the phase of a clock. If a clock with a large amount of phase noise is used to operate an analog to digital converter or digital to analog converter, the audio performance of that converter may be degraded. The clock from the PLL 38 may have lower phase noise than the clock from the oscillator 36. The accuracy of the long-term average of the clock's frequency, e.g. as compared to an international time standard, may be a characteristic of its quality/performance, as an inaccurate frequency may result in an unexpected shift of musical pitch. The clock from the PLL 38 may have better frequency accuracy than the clock from the oscillator 36. The period jitter of a clock may be a characteristic of its quality/performance, as high period jitter detracts from the useful portion of the clock cycle in the digital logic design of the SOC 10. Thus, low period jitter may be a high quality/performance clock characteristic. The clock from the PLL 38 may have lower period jitter than the clock from the oscillator 36. The duty cycle of a clock may be a characteristic of its quality/performance. A symmetrical duty cycle (50% high, 50% low) may be the preferred duty cycle for designs that may include circuitry tied to one or the other transition of the clock. Thus, duty cycles near 50% may be a high quality characteristic, as the high and low phases of the clock may be balanced at 50%. The duty cycle of the clock from the PLL 38 may be nearer 50% than the duty cycle of the clock from the oscillator 36.
During the idle time, the audio filter circuit 24 may be configured to receive audio samples from the audio codec 16, through the IFU 18A and may attempt to detect a predetermined pattern in the samples (e.g. the key word/phrase to wake up the device 5 in order to service a command or request uttered by the user). The predetermined pattern may be programmed into the audio filter circuit 24 or may be hard coded in the audio filter circuit 24. In an embodiment, the predetermined pattern may be captured from the user verbally uttering the key word/phrase, training the device 5 to the user's particular voice. In another embodiment, the predetermined pattern is a generic pattern that represents the key word/phrase as spoken with a variety of inflections, tones, etc. The detection of the key phrase may be performed with the low power clock from the oscillator 36.
In response to detecting the pattern, the audio filter 24 may be configured to cause the memory controller to be powered up and initialized (so that the matching samples and following samples may be stored in memory) and may also be configured to cause the CPU complex 14 to be powered up to boot the operating system (and potentially other portions of the SOC 10, depending on the implementation). In an embodiment, the memory controller 22 may power up relatively quickly. The PLL 38 may lock, and the memory controller 22 may be initialized, with a fairly predictable delay that is shorter than the booting up of the operating system. The interconnect 27 may be powered up as well so that the audio filter circuit 24 may transmit the parameters mentioned below and write memory operations to write the samples to the memory 12. The audio filter circuit 24 may include a sample buffer 30, and the audio filter circuit 24 may be configured to temporarily buffer samples in the sample buffer 30 for comparison to the predetermined pattern and, once the pattern is detected, to further buffer samples until the memory controller 22 is ready to receive writes to the memory 12. Thus, the size of the sample buffer 30 may be based on the delay from detecting the pattern until the memory controller 22 is ready. In some embodiments, the sample buffer 30 may be sized to permit buffering of the samples that match the predetermined pattern, the subsequently-received samples based on the delay until the memory controller is ready, and one or more samples prior to the samples that matched the predetermined pattern (i.e. the key word/phrase/sound). The prior samples may be processed to determine the background noise being captured by the microphone, which may aid the more accurate processing of the subsequent samples.
Once the PLL 38 is powered up and locked, the audio filter circuit 24 may switch from the low power clock from the oscillator 36 to the high performance, high quality clock from the PLL 38. The switch may be glitchless, and may occur over a few clock cycles (e.g. 3 or less) of the high quality clock. The time period for the switch may be much less than the sample time for the audio samples. Accordingly, at most one audio sample may be lost during the switch (and the probability of loss may be low). An audio sample may be lost if it is not included in the samples. An audio sample may also be corrupted (that is, included in the samples but not an accurate sample). At most a threshold number of samples may be corrupted during the switch. In an embodiment, at most one sample may be lost. Alternatively, the audio filter circuit 24 may be configured to ensure that the switch occurs at a time that is not near the arrival of a new sample, thus ensuring no sample loss. Operating at the high performance, high quality clock may permit additional processing of samples in the audio filter circuit 24 as well as high bandwidth transmission of samples to the memory 12, etc.
In some embodiments, the memory controller 22 may support advanced DRAM technologies which involve training the memory controller 22 and the memory 12 to properly sync on the links between them. The parameters of the memory controller 22 configuration may be programmed into the memory controller 22, either directly by hardware via the training or by software (reference numeral 34A). To more rapidly restore the memory controller 22 to operation from the audio filter circuit 24, the audio filter circuit 24 may shadow the parameters (reference numeral 34B). Alternatively, the parameters 34B may be a conservative set of parameters that are known to work properly across all versions of the DRAMs and all operating conditions in the device 10. The audio filter circuit 24 may transfer the parameters 34B to the memory controller 22 to ensure that the memory controller is prepare to write the memory 12.
The CPUs may begin execution of the operating system, and may determine that the reason the SOC 10 is reactivating is that the audio filter 24 detected the key word/phrase. The CPUs may read the samples from the memory 12, and may verify that the key word/phrase is indeed detected. For example, in some embodiments, the audio filter 24 may use a simpler and coarser-grained (less accurate) matching process than may be supported by the code executed by the CPUs. The CPUs may verify that the code is detected, and may proceed to process the rest of the received audio samples to determine the command/request that was spoken after the key word/phrase. Even though the samples were received using the low power clock and the high performance clock, the detected samples may be treated as a continuous stream of samples for processing by the CPUs.
In another embodiment, the CPU complex 14 may not be awakened in parallel with the memory controller 22. For example, in some embodiments, the audio filter circuit 24 may be configured to perform the processing of the subsequent samples (but may power up the memory controller 22 to avail itself of the space in the memory 12 to store samples). In another embodiment, the audio filter circuit 24 may also be configured to perform other operations when the device 5 is idle, and the audio filter circuit 24 may use the memory 12 for storage for some of the operations. In such embodiments, the memory controller 22 may be powered up without powering up the CPU complex 14.
Powering up various components of the SOC 10 may include communication with the PMU 20. In an embodiment, the audio filter circuit 24 may be configured to communicate with the PMU 20 to cause the power up of the other SOC circuit sections. Alternatively, on chip power gating may be implemented to power up/power down various components of the SOC 10. The internal PMGR 28 may be configured to implement the on chip power gating and the audio filter circuit 24 may be configured to communicate with the PMGR 28 to cause the power up. In still other embodiments, a combination of the PMGR 28 and the PMU 20 may be used. In yet another embodiment, the PMGR 28 may be configured to communicate with the PMU 20 and audio filter circuit 24 may communicate power up requests to the PMGR 28, which may communicate with the PMU 20 as needed.
Between the sample buffer 30 and the memory 12, there may be little to no sample loss in the audio data from the microphone(s) 26A-26B. Accordingly, the user may speak the key word/phrase and continue without any required hesitation to speak the request/command.
In various embodiments, the audio filter circuit 24 may include any combination of fixed hardware and/or one or more processors that execute software. The software may be firmware included in the audio filter circuit 24 (e.g. stored in a non-volatile memory in the audio filter circuit 24). Alternatively, the firmware may be included in other non-volatile storage in the device 5 to be accessible for execution. If a fixed hardware implementation is used, the sample pattern may still be programmable as an input to the fixed hardware. Such programmability may allow different key words/phrases/sounds to be used, for multiple languages to be supported, etc. Implementing a fixed hardware audio filter circuit 24 may provide a more power-efficient solution to monitoring the audio samples than a processor executing software may provide.
It is noted that, while the description here may refer to a key word or phrase that may be used to activate the command mode, in general any sound may be used in various embodiments (e.g. a whistle, a hand clap, a non-verbal orally-generated sound, etc.).
As used herein, the term “power up” may refer to applying power to a circuit that is currently powered down (or powered off). In some embodiments, a given circuit may support more than one power state (e.g. voltage and frequency combinations). Powering up may refer to establishing any of the power states supported by the circuit. Powering up may also be referred to as powering on. The term “power down” or “power off” may refer to reducing the power supply voltage magnitude to zero volts (with respect to ground).
The audio codec 16 may be a general coder/decoder of audio data. The codec may include analog to digital converters configured to convert the signals received from the microphones 26A-26B into digital samples that may be transmitted to the SOC 10. The codec may include digital to analog converters configured to receive digital audio data from the SOC 10 and to convert the digital audio data to an analog signal to be played on the speakers. In an embodiment, the audio codec 16 may support one or more low power modes which may be used during times that the device 5 is idle. For example, the audio codec 16 may reduce the number of microphones that are open (or “on”), and may turn off the speakers. In some embodiments, the audio sample rate may be decreased in the low power mode.
The CPU complex 14 may include one or more processors that serve as the CPU of the SOC 10. The CPU of the system includes the processor(s) that execute the main control software of the system, such as an operating system. Generally, software executed by the CPU during use may control the other components of the device 5/SOC 10 to realize the desired functionality of the device 5. The CPU processors may also execute other software, such as application programs. The application programs may provide user functionality, and may rely on the operating system for lower level device control. Accordingly, the CPU processors may also be referred to as application processors. The CPU complex may further include other hardware such as a level 2 (L2) cache and/or an interface to the other components of the system (e.g. an interface to the communication fabric 27).
The peripherals 18A-18B may be any set of additional hardware functionality included in the SOC 10. More particularly, the peripheral 18A may be an interface unit configured to couple to the audio codec 16. Any interface may be used (e.g. the serial peripheral interface (SPI), serial or parallel ports, a proprietary interface for the audio codec 16, etc.). The peripheral 18B may include video peripherals such as video encoder/decoders, scalers, rotators, blenders, graphics processing units, display controllers, etc. The peripherals may include interface controllers for various interfaces external to the SOC 10 including interfaces such as Universal Serial Bus (USB), peripheral component interconnect (PCI) including PCI Express (PCIe), serial and parallel ports, etc. The peripherals may include networking peripherals such as media access controllers (MACs). Any set of hardware may be included.
The memory controller 22 may generally include the circuitry for receiving memory requests from the other components of the SOC 10 and for accessing the memory 12 to complete the memory requests. The memory controller 22 may be configured to access any type of memory 12. For example, the memory 12 may be static random access memory (SRAM), dynamic RAM (DRAM) such as synchronous DRAM (SDRAM) including double data rate (DDR, DDR2, DDR3, etc.) DRAM. Low power/mobile versions of the DDR DRAM may be supported (e.g. LPDDR, mDDR, etc.). In some embodiments, the memory 12 may be packaged separate from the SOC 10 (e.g. in a single inline memory module (SIMM), a dual inline memory module (DIMM) or one or more DRAM chips mounted to a circuit board to which the SOC 10 is mounted). In other embodiments, the memory 12 may be packaged with the SOC 10 (e.g. in a package-on-package or chip-on-chip configuration).
The communication fabric 27 may be any communication interconnect and protocol for communicating among the components of the SOC 10. The communication fabric 27 may be bus-based, including shared bus configurations, cross bar configurations, and hierarchical buses with bridges. The communication fabric 27 may also be packet-based, and may be hierarchical with bridges, cross bar, point-to-point, or other interconnects.
As mentioned above, the power manager 28 may manage internal power sequencing within the SOC 10. The power manager 28 may be configured to establish various power/performance states in various components within the SOC 10 to balance computational demands and power consumption in the device 5. The power manager 28 may be programmable with the desired power/performance states and may manage the power on/off and clock frequency setting of the various components based on the programmed states.
The PMU 20 may generally be responsible for supplying power to the components of the device 5, including the SOC 10, the audio codec 16, the peripherals 26A-26D, and the memory 12. The PMU 20 may be coupled to receive voltage magnitude requests from at least some of the components (e.g. the SOC 10) and may include voltage regulators configured to supply the requested voltages. The SOC 10 may receive multiple voltages (e.g. a CPU voltage for the CPU complex 14, a memory voltage for memory arrays in the SOC 10 such as caches, an SOC voltage or voltages for other components of the SOC, etc.).
The microphones 26A-26B may be any device capable of receiving sound and providing an output signal that represents the received sound. In some cases, more than one microphone may be desirable. For example, in a smart phone with video capability, it may be desirable to include a microphone near where the user's mouth would be when making a voice call, as well as one near the video camera for capturing sound from the subject being filmed. Any number of microphones may be included in various embodiments, and any number of the included microphones may be open when the device 5 is idle.
The speakers 26C-26D may be any device capable of receiving an input signal and generating sound represented by the signal. In some cases, more than one speaker may be desirable. For example, multiple speakers may permit stereo-type sound effects, and multiple speakers may permit sound production to be optimized based on the orientation of the device. Any number of speakers may be included in various embodiments.
It is noted that the number of components of the SOC 10 (and the number of subcomponents for those shown in
Turning next to
The audio filter circuit 24 may receive one or more audio samples from the audio codec 16 into the sample buffer 30 (block 40) and may compare the samples to the predetermined pattern that is used as the key word/phrase/sound to activate the voice command mode in the device 5 (block 42). If there is not a match (decision block 44, “no” leg), the audio filter circuit 24 may continue receiving samples into the sample buffer 30 and comparing the samples. The sample buffer 30 may overwrite the oldest samples with new samples once the sample buffer 30 is full. That is, a sample buffer 30 having N entries for samples (where N is a positive integer) may have the most recent N samples at any given point in time.
Responsive to detecting a match (decision block 44, “yes” leg), the audio filter circuit 24 may be configured to request that the CPU complex 14 and the memory controller 22 be powered up (block 46). The request may be transmitted to the PMU 20, the PMGR 28, or a combination of the two depending on the implementation. As mentioned previously, in other embodiments, only the memory controller 22 may be powered up. Alternatively, the memory controller 22 may be powered up first, and the CPU complex 14 may be powered up subsequently. Such a staggered power up may be used in cases in which powering up the memory controller 22 (and the fabric 27) in parallel with the CPU complex 14 may have the potential to exceed the allowable amount of current during the power up (the so-called “inrush current”).
The memory controller 22 may be powered up, and the memory controller parameters 34B from the audio filter circuit 24 may be restored to the parameters 34A in the memory controller 22 (block 48). The parameters may be “restored” if the parameters 34B are a shadow of the most recent parameters 34A that were in use in the memory controller 22 (prior to powering down the memory controller 22). As mentioned above, in another embodiments, the parameters 34B may be a set of conservative “known good” parameters that will successfully permit access to the memory 12 but may not be optimized for maximum performance. In this case, “restoring” the parameters may refer to establishing the conservative parameters 34B as the parameters 34A. Subsequently, the memory controller 22 may be trained to the memory 12 and the parameters may be modified. The audio filter circuit 24 may write the matching samples and subsequent samples from the sample buffer 30 to the memory 12 through the memory controller 22, and may continue writing the samples until operation is terminated by the CPU complex 14, in an embodiment (block 50).
Additionally, the processors in the CPU complex 14 may boot into the operating system after being powered up and reset (block 52). The operating system, executing on the CPU complex 14, may process the samples stored in the memory 12 to verify that the key word/phrase/sound was indeed detected and to determine what the user's request is. The device 5 may attempt to perform the command/request (block 54).
Booting the operating system may include testing and programming the various components of the SOC 10, and may be a time-consuming task as compared to powering up and restoring the memory controller 22. The operating system may be designed to check if the reason for booting is due to detection of the key word/phrase/sound early in the process of booting, and may process at least the samples that represent the key word/phrase/sound to verify the detection. If the operating system determines that the detection by the audio filter circuit 24 was false, the operating system may cease the booting process and return the device 5 to an idle state (powering off the CPU complex 14 and the memory controller 22).
A portion of the flowchart may be performed by the audio filter circuit operating at the low power clock (above the horizontal dotted line 56 in
The control circuit 60 and the mux 62 may glitchlessly transition between the PLL clock and the oscillator clock, in either direction. In the case of the PLL clock becoming available again, the control circuit 60 may receive an assertion of the Clk_Rdy signal, indicating that the PLL has locked and the high quality clock output by the PLL 38 is stable. The control circuit 60 may be configured to ensure that both clocks are low, and then may be configured to switch the selection control from the oscillator 36 to the PLL 38. The next rising edge of the high quality clock may occur, and subsequently the filter clock may follow the high quality clock.
The above operation is illustrated in the flowchart of
Turning now to
As the audio samples generated in response to the microphone are processed by the audio filter circuit 24, the audio filter circuit 24 may detect the key phrase (reference numeral 70). Responsive to the detection, the audio filter circuit 24 may request power up of the memory controller 22 and the CPU complex 14 (reference numerals 72 and 74). The audio filter circuit 24 may restore the memory controller 22 from the parameters 34B, so that the memory controller 22 may become available to accept write operations. Subsequently, the audio filter circuit 24 may write the audio samples that matched the pattern, and the subsequent samples (representing “where is the closest pizza restaurant?”), to memory (reference numeral 76).
Meanwhile, the CPU may power up, reset, and boot the operating system (reference numerals 74 and 78). As illustrated in
Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5615296 | Stanford | Mar 1997 | A |
| 5774841 | Salazar | Jun 1998 | A |
| 5983186 | Miyazawa | Nov 1999 | A |
| 6408396 | Forbes | Jun 2002 | B1 |
| 7774204 | Mozer | Aug 2010 | B2 |
| 8117475 | Pesavento et al. | Feb 2012 | B2 |
| 8768707 | Mozer | Jul 2014 | B2 |
| 20090292934 | Esliger | Nov 2009 | A1 |
| 20090300386 | Archer | Dec 2009 | A1 |
| 20100312971 | Moallem | Dec 2010 | A1 |
| 20110291801 | Sommer | Dec 2011 | A1 |
| 20120102347 | Hobson | Apr 2012 | A1 |
| 20130080167 | Mozer | Mar 2013 | A1 |
| 20130129114 | Lesso | May 2013 | A1 |
| 20130223635 | Singer | Aug 2013 | A1 |
| 20130225238 | He | Aug 2013 | A1 |
| 20130325484 | Chakladar | Dec 2013 | A1 |
| 20140077849 | Chen | Mar 2014 | A1 |
| 20140122078 | Joshi | May 2014 | A1 |
| 20140179298 | Grokop | Jun 2014 | A1 |
| 20140218372 | Missig | Aug 2014 | A1 |
| 20140222436 | Binder | Aug 2014 | A1 |
| 20140257813 | Mortensen | Sep 2014 | A1 |
| 20140281625 | Younger | Sep 2014 | A1 |
| 20140358552 | Xu | Dec 2014 | A1 |
| 20150066438 | Brooks | Mar 2015 | A1 |
| 20150205342 | Ooi | Jul 2015 | A1 |
| 20150244349 | Bendel | Aug 2015 | A1 |
| 20150245154 | Dadu | Aug 2015 | A1 |
| 20150301557 | Walker | Oct 2015 | A1 |
| 20150326231 | Thinakaran | Nov 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 05252121 | Sep 1993 | JP |
| 2015005927 | Jan 2015 | WO |
| Entry |
|---|
| Office Action from U.S. Appl. No. 14/109,101, mailed Oct. 15, 2015, 18 pages. |
| U.S. Appl. No. 14/109,101, filed Dec. 17, 2013, Timothy J. Millet. |
| “The Jigsaw Continuous Sensing Engine for Mobile Phone Applications”, Hong Lu et al., Nov. 3-5, 2010, pp. 1-14. |
| “How to Get Started With Hands-Free Control on the Moto X”, Nick Mediati, Sep. 9, 2013, pp. 1-4. |
| “Use Voice Commands from the Samsung Galaxy S3 Lock Screen”, Nicole Cozma, Oct. 15, 2012, pp. 1-11. |
| “How the Samsung Galazy S III Can Listen Even While Sleeping”, Mashable, May 29, 2012, pp. 1-14. |
| Non-Final Office Action, U.S. Appl. No. 14/109,101, mailed Jun. 4, 2015, 18 pages. |
| Office Action, U.S. Appl. No. 14/109,101; mailed May 31, 2016; 12 pages. |
| International Search Report and Written Opinion in application No. PCT/US2015/066310 issued Mar. 28, 2016, 13 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20160240193 A1 | Aug 2016 | US |
