On Wed, Jul 08, 2015 at 11:32:42AM +0800, Nicolas Boichat wrote:
> On Tue, Jul 7, 2015 at 8:13 PM, Mark Brown wrote:
> > On Wed, Jul 01, 2015 at 12:43:59PM +0800, Nicolas Boichat wrote:
> >> (this also applies to all other regmap_init functions...). We do not want
> >> to
> >> document the lock_
On Tue, Jul 7, 2015 at 8:13 PM, Mark Brown wrote:
> On Wed, Jul 01, 2015 at 12:43:59PM +0800, Nicolas Boichat wrote:
>
>> (this also applies to all other regmap_init functions...). We do not want to
>> document the lock_key/name parameters, so we could either leave it like that,
>> or move all the
On Wed, Jul 01, 2015 at 12:43:59PM +0800, Nicolas Boichat wrote:
> (this also applies to all other regmap_init functions...). We do not want to
> document the lock_key/name parameters, so we could either leave it like that,
> or move all the documentation to regmap.h, in front of the respective ma
Lockdep validator complains about recursive locking and deadlock
when two different regmap instances are called in a nested order.
That happens anytime a regmap read/write call needs to access
another regmap.
This is because, for performance reason, lockdep groups all locks
initialized by the same
4 matches
Mail list logo
