summaryrefslogtreecommitdiffstats
path: root/Documentation/spi
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2012-10-24 02:08:18 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2012-10-24 02:08:18 +0200
commite39473d0b9448e770f49b0b15e514be884264438 (patch)
treea6fbf50c1fcd8e7cfd176425384a82fe06d3cadd /Documentation/spi
parentae0fb4b72c8db7e6c4ef32bc58a43a759ad414b9 (diff)
downloadop-kernel-dev-e39473d0b9448e770f49b0b15e514be884264438.zip
op-kernel-dev-e39473d0b9448e770f49b0b15e514be884264438.tar.gz
PM / QoS: Make it possible to expose PM QoS device flags to user space
Define two device PM QoS flags, PM_QOS_FLAG_NO_POWER_OFF and PM_QOS_FLAG_REMOTE_WAKEUP, and introduce routines dev_pm_qos_expose_flags() and dev_pm_qos_hide_flags() allowing the caller to expose those two flags to user space or to hide them from it, respectively. After the flags have been exposed, user space will see two additional sysfs attributes, pm_qos_no_power_off and pm_qos_remote_wakeup, under the device's /sys/devices/.../power/ directory. Then, writing 1 to one of them will update the PM QoS flags request owned by user space so that the corresponding flag is requested to be set. In turn, writing 0 to one of them will cause the corresponding flag in the user space's request to be cleared (however, the owners of the other PM QoS flags requests for the same device may still request the flag to be set and it may be effectively set even if user space doesn't request that). Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Reviewed-by: Jean Pihet <j-pihet@ti.com> Acked-by: mark gross <markgross@thegnar.org>
Diffstat (limited to 'Documentation/spi')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud