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.

ACPI-Defined Devices <strong>and</strong> Device-Specific Objects<br />

The OS derives the user’s display brightness preference (this reference value) either from the<br />

Brightness Control Levels (_BCL) object or another OS-specific mechanism. See Section 9.2.8,<br />

“Relationship to Backlight Control Methods”, for more information.<br />

9.2.6 _ALP (Ambient Light Polling)<br />

This optional object evaluates to a recommended polling frequency (in tenths of seconds) for this<br />

ambient light sensor. A value of zero – or the absence of this object when other ALS objects are<br />

defined – indicates that OSPM does not need to poll the sensor in order to detect meaningful changes<br />

in ambient light (the hardware is capable of generating asynchronous notifications).<br />

The use of polling is allowed but strongly discouraged by this specification. OEMs should design<br />

systems that asynchronously notify OSPM whenever a meaningful change in the ambient light<br />

occurs—relieving the OS of the overhead associated with polling.<br />

This value is specified as tenths of seconds. For example, a value of 10 would be used to indicate a 1<br />

second polling frequency. As this is a recommended value, OSPM will consider other factors when<br />

determining the actual polling frequency to use.<br />

Arguments:<br />

None<br />

Return Value:<br />

An Integer containing the recommended polling frequency in tenths of seconds<br />

0 – Polling by the host OS is not required<br />

Other –<br />

9.2.7 Ambient Light Sensor Events<br />

The recommended polling frequency in tenths of seconds<br />

To communicate meaningful changes in ALS illuminance to OSPM, AML code should issue a<br />

Notify(als_device, 0x80) whenever the lux reading changes more than 10% (from the last<br />

reading that resulted in a notification). OSPM receives this notification <strong>and</strong> evaluates the _ALI<br />

control method to determine the current ambient light status. The OS then adjusts the display<br />

brightness based upon its ALS policy (derived from _ALR).<br />

The definition of what constitutes a meaningful change is left to the system integrator, but should be<br />

at a level of granularity that provides an appropriate response without overly taxing the system with<br />

unnecessary interrupts. For example, an ALS configuration may be tuned to generate events for all<br />

changes in ambient light illuminance that result in a minimum ±5% display brightness response (as<br />

defined by _ALR).<br />

To communicate meaningful changes in ALS color temperature to OSPM, AML code should issue a<br />

Notify(als_device, 0x81) whenever the lux reading changes more than 10% (from the last<br />

reading that resulted in a notification). OSPM receives this notification <strong>and</strong> evaluates the _ALT <strong>and</strong><br />

_ALC control method to determine the current ambient light color temperature.<br />

To communicate meaningful changes in ALS response to OSPM, AML code should issue a<br />

Notify(als_device, 0x82) whenever the set of points used to convey ambient light<br />

response has changed. OSPM receives this notification <strong>and</strong> evaluates the _ALR object to determine<br />

the current response points.<br />

Version 6.0 505

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

Saved successfully!

Ooh no, something went wrong!