Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification
FACP - Flag
USE_PLATFORM_CLO
CK
1 15 A value of one indicates that OSPM should use a platform
provided timer to drive any monotonically non-decreasing
counters, such as OSPM performance counter services.
Which particular platform timer will be used is OSPM specific,
however, it is recommended that the timer used is based on
the following algorithm: If the HPET is exposed to OSPM,
OSPM should use the HPET. Otherwise, OSPM will use the
ACPI power management timer. A value of one indicates that
the platform is known to have a correctly implemented ACPI
power management timer.
A platform may choose to set this flag if a internal processor
clock (or clocks in a multi-processor configuration) cannot
provide consistent monotonically non-decreasing counters.
Note: If a value of zero is present, OSPM may arbitrarily
choose to use an internal processor clock or a platform timer
clock for these operations. That is, a zero does not imply that
OSPM will necessarily use the internal processor clock to
generate a monotonically non-decreasing counter to the
system.
S4_RTC_STS_VALID 1 16 A one indicates that the contents of the RTC_STS flag is valid
when waking the system from S4.
See Table 4-16 – PM1 Status Registers Fixed Hardware
Feature Status Bits for more information. Some existing
systems do not reliably set this input today, and this bit allows
OSPM to differentiate correctly functioning platforms from
platforms with this errata.
REMOTE_POWER_ON
_CAPABLE
FORCE_
APIC_CLUSTER_MOD
EL
Bit
Length
Bit
Offset
Description
1 17 A one indicates that the platform is compatible with remote
power- on.
That is, the platform supports OSPM leaving GPE wake
events armed prior to an S5 transition. Some existing
platforms do not reliably transition to S5 with wake events
enabled (for example, the platform may immediately generate
a spurious wake event after completing the S5 transition).
This flag allows OSPM to differentiate correctly functioning
platforms from platforms with this type of errata.
1 18 A one indicates that all local APICs must be configured for the
cluster destination model when delivering interrupts in logical
mode.
If this bit is set, then logical mode interrupt delivery operation
may be undefined until OSPM has moved all local APICs to
the cluster model.
Note that the cluster destination model doesn’t apply to
Itanium Processor Family (IPF) local SAPICs. This bit is
intended for xAPIC based machines that require the cluster
destination model even when 8 or fewer local APICs are
present in the machine.
126 April, 2015 Version 6.0