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.

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

Package Element Element Object Type Actual Valid Data Width<br />

03 – Maximum Sector Number Integer WORD<br />

04 – Maximum Head Number Integer WORD<br />

05 – Disk_specify_1 Integer BYTE<br />

06 – Disk_specify_2 Integer BYTE<br />

07 – Disk_motor_wait Integer BYTE<br />

08 – Disk_sector_siz Integer BYTE<br />

09 – Disk_eot Integer BYTE<br />

10 – Disk_rw_gap Integer BYTE<br />

11 – Disk_dtl Integer BYTE<br />

12 – Disk_formt_gap Integer BYTE<br />

13 – Disk_fill Integer BYTE<br />

14 – Disk_head_sttl Integer BYTE<br />

15 – Disk_motor_strt Integer BYTE<br />

9.9.3 _FDM (Floppy Disk Drive Mode)<br />

This control method switches the mode (300 RPM or 360 RPM) of all floppy disk drives attached to<br />

this controller. If this control method is implemented, the platform must reset the mode of all drives<br />

to 300RPM mode after a Dx to D0 transition of the controller.<br />

Arguments: (1)<br />

Arg0 – An Integer containing the new drive mode<br />

0 – Set the mode of all drives to 300 RPM mode<br />

1 – Set the mode of all drives to 360 RPM mode<br />

Return Value:<br />

None<br />

9.10 GPE Block Device<br />

The GPE Block device is an optional device that allows a system designer to describe GPE blocks<br />

beyond the two that are described in the FADT. Control methods associated with the GPE pins of<br />

GPE block devices exist as children of the GPE Block device, not within the \_GPE namespace.<br />

Because GPE block devices are meant as an extension to the GPE blocks defined in the FADT, <strong>and</strong><br />

that portion of the FADT is to be ignored in hardware-reduced ACPI, GPE block devices are not<br />

supported in hardware-reduced ACPI.<br />

A GPE Block device consumes I/O or memory address space, as specified by its _PRS or _CRS<br />

child objects. The interrupt vector used by the GPE block does not need to be the same as the<br />

SCI_INT field. The interrupt used by the GPE block device is specified in the _CRS <strong>and</strong> _PRS<br />

methods associated with the GPE block. The _CRS of a GPE Block device may only specify a single<br />

register address range, either I/O or memory. This range contains two registers: the GPE status <strong>and</strong><br />

enable registers. Each register’s length is defined as half of the length of the _CRS-defined register<br />

address range.<br />

516 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!