On Monday 14 March 2011, Waldemar.Rymarkiewicz@xxxxxxxxx wrote: > >> No, it's simply there as I have been faceing i2c write error while I > >> do two consecutive writes. > >> The second fails now and then. That's seems to be a chip issue. > >> I will try to investigate this issue. > > > >Ok. It sounds like a bug in the i2c driver, you should also > >take a look there. Maybe it has never had to deal with this > >much write data at once. > > It's been confirmed now that this is how chip is supposed to work and the > driver should not care about this scenario. Upper layers (onfc stack) handle this. > Thus, will simply remove urange_sleep and that's it. It sounds strange that this will be handled in user space, since it won't have any idea if the hardware is available again. I've tried to find the onfc stack that talks to this device but couldn't see it. Do you have a URL for this? Arnd -- 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
