On Mon, Sep 19, 2016 at 10:01:49AM +0200, Peter Rosin wrote: > Or, do what the i2c-mux code is doing and use an rt_mutex instead > of an ordinary mutex. That way you are very sure to not get any > lockdep splat ... at all. Ok, sorry, that was not a serious > suggestion, but it would be a tad bit simpler to implement... So I find it weird that people use rt_mutex as a locking primitive, since its only that one lock that then does PI and all the other locks that are related still create inversions. In any case, since people have started doing this, adding lockdep support for rt_mutex is on the todo _somewhere_, so don't expect that to avoid splats forever. -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
