diff options
| author | Suresh Siddha <suresh.b.siddha@intel.com> | 2012-04-10 00:41:44 +0200 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2012-04-10 11:42:07 +0200 |
| commit | fa4da365bc7772c2cd6d5405bdf151612455f957 (patch) | |
| tree | a688173e5ba7428e934dee1ea2905c2bbe92ef50 /Documentation/rt-mutex-design.txt | |
| parent | itimer: Use printk_once instead of WARN_ONCE (diff) | |
| download | linux-fa4da365bc7772c2cd6d5405bdf151612455f957.tar.xz linux-fa4da365bc7772c2cd6d5405bdf151612455f957.zip | |
clockevents: tTack broadcast device mode change in tick_broadcast_switch_to_oneshot()
In the commit 77b0d60c5adf39c74039e2142a1d3cd1e4d53799,
"clockevents: Leave the broadcast device in shutdown mode when not needed",
we were bailing out too quickly in tick_broadcast_switch_to_oneshot(),
with out tracking the broadcast device mode change to 'TICKDEV_MODE_ONESHOT'.
This breaks the platforms which need broadcast device oneshot services during
deep idle states. tick_broadcast_oneshot_control() thinks that it is
in periodic mode and fails to take proper decisions based on the
CLOCK_EVT_NOTIFY_BROADCAST_[ENTER, EXIT] notifications during deep
idle entry/exit.
Fix this by tracking the broadcast device mode as 'TICKDEV_MODE_ONESHOT',
before leaving the broadcast HW device in shutdown mode if there are no active
requests for the moment.
Reported-and-tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: johnstul@us.ibm.com
Link: http://lkml.kernel.org/r/1334011304.12400.81.camel@sbsiddha-desk.sc.intel.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'Documentation/rt-mutex-design.txt')
0 files changed, 0 insertions, 0 deletions