quoted

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.

/Waldek