On Sun, Dec 21, 2014 at 12:34:51AM +0200, Antti Palosaari wrote: > + * @lock_class_key: Custom lock class key for lockdep validator. Use that when > + * regmap in question is used for bus master IO in order to avoid > + * false lockdep nested locking warning. Valid only when regmap > + * default mutex locking is used. Thinking about this further this comment definitely isn't accurate, it's not just bus masters that are potentially affected but also things like clock controllers that might need to be interacted with in order to do I/O. Thinking about those I'm even unsure that a per driver class (which seems to be the idea here) will be enough, it's at least in theory possible that two different instances of the same clock IP (or generic regmap clock controller) will both need to be turned on for this to work. If it was just bus controllers it looks like we can probably just have the clients set a flag saying that's what they are and then define the class in the regmap core but I don't think that's all that's going on here.
Attachment:
signature.asc
Description: Digital signature
