7 Nokia Corporation - initial contribution. |
7 Nokia Corporation - initial contribution. |
8 Contributors: |
8 Contributors: |
9 --> |
9 --> |
10 <!DOCTYPE concept |
10 <!DOCTYPE concept |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept id="GUID-113B3755-1797-5D1B-8E07-8A18F5FE1504" xml:lang="en"><title>Power |
12 <concept id="GUID-113B3755-1797-5D1B-8E07-8A18F5FE1504" xml:lang="en"><title>Power States</title><shortdesc>Describes three power states that are defined by the kernel.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 States</title><shortdesc>Describes three power states that are defined by the Kernel.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <ul> |
13 <ul> |
15 <li id="GUID-61A3C566-05AA-5F6D-A9DE-B409C873B119"><p> <i>Off</i> - a state |
14 <li id="GUID-61A3C566-05AA-5F6D-A9DE-B409C873B119"><p> <i>Off</i> - |
16 where the device and all peripherals are powered off or inactive, or are characterised |
15 a state where the device and all peripherals are powered off or inactive, |
17 by negligible power consumption due to current leakage to the electric and |
16 or are characterised by negligible power consumption due to current |
18 electronic circuits that make up the system. This state is achieved as a result |
17 leakage to the electric and electronic circuits that make up the system. |
19 of controlled system shutdown resulting from a user action, an application |
18 This state is achieved as a result of controlled system shutdown resulting |
20 request, UI inactivity, or as a result of accidental loss of power. This may |
19 from a user action, an application request, UI inactivity, or as a |
21 also be achieved as a result of putting the system into a hibernation state. |
20 result of accidental loss of power. This may also be achieved as a |
22 Note that a reboot is necessary to return the system to the <i>Active</i> state; |
21 result of putting the system into a hibernation state. Note that a |
23 this could be a cold reboot, or a warm reboot if the system was put into a |
22 reboot is necessary to return the system to the <i>Active</i> state; |
24 hibernation state. </p> </li> |
23 this could be a cold reboot, or a warm reboot if the system was put |
25 <li id="GUID-275417B2-B8C8-5C93-B576-15543D80CAC9"><p> <i>Standby</i> - a |
24 into a hibernation state. </p> </li> |
26 low power consuming state that results from turning off most system resources |
25 <li id="GUID-275417B2-B8C8-5C93-B576-15543D80CAC9"><p> <i>Standby</i> - a low power consuming state that results from turning off most |
27 (clocks, voltages), peripherals, memory banks (where possible), cpu and internal |
26 system resources (clocks, voltages), peripherals, memory banks (where |
28 logic, while still retaining the state prior to the transition. Typically, |
27 possible), cpu and internal logic, while still retaining the state |
29 the only systems that are active are those that are required to detect the |
28 prior to the transition. Typically, the only systems that are active |
30 events that force the transition back to the Active state (e.g. RTC, clocks |
29 are those that are required to detect the events that force the transition |
31 and Peripherals involved in detecting hardware events). Returning to the Active |
30 back to the Active state (e.g. RTC, clocks and Peripherals involved |
32 state will normally take a far shorter period of time than that required to |
31 in detecting hardware events). Returning to the Active state will |
33 reboot the system. This state is achieved as a result of user action or application |
32 normally take a far shorter period of time than that required to reboot |
|
33 the system. This state is achieved as a result of user action or application |
34 request. </p> </li> |
34 request. </p> </li> |
35 <li id="GUID-A31A5A3C-C7C2-5D15-88B2-828F7E5F60D8"><p> <i>Active</i> - the |
35 <li id="GUID-A31A5A3C-C7C2-5D15-88B2-828F7E5F60D8"><p> <i>Active</i> - the fully active state. </p> </li> |
36 fully active state. </p> </li> |
|
37 </ul> |
36 </ul> |
38 <p>The three power states are defined by the enum values of the <xref href="GUID-87AB8B20-04EE-31D2-8F3D-EA904D05B8D0.dita"><apiname>TPowerState</apiname></xref> enum |
37 <p>The three power states are defined by the enum values of the <xref href="GUID-87AB8B20-04EE-31D2-8F3D-EA904D05B8D0.dita"><apiname>TPowerState</apiname></xref> enum defined in <filepath>e32power.h</filepath>. </p> |
39 defined in <filepath>e32power.h</filepath>. </p> |
|
40 </conbody><related-links> |
38 </conbody><related-links> |
41 <link href="GUID-E09E4418-4DC3-56A3-BFBE-486C9C8D25C9.dita"><linktext>Domain Manager</linktext> |
39 <link href="GUID-E09E4418-4DC3-56A3-BFBE-486C9C8D25C9.dita"><linktext>Domain |
42 </link> |
40 Manager</linktext></link> |
43 <link href="GUID-0C435514-EEC6-5660-BB5F-535790349632.dita"><linktext>Power Management</linktext> |
41 <link href="GUID-0C435514-EEC6-5660-BB5F-535790349632.dita"><linktext>Power |
44 </link> |
42 Management</linktext></link> |
45 </related-links></concept> |
43 </related-links></concept> |