diff options
| author |   Todd Poynor <toddpoynor@google.com> | 2011-10-04 11:52:29 +0200 |
|---|---|---|
| committer |   Samuel Ortiz <sameo@linux.intel.com> | 2011-10-24 14:09:17 +0200 |
| commit | ab2b9260df67e29d5bd69d989f2f84f8c2ed4238 (patch) | |
| tree | 23ae7c73b270d41656673c6beed9c2dd5344b1d1 /kernel/rtmutex-debug.c | |
| parent | ARM: imx/mx31moboard: use mc13xxx structs instead of removed mc13783 structs (diff) | |
| download | wireguard-linux-ab2b9260df67e29d5bd69d989f2f84f8c2ed4238.tar.xz wireguard-linux-ab2b9260df67e29d5bd69d989f2f84f8c2ed4238.zip | |
mfd: Fix twl6030 lockdep recursion warning on setting wake IRQs
LOCKDEP explicitly sets all irq_desc locks as a single lock-class,
causing "possible recursive locking detected" when the TWL RTC
driver calls through enable_irq_wake to twl6030_irq_set_wake,
which recursively calls irq_set_irq_wake. Although the
irq_desc and lock are different, LOCKDEP treats these as
equivalent, presumably due to problems that can be incurred
when locking more than one irq_desc, so best to avoid this.
Suspend/resume actions implemented as PM notifiers to avoid
touch the TWL core for this.
Signed-off-by: Todd Poynor <toddpoynor@google.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Diffstat (limited to 'kernel/rtmutex-debug.c')
0 files changed, 0 insertions, 0 deletions