27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

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

Proximity Domain 0 1 2 3 4<br />

1 15 10 16 24 21<br />

2 20 16 10 12 14<br />

3 18 24 12 10 23<br />

4 17 21 14 23 10<br />

The new node’s _SLI object would evaluate to a buffer containing [17,21,14,23,10,17,21,14,23,10].<br />

Note: Some systems support interleave memory across the nodes. The SLIT representation of these<br />

systems is implementation specific.<br />

6.2.16 _SRS (Set Resource Settings)<br />

This optional control method takes one byte stream argument that specifies a new resource<br />

allocation for a device. The resource descriptors in the byte stream argument must be specified<br />

exactly as listed in the _CRS byte stream – meaning that the identical resource descriptors must<br />

appear in the identical order, resulting in a buffer of exactly the same length. Optimizations such as<br />

changing an IRQ descriptor to an IRQNoFlags descriptor (or vice-versa) must not be performed.<br />

Similarly, changing StartDependentFn to StartDependentFnNoPri is not allowed. A _CRS object<br />

can be used as a template to ensure that the descriptors are in the correct format. For more<br />

information, see the _CRS object definition.<br />

The settings must take effect before the _SRS control method returns.<br />

This method must not reference any operation regions that have not been declared available by a<br />

_REG method.<br />

If the device is disabled, _SRS enables the device at the specified resources. _SRS is not used to<br />

disable a device; use the _DIS control method instead.<br />

Arguments: (1)<br />

Arg0 – A Buffer containing a Resource Descriptor byte stream<br />

Return Value:<br />

None<br />

6.2.17 _CCA (Cache Coherency Attribute)<br />

The _CCA object returns whether or not a bus-master device supports hardware managed cache<br />

coherency. Expected values are 0 to indicate it is not supported, <strong>and</strong> 1 to indicate that it is supported.<br />

All other values are reserved.<br />

On platforms for which existing default cache-coherency behavior of the OS is not adequate, _CCA<br />

enables the OS to adapt to the differences. If used, _CCA must be included under all bus-mastercapable<br />

devices defined as children of \_SB, to ensure that the operating system knows when it can<br />

rely on hardware managed cache coherency. The value of _CCA is inherited by all descendants of<br />

these devices, so it need not be repeated for their children devices <strong>and</strong> will be ignored by OSPM if it<br />

is provided there. This includes slave devices on a shared DMA controller; thus these DMA<br />

controllers must also be defined in the namespace under the System Bus <strong>and</strong> include a _CCA object.<br />

328 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!