diff options
| author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-09-29 22:29:44 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <rjw@sisk.pl> | 2011-10-04 21:54:26 +0200 |
| commit | 1a9a91525d806f2b3bd8b57b963755a96fd36ce2 (patch) | |
| tree | 511db2ab0871872bce759d35b7ffd22b9d7fc3f5 /fs | |
| parent | PM QoS: Add global notification mechanism for device constraints (diff) | |
| download | linux-1a9a91525d806f2b3bd8b57b963755a96fd36ce2.tar.xz linux-1a9a91525d806f2b3bd8b57b963755a96fd36ce2.zip | |
PM / QoS: Add function dev_pm_qos_read_value() (v3)
To read the current PM QoS value for a given device we need to
make sure that the device's power.constraints object won't be
removed while we're doing that. For this reason, put the
operation under dev->power.lock and acquire the lock
around the initialization and removal of power.constraints.
Moreover, since we're using the value of power.constraints to
determine whether or not the object is present, the
power.constraints_state field isn't necessary any more and may be
removed. However, dev_pm_qos_add_request() needs to check if the
device is being removed from the system before allocating a new
PM QoS constraints object for it, so make it use the
power.power_state field of struct device for this purpose.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions