On 12/19/2014 03:45 PM, Lars-Peter Clausen wrote:
On 12/19/2014 11:58 AM, Antti Palosaari wrote:
On 12/18/2014 11:34 PM, Lars-Peter Clausen wrote:
On 12/18/2014 10:05 PM, Antti Palosaari wrote:
lockdep complains recursive locking and deadlock when two different
regmap instances are called in a
On 12/19/2014 11:58 AM, Antti Palosaari wrote:
On 12/18/2014 11:34 PM, Lars-Peter Clausen wrote:
On 12/18/2014 10:05 PM, Antti Palosaari wrote:
lockdep complains recursive locking and deadlock when two different
regmap instances are called in a nested order. That happen easily
for example when
On 12/18/2014 11:34 PM, Lars-Peter Clausen wrote:
On 12/18/2014 10:05 PM, Antti Palosaari wrote:
lockdep complains recursive locking and deadlock when two different
regmap instances are called in a nested order. That happen easily
for example when both I2C client and muxed/repeater I2C adapter a
On 12/18/2014 10:05 PM, Antti Palosaari wrote:
lockdep complains recursive locking and deadlock when two different
regmap instances are called in a nested order. That happen easily
for example when both I2C client and muxed/repeater I2C adapter are
using regmap. As a solution, pass regmap name fo
lockdep complains recursive locking and deadlock when two different
regmap instances are called in a nested order. That happen easily
for example when both I2C client and muxed/repeater I2C adapter are
using regmap. As a solution, pass regmap name for lockdep in order
to force lockdep validate regm
