18.12.2012 Views

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

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 />

slave address 1 (0x09) is placed in the embedded controller’s Alarm Address Register <strong>and</strong> the EC’s<br />

Status Register’s Alarm bit is set. The embedded controller then asserts an SCI.<br />

10.1.1.2 Smart Battery Charger with optional System Manager or Selector<br />

A Smart Battery Charger that contains the optional System Manager or Selector function (as<br />

indicated by the ChargerSpecInfo() comm<strong>and</strong> register, 0x11, bit 4) is required to generate an SMBus<br />

Alarm Notify on a battery or AC status change. The content of the Smart Battery Charger with an<br />

optional System Manager, the BatterySystemState() comm<strong>and</strong> register (0x21) (or in the case of an<br />

optional Selector, the SelectorState() (0x01) ), is placed in the EC’s Alarm Data Registers, the Smart<br />

Battery Charger’s slave address (0x09) is placed in the embedded controller’s Alarm Address<br />

Register, <strong>and</strong> the embedded controller’s Status Register’s Alarm bit is set. The embedded controller<br />

then asserts an SCI.<br />

10.1.1.3 Smart Battery System Manager<br />

The Smart Battery System Manager is required to generate an SMBus Alarm Notify on a battery or<br />

AC status change. The content of the Smart Battery System Manager’s BatterySystemState()<br />

comm<strong>and</strong> register (0x01) is placed in the EC’s Alarm Data Registers, the Smart Battery System<br />

Manager’s slave address (0x0A) is placed in the EC’s Alarm Address Register, <strong>and</strong> the embedded<br />

controller’s Status Register’s Alarm bit is set. The embedded controller then asserts an SCI.<br />

10.1.1.4 Smart Battery Selector<br />

The requirements for the Smart Battery Selector are the same as the requirements for the Smart<br />

Battery System Manager, with the exception that the contents of the SelectorState() comm<strong>and</strong><br />

register (0x01) are used instead of BatterySystemState(). The Smart Battery Selector is a subset of<br />

the Smart Battery System Manager <strong>and</strong> does not have the added support for simultaneous charge/<br />

discharge of multiple batteries. The System Manager is the preferred implementation.<br />

10.1.2 Smart Battery Objects<br />

The Smart Battery subsystem requires a number of objects to define its interface. These are<br />

summarized below:<br />

Table 10-231 Smart Battery Objects<br />

Object Description<br />

_HID This is the hardware ID named object that contains a string. For Smart Battery subsystems, this<br />

object returns the value of “ACPI0002.” This identifies the Smart Battery subsystem to the Smart<br />

Battery driver.<br />

_SBS This is the Smart Battery named object that contains a DWORD. This named object returns the<br />

configuration of the Smart Battery.<br />

1. Notice that the 1.0 SMBus protocol specification is ambiguous about the definition of the “slave address”<br />

written into the comm<strong>and</strong> field of the host controller. In this case, the slave address is actually the combination of the<br />

7-bit slave address <strong>and</strong> the Write protocol bit. Therefore, bit 0 of the initiating device’s slave address is aligned to bit<br />

1 of the host controller’s slave comm<strong>and</strong> register, bit 1 of the slave address is aligned to bit 2 of the controller’s slave<br />

comm<strong>and</strong> register, <strong>and</strong> so on.<br />

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba 493

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

Saved successfully!

Ooh no, something went wrong!