Guenter, thanks for the update
> Ultimately, the real problem is how i2c-dev accesses a client, not how > i2c client drivers (who assume they have exclusive access to a chip) > handle multi-command sequences. Forcing extensive locking on all drivers > because of i2c-dev just doesn't seem to be the right thing to do. I agree. i2c-dev is too much of a special case. And since at24 has its own lock (I missed that), your patch might as well be good enough to be applied, I'd think. Thanks for this work!
signature.asc
Description: Digital signature
