Electronic apparatus, control method and electronic device
By employing the collaborative control of SoC and PMU in electronic devices, complete SoC power-down and memory self-refresh are achieved, resolving the contradiction between battery life and fast screen-on in low-power standby mode, and providing an efficient state switching and data recovery solution.
Patent Information
- Application Number
- PCT/CN2026/091242
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-15
- Filing Date
- 2026-04-17
- Publication Date
- 2026-11-19
AI Technical Summary
Existing technologies struggle to simultaneously deliver both long battery life and fast screen-on performance in electronic devices. Suspending to memory results in short standby time because the SoC is not fully powered down, while suspending to disk leads to long wake-up times and data loss. It is impossible to achieve low-power standby with a single switch.
An electronic device is used, including a system-on-a-chip (SoC) and a power management unit (PMU). In an ultra-low power state, the SoC is completely powered down, the memory enters a self-refresh state, and the operating state information is stored. Upon wake-up, the operating state is quickly restored based on the memory information, skipping the complete boot process.
It achieves a balance between battery life and fast screen-on experience in ultra-low power consumption, with short wake-up latency, minimal data loss, and simplified state switching process.
Smart Images

Figure CN2026091242_19112026_PF_FP_ABST
Abstract
Description
An electronic device, control method and electronic equipment
[0001] This application claims priority to Chinese Patent Application No. 202510631715.5, filed on May 15, 2025, entitled "An Electronic Device, Control Method and Electronic Equipment", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of electronic technology, and more particularly to an electronic device, control method, and electronic equipment. Background Technology
[0003] Battery life and quick screen wake-up (or fast screen activation) are two important aspects of the user experience for electronic devices such as laptops, tablets, and PDAs. Battery life requires minimizing power consumption in standby mode to extend standby time. Fast screen wake-up requires the ability to be quickly woken up from standby mode to its previous state.
[0004] Currently, low-power standby for electronic devices is typically achieved by suspending to RAM or disk. However, in the RAM-to-RAM method, the system-on-chip (SoC) of the electronic device is not completely powered off, resulting in a short standby time. In the disk-to-disk method, although the SoC is completely powered off, the time required to wake up the device is relatively long. Therefore, how to simultaneously improve the user experience of both battery life and fast screen-on speed is a pressing technical problem that needs to be solved. Summary of the Invention
[0005] This application provides an electronic device, control method, and electronic device that simultaneously provides users with both extended battery life and fast screen-on experience.
[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:
[0007] In a first aspect, an electronic device is provided, comprising: a system-on-a-chip (SoC) and a power management unit (PMU); the PMU is configured to provide a first power supply signal to the SoC and a second power supply signal to memory in the operating state of the electronic device; the PMU is further configured to stop providing any power supply signal to the SoC in the ultra-low power state of the electronic device, and to switch the second power supply signal provided to the memory to a third power supply signal, the third power supply signal being used to maintain the memory in a self-refresh state; the SoC is configured to store the SoC's operating state information in the memory and perform a power-down operation when the electronic device needs to enter the ultra-low power state from the operating state; After the power-down operation, the electronic device enters the ultra-low power state; the PMU is also used to provide a first power supply signal to the SoC in response to the wake-up signal, and to switch the third power supply signal provided to the memory to a second power supply signal; the SoC is also used to receive the first power supply signal and perform a power-on operation based on the running state information stored in the memory to restore the working state of the electronic device; wherein, the power-on operation includes: a read-only memory ROM boot operation, an initial boot program xloader boot operation, and restoring the SoC operation based on the running state information, and skipping the subsequent boot program of the xloader in the complete boot process during the power-on operation.
[0008] In the above technical solution, the electronic device can enter an ultra-low power state from the working state and also return to the working state from the ultra-low power state. In the ultra-low power state, the SoC is completely powered down, the memory enters a self-refresh state, and the memory stores the SoC's operating status information. When the electronic device needs to return to the working state, the memory can exit the self-refresh state. After the SoC is powered on, it can perform a power-on operation based on the operating status information stored in the memory to return to the working state. Moreover, the power-on operation can skip the subsequent boot program of xloader in the complete boot process, so that the electronic device can switch between the working state and the ultra-low power state while ensuring both the user's battery life and fast screen-on experience.
[0009] In one possible implementation of the first aspect, the runtime status information includes user-mode runtime status information, kernel-mode runtime status information, and software image information of the microcontroller (MCU) for power consumption control. Optionally, the runtime status information includes runtime status information of the power-down subsystem and runtime status information of the non-power-down subsystem. A portion of any subsystem in the power-down or non-power-down subsystem can run in user mode, and another portion can run in kernel mode, thus the runtime status information of any subsystem can simultaneously include relevant user-mode runtime status information and kernel-mode runtime status information. In the above possible implementations, based on the kernel-mode runtime status information and the user-mode runtime status information, the kernel-mode and user-mode operation of the SoC can be quickly restored, thereby reducing wake-up latency and satisfying the user's need for a fast screen-on experience.
[0010] In one possible implementation of the first aspect, the SoC further includes a non-power-down subsystem, and the operating state information includes non-power-down operating state information; in the ultra-low power state of the electronic device, the non-power-down subsystem is powered down; restoring the SoC operation based on the operating state information includes: the non-power-down subsystem resuming operation based on the non-power-down operating state information. In the above possible implementations, powering down the non-power-down subsystem in the ultra-low power state of the electronic device can further improve the user's battery life experience; when returning to the working state, the non-power-down subsystem resuming operation based on the non-power-down operating state information can reduce wake-up latency and improve the user's fast screen-on experience.
[0011] In one possible implementation of the first aspect, the SoC is further configured to: configure the PMU to control the memory reset signal when the electronic device needs to enter the ultra-low power state from the operating state; the PMU is further configured to: control the memory reset signal in the ultra-low power state of the electronic device. In the above possible implementations, by configuring the PMU to control the memory reset signal in the ultra-low power state of the electronic device, the SoC can achieve complete power-down, and the memory can enter a self-refresh state.
[0012] In one possible implementation of the first aspect, the SoC is further configured to: when the electronic device needs to enter the ultra-low power state from the operating state, configure the status flag in the PMU to a first value, the first value indicating that the electronic device enters the ultra-low power state; after performing the power-on operation, configure the status flag to a second value, the second value indicating that the electronic device resumes the operating state. In the above possible implementations, by configuring the status flag in the PMU, the electronic device, when resuming the operating state, can perform a power-on operation based on the running state information in the memory to resume the operating state, thus skipping the subsequent boot program of the xloader in the complete boot process, thereby reducing wake-up latency and satisfying the user's fast screen-on experience.
[0013] Secondly, a control method for an electronic device is provided, the electronic device including a system-on-a-chip (SoC) and a power management unit (PMU), the method comprising: in the operating state of the electronic device, the PMU provides a first power supply signal to the SoC and a second power supply signal to memory; in the ultra-low power state of the electronic device, the PMU stops providing any power supply signal to the SoC and switches the second power supply signal provided to the memory to a third power supply signal, the third power supply signal being used to maintain the memory in a self-refresh state; when the electronic device needs to enter the ultra-low power state from the operating state, the SoC stores the SoC's operating state information in the memory, and... A power-down operation is performed; after the power-down operation, the electronic device enters the ultra-low power state; in response to the wake-up signal, the PMU provides a first power supply signal to the SoC and switches the third power supply signal provided to the memory to a second power supply signal; the SoC receives the first power supply signal and performs a power-on operation based on the running state information stored in the memory to restore the working state of the electronic device; wherein, the power-on operation includes: a read-only memory ROM boot operation, an initial boot program xloader boot operation, and restoring the SoC operation based on the running state information, and skipping the subsequent boot program of the xloader in the complete boot process during the power-on operation.
[0014] In one possible implementation of the second aspect, the runtime status information includes user-mode runtime status information and kernel-mode runtime status information. Optionally, the runtime status information includes runtime status information of the power-down subsystem and runtime status information of the non-power-down subsystem. A portion of any subsystem in the power-down subsystem and the non-power-down subsystem can run in user mode, and another portion can run in kernel mode, thus the runtime status information of any subsystem can simultaneously include relevant user-mode runtime status information and kernel-mode runtime status information.
[0015] In one possible implementation of the second aspect, the SoC further includes a non-power-down subsystem, and the operating status information includes non-power-down operating status information; in the ultra-low power state of the electronic device, the non-power-down subsystem is powered down; restoring the SoC operation based on the operating status information includes: the non-power-down subsystem restoring operation based on the non-power-down operating status information.
[0016] In one possible implementation of the second aspect, the method further includes: when the electronic device needs to enter the ultra-low power state from the operating state, the SoC configures the PMU to control the memory reset signal; the PMU controls the memory reset signal in the ultra-low power state of the electronic device.
[0017] In one possible implementation of the second aspect, the method further includes: when the electronic device needs to enter the ultra-low power state from the operating state, the SoC configures the status identifier in the PMU to a first value, the first value being used to indicate that the electronic device enters the ultra-low power state; after performing the power-on operation, the SoC configures the status identifier to a second value, the second value being used to indicate that the electronic device resumes the operating state.
[0018] Thirdly, an electronic device is provided, comprising: a memory, and an electronic means as provided in the first aspect or any possible implementation thereof; wherein the memory is coupled to the electronic means for storing operating state information of a SoC in the electronic means.
[0019] Understandably, the beneficial effects achieved by any of the control methods and electronic devices provided above can be referred to in the context of the beneficial effects of the electronic devices provided above, and will not be repeated here. Attached Figure Description
[0020] Figure 1 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;
[0021] Figure 2 is a schematic diagram of a suspension to memory provided in an embodiment of this application;
[0022] Figure 3 is a schematic diagram of suspending to a disk according to an embodiment of this application;
[0023] Figure 4 is a schematic diagram of an electronic device switching between multiple states according to an embodiment of this application;
[0024] Figure 5 is a schematic diagram of the structure of another electronic device provided in an embodiment of this application;
[0025] Figure 6 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;
[0026] Figure 7 is a schematic diagram of an electronic device switching between a working state and an ultra-low power consumption state according to an embodiment of this application;
[0027] Figure 8 is a schematic diagram of an electronic device entering an ultra-low power state from an operating state according to an embodiment of this application;
[0028] Figure 9 is a schematic diagram of an electronic device skipping the subsequent boot process of xloader according to an embodiment of this application;
[0029] Figure 10 is a schematic diagram of an electronic device recovering from an ultra-low power state to an operating state according to an embodiment of this application;
[0030] Figure 11 is a schematic diagram of the structure of another electronic device provided in an embodiment of this application. Detailed Implementation
[0031] The following sections will discuss the fabrication and use of various embodiments in detail. However, it should be understood that many of the concepts applicable to this application can be implemented in a variety of specific environments. The specific embodiments discussed are merely illustrative of specific ways to implement and use this application and technology, and do not limit the scope of this application.
[0032] Unless otherwise defined, all technical terms used herein have the same meaning as commonly known to one of ordinary skill in the art.
[0033] Each circuit or other component may be described or referred to as "for" performing one or more tasks. In this context, "for" is used to imply a structure by indicating that the circuit / component includes a structure (e.g., a circuit system) that performs one or more tasks during operation. Therefore, even when the specified circuit / component is currently inoperable (e.g., not turned on), it can still be referred to as "for performing that task." Circuits / components used with the term "for" include hardware, such as circuits that perform operations.
[0034] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a, b, and c; where a, b, and c can be single or multiple.
[0035] The embodiments of this application use terms such as "first" and "second" to distinguish objects with similar names, functions, or effects. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or order of execution. The term "coupling" is used to indicate an electrical connection, including direct connection via wires or terminals or indirect connection via other devices. Therefore, "coupling" should be considered as a broad type of electronic communication connection.
[0036] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0037] Before introducing the embodiments of this application, the application scenarios involved in this application will be described first.
[0038] With the rapid development of technology, people have placed numerous demands on electronic devices such as laptops, tablets, and PDAs. For example, they require devices to avoid frequent charging, to be readily available and usable, to retain data when the lid is closed and reopened, and to be thinner and lighter. Among these, battery life and fast screen-on (or quick wake-up) are two crucial user experiences closely related to most of these requirements. In practical applications, low-power standby can improve the user experience of battery life and fast screen-on. The following example, using the electronic device shown in Figure 1, illustrates several low-power standby solutions for this device.
[0039] As shown in Figure 1, the electronic device includes a system-on-chip (SoC), a power management unit (PMU), and memory. The output of the PMU is coupled to the power supply terminals VDD of both the SoC and the memory. The control terminal of the SoC is coupled to its reset (RST) terminal. The PMU can be used to output power signals to the SoC and the memory, and the SoC can be used to provide a reset signal to the memory. The SoC may include a power-down subsystem and an always-on unit (AO) subsystem. Either the power-down subsystem or the always-on unit (AO) subsystem can run in user mode or kernel mode. The power-down subsystem can be a peripheral unit (PERI) subsystem. Furthermore, the power-down subsystem may include an application central processing unit (ACPU) and a microcontroller unit (MCU) for power consumption control. Specifically, the MCU can control the power-on and power-off of the ACPU. The ACPU can refer to one or more application-related processors, including a central processing unit (CPU), a graphics processing unit (GPU), a neural network processing unit (NPU), or at least one other processor. Optionally, the memory may be double-data-rate (DDR) synchronous dynamic random access memory (SDRAM). DDR SDRAM can be abbreviated as DDR; Figure 1 uses DDR memory as an example for illustration.
[0040] In one possible embodiment, as shown in Figure 2, a suspend-to-RAM scheme can be used to achieve low-power standby for electronic devices. Suspending to RAM can also be referred to as S3 technology, and the state in which the electronic device enters suspend-to-RAM can be described as the electronic device entering the S3 state. Specifically, when certain conditions are met, the SoC of the electronic device can back up user data and context information from the power-down subsystem to the DDR and the non-power-down electronic system, and execute the power-down operation of the SoC's power-down subsystem. For example, it can freeze the user / kernel processes running in the CPU, suspend multiple software drivers in the kernel, power down the hardware corresponding to these multiple software drivers, suspend the CPU's software drivers, and power down the processing core. Finally, the MCU controls other processors such as the GPU and NPU to power down, shut down the clock, and power down the bus, thereby enabling the electronic device to enter the S3 state.
[0041] In this embodiment, when the electronic device enters the S3 state, only the power-down subsystem is powered down, while the non-power-down subsystem remains powered on. The SoC maintains its ability to be woken up at any time and enters a low-power mode to reduce system power consumption. In addition, in the S3 state, the DDR does not power down but enters an auto-refresh (AR) state to prevent data loss. At the same time, when entering the S3 state, the relevant information of the power-down subsystem is backed up to the DDR. Thus, when waking up, the SoC will not execute the initialization process of each module or unit in the power-down subsystem. It only needs to quickly restore the state before entering S3 based on the backed-up information. Therefore, the wake-up latency of the S3 state is short, and the fast screen-on experience can be achieved within 1 second.
[0042] However, the SoC in this solution does not completely power down, resulting in a short standby time for the electronic device. For example, assuming the power consumption of the electronic device in S3 state is in the range of 150-200mW and the battery capacity of the electronic device is 70Wh, the electronic device can only maintain its power for 15-20 days in S3 state. Without user intervention, the electronic device will eventually shut down as the battery is depleted, and the data backed up in DDR will be lost after shutdown.
[0043] In another possible embodiment, as shown in Figure 3, a suspend-to-disk approach can be used to achieve low-power standby for the electronic device. Suspending to disk can also be referred to as S4 technology, and the electronic device being in this state can be described as entering the S4 state. Specifically, when certain conditions are met, the current memory (or on-chip memory) of the SoC is backed up to an external disk in the form of a snapshot. This involves backing up the relevant information of the power-down subsystem and the non-power-down subsystem of the SoC to the disk, which is a non-volatile storage medium. Then, a DDR power-down operation is performed, followed by a SoC power-down operation, to put the electronic device into the S4 state. Taking the power-down subsystem as an example, the user / kernel processes running within the CPU A can be frozen, multiple software drivers within the kernel can be frozen, the hardware corresponding to these software drivers can be powered down, and the CPU's software drivers and processing cores can be powered down. A snapshot is then created and saved to the disk.
[0044] In this embodiment, when the electronic device enters the S4 state, both the power-down subsystem and the non-power-down subsystem are powered down instead of entering a low-power mode; the DDR is also powered down instead of entering a self-refresh state, and the power consumption is 0; in addition, when entering the S4 state, a snapshot of the current memory of the SoC is taken and stored on an external disk, so that the snapshot can be restored from the disk when the device is woken up, so that the electronic device can be restored to the state before the power-down.
[0045] However, in this solution, both the SoC and DDR are fully powered down, requiring a power-on process upon restarting. Furthermore, the previously saved snapshot needs to be moved and restored during wake-up, resulting in a screen-on latency of approximately 10 seconds. This leads to a poor screen-on experience for users and fails to effectively meet their need for on-demand use.
[0046] In another possible embodiment, to minimize the power consumption of the electronic device, the user can also shut it down. The shutdown state of the electronic device can also be referred to as the S5 state. Shutting down the device completely eliminates the need to back up user data and related context information, resulting in zero power consumption. However, this method does not back up and restore user data and context information, leading to data loss. Upon powering on, the entire device needs to be initialized, following a cold boot process, resulting in a boot-up delay of approximately 10-20 seconds. Furthermore, it requires significant user interaction with the user interface, leading to a poor user experience.
[0047] In practical applications, to simultaneously consider the user's experience with battery life and fast screen-on speed, the solutions from the various embodiments described above are typically time-division multiplexed in a tiered manner. For example, as shown in Figure 4, when an electronic device is in an active state and meets the S3 standby condition, it can enter the S3 state. When it meets the S4 standby condition in the S3 state, it can enter the S4 state. When it meets the power-off condition in the S4 state, it can enter the power-off state. The electronic device can also enter the active state from any of the power-off state, the S4 state, and the S3 state. The S3 standby condition, the S4 standby condition, and the power-off condition can be configured according to actual needs. For example, these conditions can be configured based on standby days and power consumption in a certain state. Furthermore, the wake-up delay of the electronic device from the power-off state to the active state (e.g., <20s) is greater than the wake-up delay from the S4 state to the active state (e.g., <10s), and the wake-up delay from the S4 state to the active state (e.g., <10s) is greater than the wake-up delay from the S3 state to the active state (e.g., <1s). The aforementioned active state can also be referred to as the working state.
[0048] The aforementioned time-division multiplexing approach creates complex state switching. While it can balance battery life and fast screen-on speed, it requires the electronic device to support multiple implementations simultaneously and to switch between these different states, which cannot be achieved through a single switch. Therefore, how to achieve low-power standby while maintaining both battery life and fast screen-on speed when switching between multiple states is a pressing technical problem that needs to be solved.
[0049] Based on this, embodiments of this application provide an electronic device that can enter an ultra-low power state from a working state. In this ultra-low power state, the SoC is completely powered down, the memory (e.g., DDR) enters a self-refresh state, and the memory stores the SoC's operating state information. When the electronic device needs to return to the working state, the SoC can perform a power-on operation based on the operating state information stored in the memory after receiving a power supply signal to return to the working state. In this power-on operation, the subsequent boot program of the initial boot program xloader in the complete boot process can be skipped. Thus, the ultra-low power state of the electronic device can simultaneously provide users with both battery life and fast screen-on experience.
[0050] The technical solutions provided in this application can be applied to a variety of electronic devices, including portable devices such as portable personal computers (PCs); of course, the various electronic devices may also include other devices besides portable devices. Optionally, the electronic devices may include, but are not limited to: tablet computers, laptops, desktop computers, handheld computers, ultra-mobile personal computers (umPCs), mobile internet devices (MIDs), netbooks, wearable devices, in-vehicle devices, smart vehicles, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, workshop equipment, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc.
[0051] Figure 5 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Taking a laptop computer as an example, the electronic device includes: a radio frequency (RF) circuit 110, a memory 120, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a processor 170, and a power supply 180, etc.
[0052] The RF circuit 110 can be used to transmit and receive information, or to receive or send signals during a call. Specifically, it receives downlink information from the base station and processes it in the processor 170; additionally, it transmits uplink data to the base station. Typically, the RF circuit 110 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc. Furthermore, the RF circuit 110 can also communicate wirelessly with networks and other devices.
[0053] The memory 120 can be used to store data, software programs, and modules; it includes a program storage area and a data storage area. The program storage area can store the operating system and application programs required for at least one function, such as sound playback and image playback functions. The data storage area can store data created based on the use of the electronic device, such as audio data, image data, and a phone book. Optionally, the electronic device may include random access memory (RAM) and read-only memory (ROM), and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Exemplarily, the random access memory may include static random access memory (SRAM) and dynamic random access memory (DRAM), for example, the dynamic random access memory may be double-rate synchronous dynamic random access memory (DDR).
[0054] Input unit 130 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the electronic device. Input unit 130 may include touch screen 131 and other input devices 132. Touch screen 131 can collect touch operations on or near the user and drive corresponding connected devices according to a pre-set program. For example, touch operations may include operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch screen. Optionally, other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys, mouse, joystick, etc., such as volume control buttons, power switch buttons, etc.
[0055] Display unit 140 can be used to display information input by the user or information provided to the user, as well as various menus of the electronic device. In one example, display unit 140 may include display screen 141, which may be configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar device. Furthermore, touchscreen 131 may cover display screen 141. When touchscreen 131 detects a touch operation on or near it, it transmits the information to processor 170 to determine the type of touch event. Subsequently, processor 170 provides corresponding visual output on display screen 141 based on the type of touch event. Although in the figures, touchscreen 131 and display screen 141 are shown as two separate components to implement the input and output functions of the electronic device, in some embodiments, touchscreen 131 and display screen 141 can be integrated to achieve the input and output functions of the electronic device.
[0056] Sensor 150 may include one or more sensors for providing status assessments of various aspects of the electronic device. Sensor 150 may include a light sensor, which can be used in imaging applications, i.e., as a component of a camera or video camera. Furthermore, sensor 150 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor. Sensor 150 can detect acceleration / deceleration, orientation, on / off state, relative positioning of components, or temperature changes of the electronic device.
[0057] Audio circuitry 160, a speaker, and a microphone provide an audio interface between the user and the electronic device. Audio circuitry 160 converts received audio data into electrical signals and transmits them to the speaker, where the speaker converts them into sound signals for output. On the other hand, the microphone converts collected sound signals into electrical signals, which are then received by audio circuitry 160, converted into audio data, and output to RF circuitry 110 for transmission to another electronic device, or to memory 120 for further processing.
[0058] The processor 170 is the control center of the electronic device, connecting various parts of the device through various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 120, and by calling data stored in the memory 120, thereby providing overall control of the electronic device. Optionally, the processor 170 may include one or more processing units, which may include, but are not limited to: a central processing unit (CPU), a neural network processor (NPU), a graphics processing unit (GPU), an image signal processor (ISP), a tensor processing unit (TPU), a data processing unit (DPU), a digital signal processor (DSP), a microcontroller, or a microprocessor. Further, the processor 170 may also include other hardware circuits or accelerators, such as application-specific integrated circuits (ASICs), complex programmable logic devices (CPLDs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. Optionally, the processor 170 may also be a combination that implements computational functions, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor.
[0059] The electronic device may also include a power supply 180 (e.g., a battery) to power various components. The power supply 180 can be logically connected to the processor 170 via a power management unit (PMU), thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Optionally, the power management system can simultaneously support fast charging and non-fast charging technologies. In practical applications, the power management system can charge the battery in the power supply 180 using either fast charging or non-fast charging technologies.
[0060] Furthermore, the electronic device may also include a Wi-Fi module, a Bluetooth module, etc., which will not be described in detail in the embodiments of this application. Those skilled in the art will understand that the structure of the electronic device shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0061] In practical applications, the processor 170 in this electronic device can be integrated into a System-on-a-Chip (SoC). Other components besides the SoC can be integrated into the SoC, or not integrated into the SoC, or at least partially integrated into the SoC. For example, the DDR in the memory 120 can be set outside the SoC as off-chip memory (referred to as RAM), the SRAM in the memory 120 can be integrated inside the SoC as on-chip memory, and the PMU can also be integrated outside the SoC.
[0062] Figure 6 is a schematic diagram of an electronic device provided in an embodiment of this application. The electronic device may include a coupled SoC and PMU. The SoC may correspond to the processor 170 in Figure 5, and the PMU is coupled between the processor 170 and the power supply 180 in Figure 5. The SoC and the PMU can also be coupled to memory, which can be disposed in the same electronic device as the electronic device, specifically as part of the memory 120 in Figure 5. For example, the PMU can be coupled to the power supply terminal VDD1 of the SoC and the power supply terminal VDD2 of the memory. The PMU and the SoC can also be coupled to the reset terminal RST of the memory. The memory can be off-chip memory of the SoC, such as DRAM or DRAM DDR.
[0063] In this embodiment, the electronic device has an operating state and an ultra-low power state. The electronic device can directly enter the ultra-low power state from the operating state, and can also directly recover from the ultra-low power state back to the operating state. The ultra-low power state can also be referred to as an ultra-low power suspend and resume (ULRS) state. Optionally, the electronic device can also have a low power state, which it can enter from the operating state and recover from the low power state back to the operating state. The power consumption of the electronic device in the low power state is greater than the power consumption of the electronic device in the ultra-low power state.
[0064] In the ultra-low power state of the electronic device, the SoC can be completely powered down. For example, both the power-down subsystem and the non-power-down subsystem in the SoC are powered down, as shown in Figure 8. In the low power state of the electronic device, the SoC is partially powered down. For example, the power-down subsystem in the SoC is powered down, while the non-power-down subsystem is not powered down, as shown in Figure 2.
[0065] The following mainly describes the state of the electronic device in the working state and the ultra-low power state, as well as the process of entering the ultra-low power state from the working state and the process of returning to the working state from the ultra-low power state.
[0066] As shown in Figure 7, in the operating state of this electronic device, the PMU provides a first power supply signal U1 to the SoC and a second power supply signal U2 to the memory. In this operating state, the SoC can be used for normal operation, and the memory can be used for normal access; for example, the SoC can be used for normal business processing, and the memory can be used for normal storage and retrieval of information. The first power supply signal U1 and the second power supply signal U2 can be two independent power supply signals output by the PMU, meaning that the power supply to the SoC and the power supply to the memory are independent and do not affect each other. In practical applications, the power supply voltage corresponding to the first power supply signal U1 and the power supply voltage corresponding to the second power supply signal U2 can be equal or unequal; this embodiment does not impose specific limitations on this.
[0067] As shown in Figure 7, in the ultra-low power state of this electronic device, the PMU is used to stop providing any power supply signal to the SoC and switch the second power supply signal U2 provided to the memory to the third power supply signal U3. The third power supply signal U3 is used to maintain the memory in a self-refresh state. After entering the self-refresh state, the memory can automatically refresh the information stored internally to maintain the integrity of the information. Optionally, the supply voltage corresponding to the second power supply signal U2 can be greater than the supply voltage corresponding to the third power supply signal U3, i.e., U2 > U3. The power consumption of the memory in the self-refresh state can be less than the power consumption in the normal access state.
[0068] Optionally, the PMU may include a status flag that can be used to identify the state of the electronic device. For example, the PMU may include a register that stores the status flag, and the SoC may configure the value of the status flag. When the status flag is configured to different values, it can indicate different states of the electronic device. For instance, when the status flag is configured to a first value, it can indicate that the electronic device has entered an ultra-low power state; when the status flag is configured to a second value, it can indicate that the electronic device has entered an operating state, or that the electronic device has resumed its operating state.
[0069] Optionally, in this embodiment, the memory reset signal can be controlled by the SoC or the PMU. For example, in the operating state of the electronic device, the SoC can be used to control the memory reset signal; for instance, when the memory needs to be reset, the SoC can provide a valid reset signal, and when the memory does not need to be reset, the SoC can provide an invalid reset signal. In the ultra-low power state of the electronic device, the PMU can be used to control the memory reset signal; for instance, when the memory enters a self-refresh state, the PMU can provide an invalid reset signal.
[0070] In one possible embodiment, when the electronic device needs to transition from the operating state to the ultra-low power state, the SoC can be used to: store the SoC's operating state information in the memory, configure the state flag in the PMU to a first value, configure the PMU to control the memory's reset signal, and perform a power-down operation. After the power-down operation is completed, the electronic device enters the ultra-low power state.
[0071] Optionally, the runtime status information may include user-mode runtime status information, kernel-mode runtime status information, and software image information of the MCU within the SOC for power consumption control. The user-mode runtime status information may include runtime status information of relevant software and hardware running in user mode. The kernel-mode runtime status information may include runtime status information of relevant software and hardware running in kernel mode. The MCU software image information may include image information of the software running on the MCU, which may include the software itself and its runtime information. For example, either the user-mode runtime status information or the kernel-mode runtime status information may include runtime data, context information, relevant address information, relevant register states, temporary information, and other information.
[0072] Optionally, the operating status information may include operating status information of the power-down subsystem and operating status information of the non-power-down subsystem. A portion of any subsystem in the power-down or non-power-down subsystem may run in user mode, while another portion may run in kernel mode. Therefore, the operating status information of any subsystem may simultaneously include relevant user-mode and kernel-mode operating status information. Furthermore, the operating status information of the power-down subsystem may also include the MCU software image information. Further, if the SoC includes other components, the operating status information may also include operating status information related to those other components; this embodiment does not impose specific limitations in this regard.
[0073] In practical applications, the runtime status information stored in this memory can be a subset of all runtime status information corresponding to the SoC. Optionally, runtime status information of relevant software or hardware whose states have changed when the electronic device recovers from the ultra-low power state to the operating state does not need to be stored. For example, the runtime status information may not include the temperature information of the electronic device, meaning that the temperature information does not need to be backed up. For instance, after the electronic device enters the ultra-low power state and maintains it for a long time, the temperature information of the electronic device may have changed significantly, making it meaningless to back up the temperature information. Therefore, it is not necessary to back up the temperature information of the power-down subsystem or the non-power-down subsystem before power-down. Furthermore, the runtime status information may not include the relevant register information and status information of the audio / video services corresponding to the non-power-down subsystem in kernel mode, meaning that the relevant register information and status information of the audio / video services in kernel mode does not need to be backed up.
[0074] Optionally, storing the SoC's operating status information in the memory and performing a power-down operation may include: storing the operating status information of the power-down subsystem in the memory and performing a power-down operation on the power-down subsystem; and storing the operating status information of the non-power-down subsystem in the memory, with the non-power-down subsystem performing a power-down operation. Further, the electronic device or the electronic device in which the electronic device resides may also include an embedded controller (EC) and peripheral devices. After the SoC performs a power-down operation, the embedded controller and the peripheral devices may also perform power-down operations; subsequently, the electronic device enters the ultra-low power state.
[0075] Furthermore, the electronic device can determine whether it needs to enter the ultra-low power state from the current operating state based on certain conditions. These conditions are configurable, for example, they can be dynamically configured according to actual conditions and needs. Optionally, these conditions may include one or more of the following: direct current (DC) power supply, cover closed, screen locked, preset screen off time, remaining battery power less than a preset battery power, and usable time less than a preset time. This application embodiment does not impose specific restrictions on the conditions under which the electronic device enters the ultra-low power state from the current operating state.
[0076] For ease of understanding, the memory is DDR, and Figure 8 illustrates the process by which the electronic device transitions from the operating state to the ultra-low power state. For example, as shown in Figure 8, the process of the electronic device transitioning from the operating state to the ultra-low power state may include: when the electronic device meets certain conditions (e.g., DC power supply, screen lock, and screen off for 4 hours), it indicates that the electronic device needs to transition from the operating state to the ultra-low power state. At this time, the operating state information of the power-down subsystem and the operating state information of the non-power-down subsystem can be stored in the memory. Then, the power-down operation of the power-down subsystem and the power-down operation of the non-power-down subsystem are performed. In the case where the power-down subsystem includes an ACPU and an MCU, the user / kernel processes running on the ACPU within the SoC can be frozen first. Then, the running status information related to the ACPU is stored in the memory, multiple software drivers in the kernel are suspended, the hardware corresponding to these multiple software drivers is powered down, the CPU's software drivers are suspended, and the processing core is powered down. If the kernel includes a non-secure state and a secure state, the non-secure state can perform the power-down first, and the secure state can perform the power-down later. Afterward, the MCU controls other processors such as the GPU and NPU to power down, shut down the clock, power down the bus, and power up the power configuration. In addition, the PMU switches the second power supply signal U2 provided to the DDR to the third power supply signal U3, and the DDR enters a self-refresh state. In one example, the SoC configures the status flag in the PMU to a first value and configures the PMU to control the reset signal of the DDR to provide an invalid reset signal to the DDR. Afterward, the PMU stops providing any power supply signal to the SoC, for example, setting the SoC's power hold signal to 0 to perform a full power-down of the SoC.
[0077] In one possible embodiment, when the electronic device recovers from the ultra-low power state to the operating state, the PMU, in response to a wake-up signal, provides a first power supply signal U1 to the SoC and switches the third power supply signal U3 provided to the memory to a second power supply signal U3. The SoC receives the first power supply signal U1 and performs a power-on operation based on the operating state information stored in the memory to restore the operating state of the electronic device. Optionally, during the process of the electronic device recovering from the ultra-low power state to the operating state, the SoC is further configured to configure the status flag in the PMU to a second value, control the memory to exit the self-refresh state, and control the memory's reset signal. The memory reset signal in this embodiment can also be called the memory management reset signal, i.e., controlling whether the memory is reset.
[0078] In this embodiment of the application, the power-on operation when the SoC restores to the working state includes: read-only memory ROM boot operation, initial boot program xloader boot operation, and restoring the SoC operation based on the running state information, and skipping the subsequent boot program of the xloader in the complete boot process during the power-on operation.
[0079] The wake-up signal can be triggered by the user, and the PMU can detect the wake-up signal. For example, when the user needs to restore the electronic device to its working state, the user can trigger the wake-up signal by pressing the power button or opening the lid (e.g., opening the front cover of the laptop), so that the PMU can detect the wake-up signal.
[0080] Furthermore, the supply voltage corresponding to the first power supply signal U1 provided by the PMU to the SoC in response to the wake-up signal can be referred to as the first voltage, and the supply voltage corresponding to the first power supply signal U1 provided by the PMU to the SoC in the operating state of the electronic device can be referred to as the second voltage. The first voltage and the second voltage can be equal or unequal, and the SoC can operate under both the first voltage and the second voltage. That is to say, the value of the first power supply signal U1 of the SoC can vary in different operating states at different times, and can be changed according to its workload.
[0081] Furthermore, the complete boot process can refer to the boot process when the electronic device is powered on using a cold boot method. This complete boot process can correspond to multiple stages, with the ROM boot operation being the first stage and the xloader boot operation being the second stage; that is, the xloader boot operation is the next stage after the ROM boot operation. For example, the ROM boot operation can refer to executing the bootROM, which is typically embedded within the SOC.
[0082] Optionally, the subsequent bootloader in the complete boot process may include firmware loading and module initialization. For example, firmware loading may be a u-boot boot operation, and module initialization may be the initialization of multiple hardware components and their corresponding software within the SoC. This process can be omitted during the recovery from the ultra-low power state to the operating state, i.e., skipped. For instance, as shown in Figure 9, when the SoC recovers from the ultra-low power state to the operating state, only the bootROM and xloader in the complete boot process are executed (shown in the solid box in Figure 9), while the execution of other subsequent programs such as u-boot and module initialization is skipped (shown in the dashed box in Figure 9).
[0083] Optionally, after executing the ROM boot operation and the xloader boot operation, the SoC can restore its operation based on the runtime state information. This can include: restoring the SoC's kernel-mode operation based on kernel-mode runtime state information, and restoring the SoC's user-mode operation based on user-mode runtime state information, to restore the SoC to its operating state before power-down; or, restoring the SoC's non-power-down subsystem operation based on the non-power-down subsystem operation state information, and restoring the SoC's power-down subsystem operation based on the power-down subsystem operation state information, to restore the SoC to its operating state before power-down. Furthermore, during the process of restoring the SoC's operation, the DDR also exits the self-refresh state and returns to a normal access state.
[0084] For ease of understanding, the process of the electronic device recovering from the ultra-low power state to the operating state is illustrated below using DDR memory as an example, with reference to Figure 10. For example, as shown in Figure 10, the process of the electronic device recovering from the ultra-low power state to the operating state may include: when the user triggers a wake-up signal via a power-on event, the PMU responds to the wake-up signal by providing a first power supply signal U1 to the SoC and switching the third power supply signal U3 provided to the DDR to a second power supply signal U2; the SoC receives the first power supply signal U1 and performs ROM boot operations and xloader boot operations; during the xloader boot operation, the initialization of the execution part is determined based on the status identifier in the PMU as a first value, and the PMU... The status flag is configured to the second value; the DDR receives the second power supply signal U2, exits the self-refresh state, and resumes normal access; the SoC controls the reset signal of the DDR, obtains the stored operating status information from the DDR, and restores the operation of the SoC based on the operating status information. For example, it restores the operation of the SoC's non-power-down subsystem based on the non-power-down subsystem operating status information, and restores the operation of the SoC's power-down subsystem based on the power-down subsystem operating status information, i.e., it performs service recovery of the non-power-down subsystem and service recovery of the non-power-down subsystem; then, user-mode services are restored. Where the power-down subsystem includes an ACPU and an MCU, performing service recovery of the non-power-down subsystem may include: first performing MCU service recovery, then performing ACPU service recovery. For example, first, the relevant information of the MCU is obtained from the DDR to restore the operation of the MCU; then, the MCU powers on the bus, restores the clock, and powers on other processors such as the GPU and NPU to restore them, and the MCU powers on the ACPU; the ACPU obtains kernel-mode running status information and user-mode running status information from the DDR, and restores kernel-mode operation and user-mode operation respectively according to the kernel-mode running status information and the user-mode running status information.
[0085] In actual testing, taking a portable PC as an example, if the portable PC adopts the above-mentioned S3, S4 and S5 schemes and the scheme provided in the embodiment of this application (denoted as ULSR) under the same conditions, the following table 1 can be obtained. Table 1 shows the standby power consumption and wake-up time under different schemes.
[0086] Table 1
[0087] As shown in Table 1 above, the portable PC adopts the solution provided in the embodiments of this application. After entering the ultra-low power state, the corresponding standby power consumption can be reduced to less than 50mW, and the wake-up time is controlled to less than 1.5s. This can support the standby days of the portable PC for about 70 days, thereby achieving the ultra-long standby of the portable PC.
[0088] The electronic device provided in this application embodiment can enter an ultra-low power state from a working state and also recover from the ultra-low power state back to the working state. In the ultra-low power state, the SoC is completely powered down, the memory enters a self-refresh state, and the memory stores the SoC's operating state information. When the electronic device needs to recover to the working state, the memory can exit the self-refresh state. After the SoC is powered on, it can perform a power-on operation based on the operating state information stored in the memory to recover to the working state. Moreover, the power-on operation can skip the subsequent boot program of xloader in the complete boot process, so that the electronic device can switch between the working state and the ultra-low power state while simultaneously providing users with both battery life and fast screen-on experience.
[0089] Based on this, embodiments of this application also provide a control method for an electronic device, which can be the electronic device provided above, such as a SoC and a PMU. This method can be used to allow the electronic device to enter an ultra-low power state from an operating state, or to allow the electronic device to return to an operating state from an ultra-low power state.
[0090] In the operating state of the electronic device, the PMU provides a first power supply signal to the SoC and a second power supply signal to the memory; in the ultra-low power state of the electronic device, the PMU stops providing any power supply signal to the SoC and switches the second power supply signal to the memory to a third power supply signal, which is used to maintain the memory in the self-refresh state.
[0091] In one possible embodiment, the method may include: when the electronic device needs to transition from the operating state to the ultra-low power state, the SoC stores its operating state information in the memory and performs a power-down operation; wherein, after the power-down operation is completed, the electronic device enters the ultra-low power state. Optionally, the memory enters a self-refresh state.
[0092] In another possible embodiment, the method may include: the PMU providing a first power supply signal to the SoC in response to a wake-up signal, and switching a third power supply signal to the memory to a second power supply signal; the SoC receiving the first power supply signal and performing a power-on operation based on the operating state information stored in the memory to restore the operating state of the electronic device; wherein the power-on operation includes: a read-only memory (ROM) boot operation, an initial bootloader (xloader) boot operation, and restoring the SoC's operation based on the operating state information, and skipping subsequent bootloader steps of the xloader in the complete boot process during the power-on operation. Optionally, the memory exits a self-refresh state.
[0093] Optionally, the running status information includes user-mode running status information and kernel-mode running status information; and / or, the running status information may include power-down subsystem running status information and non-power-down subsystem running status information.
[0094] For example, the SoC also includes a non-power-down subsystem, and the operating status information includes non-power-down operating status information; in the ultra-low power state of the electronic device, the non-power-down subsystem is powered down: restoring the SoC operation based on the operating status information includes: the non-power-down subsystem restoring operation based on the non-power-down operating status information.
[0095] Furthermore, the method also includes: when the electronic device needs to enter the ultra-low power state from the operating state, the SoC configures the PMU to control the memory reset signal; the PMU controls the memory reset signal in the ultra-low power state of the electronic device.
[0096] Furthermore, the method also includes: when the electronic device needs to enter the ultra-low power state from the working state, the SoC configures the status identifier in the PMU to a first value, the first value being used to indicate that the electronic device enters the ultra-low power state; after the SoC performs the power-on operation, the status identifier is configured to a second value, the second value being used to indicate that the electronic device resumes the working state.
[0097] It is understood that all relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here in the embodiments of this application.
[0098] In another embodiment of this application, an electronic device is provided, as shown in FIG11. This electronic device includes a memory and any of the electronic devices described above. The memory is coupled to the electronic device, for example, to both the SoC and PMU within the electronic device. The memory can be used to store the operating status information of the SoC of the electronic device. Furthermore, the electronic device may also include other components, such as an embedded controller and peripheral devices, including but not limited to: a display screen, keyboard, mouse, touchpad, speaker, and microphone. For a description of the electronic device, please refer to the detailed description above; further details will not be repeated here.
[0099] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. When the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product.
[0100] In another embodiment of this application, a readable storage medium is also provided, which stores computer-executable instructions that are executed by a device (which may be a microcontroller, chip, etc.) or a processor when executing the steps in the above method embodiments.
[0101] In another embodiment of this application, a computer program product is also provided, the computer program product including computer instructions stored in a readable storage medium; at least one processor of the device can read the computer instructions from the readable storage medium, and the at least one processor executes the computer instructions to cause the device to perform the steps in the above method embodiments.
[0102] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. An electronic device, characterized in that, include: System-on-a-Chip (SoC) and Power Management Unit (PMU); The PMU is used for: In the operating state of the electronic device, a first power supply signal is provided to the SoC, and a second power supply signal is provided to the memory; and In the ultra-low power state of the electronic device, any power supply signal to the SoC is stopped, and the second power supply signal to the memory is switched to a third power supply signal, which is used to maintain the memory in a self-refresh state; The SoC is configured to store the SoC's operating state information in the memory and perform a power-down operation when the electronic device needs to enter the ultra-low power state from the operating state; after the power-down operation, the electronic device enters the ultra-low power state. The PMU is also configured to, in response to a wake-up signal, provide the first power supply signal to the SoC, and switch the third power supply signal provided to the memory to the second power supply signal; The SoC is also configured to receive the first power supply signal and perform a power-on operation based on the operating status information stored in the memory to restore the working state of the electronic device; The power-on operation includes: a read-only memory (ROM) boot operation, an initial bootloader (xloader) boot operation, and restoring the SOC to operation based on the running status information. In the power-on operation, the subsequent bootloader of the xloader in the complete boot process is skipped. 2.The electronic device of claim 1, wherein, The operating status information includes user-mode operating status information, kernel-mode operating status information, and software image information of the microcontroller (MCU) used for power consumption control. 3.The electronic device of claim 1 or 2, wherein, The SoC also includes a non-power-down zone subsystem, and the operating status information includes non-power-down zone operating status information; In the ultra-low power state of the electronic device, the non-power-down subsystem is powered down: The process of restoring the SOC operation based on the operating status information includes: the non-power-off zone subsystem restoring operation based on the non-power-off zone operating status information.
4. The electronic device according to any one of claims 1-3, characterized in that, The SoC is also configured to configure the PMU to control the memory reset signal when the electronic device needs to enter the ultra-low power state from the operating state; The PMU is also used to control the reset signal of the memory in the ultra-low power state of the electronic device.
5. The electronic device according to any one of claims 1-4, characterized in that, The SoC is also configured to configure the status identifier in the PMU to a first value when the electronic device needs to enter the ultra-low power state from the working state. The first value is used to indicate that the electronic device enters the ultra-low power state. The SoC is further configured to configure the status identifier as a second value after performing the power-on operation, the second value being used to instruct the electronic device to resume the operating state. 6.A control method of an electronic device, the method comprising: The electronic device includes a system-on-a-chip (SoC) and a power management unit (PMU), and the method includes: In the operating state of the electronic device, the PMU provides a first power supply signal to the SoC and a second power supply signal to the memory; In the ultra-low power state of the electronic device, the PMU stops providing any power supply signal to the SoC and switches the second power supply signal provided to the memory to a third power supply signal, which is used to maintain the memory in a self-refresh state; When the electronic device needs to enter the ultra-low power state from the operating state, the SoC stores the SoC's operating state information in the memory and performs a power-down operation; after the power-down operation, the electronic device enters the ultra-low power state. In response to a wake-up signal, the PMU provides the first power supply signal to the SoC and switches the third power supply signal provided to the memory to the second power supply signal; The SoC receives the first power supply signal and performs a power-on operation based on the operating status information stored in the memory to restore the working state of the electronic device; The power-on operation includes: a read-only memory (ROM) boot operation, an initial bootloader (xloader) boot operation, and restoring the SOC to operation based on the running status information. In the power-on operation, the subsequent bootloader of the xloader in the complete boot process is skipped.
7. The method according to claim 6, characterized in that, The operating status information includes user-mode operating status information, kernel-mode operating status information, and software image information of the microcontroller (MCU) used for power consumption control.
8. The method according to claim 6 or 7, characterized in that, The SoC also includes a non-power-down zone subsystem, and the operating status information includes non-power-down zone operating status information; In the ultra-low power state of the electronic device, the non-power-down subsystem is powered down: The process of restoring the SOC operation based on the operating status information includes: the non-power-off zone subsystem restoring operation based on the non-power-off zone operating status information.
9. The method according to any one of claims 6-8, characterized in that, The method further includes: When the electronic device needs to enter the ultra-low power state from the operating state, the SoC configures the PMU to control the memory reset signal; The PMU controls the reset signal of the memory in the ultra-low power state of the electronic device.
10. The method according to any one of claims 6-9, characterized in that, The method further includes: When the electronic device needs to enter the ultra-low power state from the operating state, the SoC configures the state identifier in the PMU to a first value, which is used to indicate that the electronic device enters the ultra-low power state. After performing the power-on operation, the SoC configures the status identifier to a second value, which is used to instruct the electronic device to resume the operating state.
11. An electronic device, characterized in that, The electronic device includes: a memory, and an electronic device as described in any one of claims 1-5; wherein the memory is coupled to the electronic device and is used to store the operating status information of the SoC in the electronic device.
