5 Jun
2015
5 Jun
'15
7:13 p.m.
On Fri, Jun 05, 2015 at 12:53:27PM +0200, Lars-Peter Clausen wrote:
Now the issue here is that we have nested regmap instances, meaning one regmap instances uses another instance in its read/write implementation.
Ah, that sounds more familiar than unlocking in different orders.
I think Antti submitted some patches to attend to fix this, but there were still issues with the patches and they never got merged.
IIRC his patch was adding the ability for drivers to override the lock class which wasn't exactly fixing the problem but rather providing a different way to try to work around it in drivers.