diff options
| author | Mika Westerberg <[email protected]> | 2015-07-27 18:03:56 +0300 |
|---|---|---|
| committer | Lee Jones <[email protected]> | 2015-07-28 08:50:41 +0100 |
| commit | 13b2c4a0c3b1cd37ee6bcfbb5b6e2b94e9a75364 (patch) | |
| tree | 016216659f73b115aeaaa4ce712021dd67e2c551 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | bc0195aad0daa2ad5b0d76cce22b167bc3435590 (diff) | |
PM / QoS: Make it possible to expose device latency tolerance to userspace
Typically when a device is created the bus core it belongs to (for example
PCI) does not know if the device supports things like latency tolerance.
This is left to the driver that binds to the device in question. However,
at that time the device has already been created and there is no way to set
its dev->power.set_latency_tolerance anymore.
So follow what has been done for other PM QoS attributes as well and allow
drivers to expose and hide latency tolerance from userspace, if the device
supports it.
Acked-by: Rafael J. Wysocki <[email protected]>
Signed-off-by: Mika Westerberg <[email protected]>
Signed-off-by: Andy Shevchenko <[email protected]>
Signed-off-by: Lee Jones <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions