On Tue, 10 Feb 2015, Peter Ujfalusi wrote: > Add struct lock_class_key to omap_hwmod struct and use it to set unique > lockdep class per hwmod. > This will ensure that lockdep will know that each omap_hwmod->_lock should > be treated as separate class and will not give false warning about deadlock > or other issues due to nested use of hwmods. > DRA7x's ATL hwmod is one example for this since McASP can select ATL clock > as functional clock, which will trigger nested oh->_lock usage. This will > trigger false warning from lockdep validator as it is dealing with classes > and for it all hwmod clocks are the same class. > > Suggested-by: Peter Zijlstra <peterz@xxxxxxxxxxxxx> > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@xxxxxx> Thanks queued for v3.20-rc. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
