GitHub-Mirror/Star64_linux
2
0
Fork 0
mirror of https://github.com/Fishwaldo/Star64_linux.git synced 2025-04-21 13:53:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

PM / Runtime: Allow _put_sync() from interrupts-disabled context

Browse source 
Currently the use of pm_runtime_put_sync() is not safe from
interrupts-disabled context because rpm_idle() will release the
spinlock and enable interrupts for the idle callbacks.  This enables
interrupts during a time where interrupts were expected to be
disabled, and can have strange side effects on drivers that expected
interrupts to be disabled.

This is not a bug since the documentation clearly states that only
_put_sync_suspend() is safe in IRQ-safe mode.

However, pm_runtime_put_sync() could be made safe when in IRQ-safe
mode by releasing the spinlock but not re-enabling interrupts, which
is what this patch aims to do.

Problem was found when using some buggy drivers that set
pm_runtime_irq_safe() and used _put_sync() in interrupts-disabled
context.

Reported-by: Colin Cross <ccross@google.com>
Tested-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
This commit is contained in:
Kevin Hilman 2011-08-05 21:45:20 +02:00 • committed by Rafael J. Wysocki
parent fe202fde50
commit 02b26774af
2 changed files with 13 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Documentation/power/runtime_pm.txt
View file

@ -54,11 +54,10 @@ referred to as subsystem-level callbacks in what follows.
By default, the callbacks are always invoked in process context with interrupts By default, the callbacks are always invoked in process context with interrupts
enabled. However, subsystems can use the pm_runtime_irq_safe() helper function enabled. However, subsystems can use the pm_runtime_irq_safe() helper function
to tell the PM core that a device's ->runtime_suspend() and ->runtime_resume() to tell the PM core that a device's ->runtime_suspend() and ->runtime_resume()
callbacks should be invoked in atomic context with interrupts disabled callbacks should be invoked in atomic context with interrupts disabled.
(->runtime_idle() is still invoked the default way). This implies that these This implies that these callback routines must not block or sleep, but it also
callback routines must not block or sleep, but it also means that the means that the synchronous helper functions listed at the end of Section 4 can
synchronous helper functions listed at the end of Section 4 can be used within be used within an interrupt handler or in an atomic context.
an interrupt handler or in an atomic context.
The subsystem-level suspend callback is _entirely_ _responsible_ for handling The subsystem-level suspend callback is _entirely_ _responsible_ for handling
the suspend of the device as appropriate, which may, but need not include the suspend of the device as appropriate, which may, but need not include
@ -483,6 +482,7 @@ pm_runtime_suspend()
pm_runtime_autosuspend() pm_runtime_autosuspend()
pm_runtime_resume() pm_runtime_resume()
pm_runtime_get_sync() pm_runtime_get_sync()
pm_runtime_put_sync()
pm_runtime_put_sync_suspend() pm_runtime_put_sync_suspend()
5. Runtime PM Initialization, Device Probing and Removal 5. Runtime PM Initialization, Device Probing and Removal

6
drivers/base/power/runtime.c
View file

@ -226,10 +226,16 @@ static int rpm_idle(struct device *dev, int rpmflags)
callback = NULL; callback = NULL;
if (callback) { if (callback) {
if (dev->power.irq_safe)
spin_unlock(&dev->power.lock);
else
spin_unlock_irq(&dev->power.lock); spin_unlock_irq(&dev->power.lock);
callback(dev); callback(dev);
if (dev->power.irq_safe)
spin_lock(&dev->power.lock);
else
spin_lock_irq(&dev->power.lock); spin_lock_irq(&dev->power.lock);
} }