tree 23ae7c73b270d41656673c6beed9c2dd5344b1d1
parent d3efa4edd5a3b90aff813524aeece01d73d2279b
author Todd Poynor <toddpoynor@google.com> 1317721949 +0200
committer Samuel Ortiz <sameo@linux.intel.com> 1319458157 +0200

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>