Hi David, On Fri, 23 Jan 2009 01:39:38 -0800, David Brownell wrote: > On Friday 23 January 2009, Jean Delvare wrote: > > David, can you please comment on the proposed change? > > If it's a legacy driver, it will already have been decoupled > from devices, so the nastiest bit of stuff will have gotten > the protection it needs. New-style drivers shouldn't care > about the legacy stuff at all. So that much looks plausible. > > But I don't have the patience to really analyse the other > locking implications; there were some rude and un-obvious > things lurking there, including abuse of complete() for > the legacy i2c_client lifecycle. This was my conclusion as well. I think I'll try Rodoflo's patch locally and see if anything breaks. If things appear to work, I am ready to push the patch upstream, but obviously if anyone reports a locking issue after that, it would have to be reverted. In the meantime I will try to find time again to convert more legacy drivers. My feeling is that we won't do much progress on multiplexing before we get rid of legacy drivers and their custom locking model. -- Jean Delvare -- 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
