27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Processor <strong>Configuration</strong> <strong>and</strong> Control<br />

8.4.5.5 _TDL (T-state Depth Limit)<br />

This optional object evaluates to the _TSS entry number of the lowest power throttling state that<br />

OSPM may use. _TDL enables the platform to limit the amount of performance reduction that<br />

OSPM may invoke using processor throttling controls in an attempt to alleviate an adverse thermal<br />

condition. OSPM may choose the corresponding state entry in the _TSS as indicated by the value<br />

returned by the _TDL object or a higher performance (lower numbered) state entry in the _TSS<br />

down to <strong>and</strong> including the _TSS entry number returned by the _TPC object or the first entry in the<br />

table (if _TPC is not implemented). The value returned by the _TDL object must be greater than or<br />

equal to the value returned by the _TPC object or the corresponding value to the last entry in the<br />

_TSS if _TPC is not implemented. In the event of a conflict between the values returned by the<br />

evaluation of the _TDL <strong>and</strong> _TPC objects, OSPM gives precedence to the _TPC object, limiting<br />

power consumption.<br />

Arguments:<br />

None<br />

Return Value:<br />

An Integer containing the Throttling Depth Limit _TSS entry number:<br />

0 – throttling disabled.<br />

1 – state 1 is the lowest power T-state available.<br />

2 – state 2 is the lowest power T-state available.<br />

…<br />

n – state n is the lowest power T-state available.<br />

In order for the platform to dynamically indicate the limit of performance reduction that is available<br />

for OSPM use, Notify events on the processor object of type 0x82 will cause OSPM to reevaluate<br />

any _TDL object in the processor’s object list. This allows AML code to notify OSPM when the<br />

number of supported throttling states may have changed as a result of an asynchronous event. OSPM<br />

ignores _TDL Notify events on platforms that support P-states unless the platform has limited<br />

OSPM’s use of P-states to the lowest power P-state. OSPM may choose to disregard any platform<br />

conveyed T-state depth limits when the platform enables OSPM usage of other than the lowest<br />

power P-state.<br />

8.4.6 Processor Performance Control<br />

Processor performance control is implemented through three optional objects whose presence<br />

indicates to OSPM that the platform <strong>and</strong> CPU are capable of supporting multiple performance states.<br />

The platform must supply all three objects if processor performance control is implemented. The<br />

platform must expose processor performance control objects for either all or none of its processors.<br />

The processor performance control objects define the supported processor performance states, allow<br />

the processor to be placed in a specific performance state, <strong>and</strong> report the number of performance<br />

states currently available on the system.<br />

In a multiprocessing environment, all CPUs must support the same number of performance states<br />

<strong>and</strong> each processor performance state must have identical performance <strong>and</strong> power-consumption<br />

parameters. Performance objects must be present under each processor object in the system for<br />

OSPM to utilize this feature.<br />

Version 6.0 469

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

Saved successfully!

Ooh no, something went wrong!