Hi Wolfram, arno@xxxxxxxxxxxx (Arnaud Ebalard) writes: > Wolfram Sang <wsa@xxxxxxxxxxxxx> writes: > >>> does nothing fancy either. While debugging I ended up on Debian bug >>> #622325 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622325) which >>> made the driver a little less suspect when a revert of commit eda6bee6c7 >>> fixed the issue for me. >> >> Either wait for 3.11 or pick 4243fa0bad551b8c8d4ff7104e8fd557ae848845 >> "(I2C: mv64xxx: fix race between FSM/interrupt and process context") >> from my for-next branch. (Note the other patches from Russell, probably >> all worth to pick). > > Thanks for the tip. Will try it tomorrow. Done. It works as expected, i.e. no i2c lock at boot on my ReadynNAS 102 once applied. Note that I had to also apply other patches from Russel on which this specific commit somewhat depends. >> Would be nice if you could pass the info to the Debian bug as well. Done as well. I put you in the Cc: list. Thanks for your work, Cheers, a+ -- 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
