27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

4.8.2.4 Real Time Clock Alarm<br />

If implemented, the Real Time Clock (RTC) alarm must generate a hardware wake event when in<br />

the sleeping state. The RTC can be programmed to generate an alarm. An enabled RTC alarm can be<br />

used to generate a wake event when the system is in a sleeping state. ACPI provides for additional<br />

hardware to support OSPM in determining that the RTC was the source of the wake event: the<br />

RTC_STS <strong>and</strong> RTC_EN bits. Although these bits are optional, if supported they must be<br />

implemented as described here.<br />

If the RTC_STS <strong>and</strong> RTC_EN bits are not supported, OSPM will attempt to identify the RTC as a<br />

possible wake source; however, it might miss certain wake events. If implemented, the RTC wake<br />

feature is required to work in the following sleeping states: S1-S3. S4 wake is optional <strong>and</strong><br />

supported through the RTC_S4 flag within the FADT (if set, then the platform supports RTC wake<br />

in the S4 state) 1 .<br />

When the RTC generates a wake event the RTC_STS bit will be set. If the RTC_EN bit is set, an<br />

RTC hardware power management event will be generated (which will wake the system from a<br />

sleeping state, provided the battery low signal is not asserted).<br />

Real Time Clock<br />

(RTC)<br />

RTC_STS<br />

PM1x_STS.10<br />

RTC Wake-up<br />

Event<br />

RTC_EN<br />

PM1x_EN.10<br />

Figure 4-19 RTC Alarm<br />

The RTC wake event status <strong>and</strong> enable bits are an optional fixed hardware feature <strong>and</strong> a flag within<br />

the FADT (FIX_RTC) indicates if the register bits are to be used by OSPM. If the RTC wake event<br />

status <strong>and</strong> enable bits are implemented in fixed hardware, OSPM can determine if the RTC was the<br />

source of the wake event without loading the entire OS. This also gives the platform the capability of<br />

indicating an RTC wake source without consuming a GPE bit, as would be required if RTC wake<br />

was not implemented using the fixed hardware RTC feature. If the fixed hardware feature event bits<br />

are not supported, then OSPM will attempt to determine this by reading the RTC’s status field. If the<br />

platform implements the RTC fixed hardware feature, <strong>and</strong> this hardware consumes resources, the<br />

_FIX method can be used to correlate these resources with the fixed hardware. See Section 6.2.5,<br />

“_FIX (Fixed Register Resource Provide”, for details.<br />

OSPM supports enhancements over the existing RTC device (which only supports a 99 year date <strong>and</strong><br />

24-hour alarm). Optional extensions are provided for the following features:<br />

Day Alarm.<br />

The DAY_ALRM field points to an optional CMOS RAM location that selects the<br />

day within the month to generate an RTC alarm.<br />

1. Notice that the G2/S5 “soft off” <strong>and</strong> the G3 “mechanical off” states are not sleeping states. The OS will disable<br />

the RTC_EN bit prior to entering the G2/S5 or G3 states regardless.<br />

82 April, 2015 Version 6.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!