Re: [PATCH v3 0/2] Re: Problem: lockdep warning with nested instances of i2c-mux

On Thu, May 24, 2018 at 6:52 AM Peter Rosin wrote: > Hi! > Sorry for spamming. At least I'm finding these embarrassing f$&%ups > myself, not that it helps all that much, but... > Changes since v2https://lkml.org/lkml/2018/5/24/176 > -

Re: [PATCH v3 0/2] Re: Problem: lockdep warning with nested instances of i2c-mux

On Thu, May 24, 2018 at 6:52 AM Peter Rosin wrote: > Hi! > Sorry for spamming. At least I'm finding these embarrassing f$&%ups > myself, not that it helps all that much, but... > Changes since v2https://lkml.org/lkml/2018/5/24/176 > - EXPORT_SYMBOL_GPL(rt_mutex_lock_nested) is more

[PATCH v3 0/2] Re: Problem: lockdep warning with nested instances of i2c-mux

Hi! Sorry for spamming. At least I'm finding these embarrassing f$&%ups myself, not that it helps all that much, but... Changes since v2https://lkml.org/lkml/2018/5/24/176 - EXPORT_SYMBOL_GPL(rt_mutex_lock_nested) is more appropriate (the rt_ prefix was missing). Changes since v1

[PATCH v3 0/2] Re: Problem: lockdep warning with nested instances of i2c-mux

Hi! Sorry for spamming. At least I'm finding these embarrassing f$&%ups myself, not that it helps all that much, but... Changes since v2https://lkml.org/lkml/2018/5/24/176 - EXPORT_SYMBOL_GPL(rt_mutex_lock_nested) is more appropriate (the rt_ prefix was missing). Changes since v1

[PATCH v2 0/2] Re: Problem: lockdep warning with nested instances of i2c-mux

Changes since v1: - Further compile tests indicated a missing #define for rt_mutex_lock with lockdep enabled, so that one is added. - I have verified that I don't get any lockdep splat for a local i2c-mux setup with these patches applied, and that I do without them. Again, thanks for the

[PATCH v2 0/2] Re: Problem: lockdep warning with nested instances of i2c-mux

Changes since v1: - Further compile tests indicated a missing #define for rt_mutex_lock with lockdep enabled, so that one is added. - I have verified that I don't get any lockdep splat for a local i2c-mux setup with these patches applied, and that I do without them. Again, thanks for the

Re: Problem: lockdep warning with nested instances of i2c-mux

On 2018-05-24 04:25, John Sperbeck wrote: > If an i2c topology has instances of nested muxes, then a lockdep splat > is produced when when i2c_parent_lock_bus() is called. Here is an > example: > > > WARNING: possible recursive locking detected >

Re: Problem: lockdep warning with nested instances of i2c-mux

On 2018-05-24 04:25, John Sperbeck wrote: > If an i2c topology has instances of nested muxes, then a lockdep splat > is produced when when i2c_parent_lock_bus() is called. Here is an > example: > > > WARNING: possible recursive locking detected >