Merge branch 'acpi-pm' into pm-core

		This attribute has no effect on system-wide suspend/resume and

		hibernation.

What:		/sys/devices/.../power/pm_qos_remote_wakeup

Date:		September 2012

Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>

Description:

		The /sys/devices/.../power/pm_qos_remote_wakeup attribute

		is used for manipulating the PM QoS "remote wakeup required"

		flag.  If set, this flag indicates to the kernel that the

		device is a source of user events that have to be signaled from

		its low-power states.

		Not all drivers support this attribute.  If it isn't supported,

		it is not present.

		This attribute has no effect on system-wide suspend/resume and

		hibernation.

To enumerate platform Low Power Idle states, Intel platforms are using

“Low Power Idle Table” (LPIT). More details about this table can be

downloaded from:

http://www.uefi.org/sites/default/files/resources/Intel_ACPI_Low_Power_S0_Idle.pdf

Residencies for each low power state can be read via FFH

(Function fixed hardware) or a memory mapped interface.

On platforms supporting S0ix sleep states, there can be two types of

residencies:

- CPU PKG C10 (Read via FFH interface)

- Platform Controller Hub (PCH) SLP_S0 (Read via memory mapped interface)

The following attributes are added dynamically to the cpuidle

sysfs attribute group:

	/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us

	/sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us

The "low_power_idle_cpu_residency_us" attribute shows time spent

by the CPU package in PKG C10

The "low_power_idle_system_residency_us" attribute shows SLP_S0

residency, or system time spent with the SLP_S0# signal asserted.

This is the lowest possible system power state, achieved only when CPU is in

PKG C10 and all functional blocks in PCH are in a low power state.

The target values of resume latency and active state latency tolerance are

simply the minimum of the request values held in the parameter list elements.

The PM QoS flags aggregate value is a gather (bitwise OR) of all list elements'

values.  Two device PM QoS flags are defined currently: PM_QOS_FLAG_NO_POWER_OFF

and PM_QOS_FLAG_REMOTE_WAKEUP.

values.  One device PM QoS flag is defined currently: PM_QOS_FLAG_NO_POWER_OFF.

Note: The aggregated target values are implemented in such a way that reading

the aggregated value does not require any locking mechanism.

pm_qos_resume_latency_us from the device's power directory.

int dev_pm_qos_expose_flags(device, value)

Add a request to the device's PM QoS list of flags and create sysfs attributes

pm_qos_no_power_off and pm_qos_remote_wakeup under the device's power directory

allowing user space to change these flags' value.

Add a request to the device's PM QoS list of flags and create sysfs attribute

pm_qos_no_power_off under the device's power directory allowing user space to

change the value of the PM_QOS_FLAG_NO_POWER_OFF flag.

void dev_pm_qos_hide_flags(device)

Drop the request added by dev_pm_qos_expose_flags() from the device's PM QoS list

of flags and remove sysfs attributes pm_qos_no_power_off and pm_qos_remote_wakeup

under the device's power directory.

of flags and remove sysfs attribute pm_qos_no_power_off from the device's power

directory.

Notification mechanisms:

The per-device PM QoS framework has a per-device notification tree.

config ACPI_SPCR_TABLE

	bool

config ACPI_LPIT

	bool

	depends on X86_64

	default y

config ACPI_SLEEP

	bool

	depends on SUSPEND || HIBERNATION

acpi-$(CONFIG_ACPI_NUMA)	+= numa.o

acpi-$(CONFIG_ACPI_PROCFS_POWER) += cm_sbs.o

acpi-y				+= acpi_lpat.o

acpi-$(CONFIG_ACPI_LPIT)	+= acpi_lpit.o

acpi-$(CONFIG_ACPI_GENERIC_GSI) += irq.o

acpi-$(CONFIG_ACPI_WATCHDOG)	+= acpi_watchdog.o