summaryrefslogtreecommitdiffstats
path: root/CREDITS
diff options
context:
space:
mode:
authorJean Pihet <jean.pihet@newoldbits.com>2012-09-19 14:17:20 +0200
committerRafael J. Wysocki <rjw@sisk.pl>2012-09-19 14:17:20 +0200
commitfc2fb3a075c206927d3fbad251dae82ba82ccf2d (patch)
tree12306571287f05058831654bbe516e54e0e76546 /CREDITS
parentc6a57bfffea5b673e5b4f9aeff85a00607e59077 (diff)
downloadblackbird-op-linux-fc2fb3a075c206927d3fbad251dae82ba82ccf2d.tar.gz
blackbird-op-linux-fc2fb3a075c206927d3fbad251dae82ba82ccf2d.zip
PM QoS: Use spinlock in the per-device PM QoS constraints code
The per-device PM QoS locking requires a spinlock to be used. The reasons are: - an alignement with the PM QoS core code, which is used by the per-device PM QoS code for the constraints lists management. The PM QoS core code uses spinlocks to protect the constraints lists, - some drivers need to use the per-device PM QoS functionality from interrupt context or spinlock protected context. An example of such a driver is the OMAP HSI (high-speed synchronous serial interface) driver which needs to control the IP block idle state depending on the FIFO empty state, from interrupt context. Reported-by: Djamil Elaidi <d-elaidi@ti.com> Signed-off-by: Jean Pihet <j-pihet@ti.com> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud