30 Apr
2019
30 Apr
'19
3:49 a.m.
I would really like not to see such board specific code added to this driver.
Frankly, I fail to understand why used udelay(11) instead of udelay(10) should result in such a difference on your board. Could you please investigate a bit more and hopefully come up with a "better" solution for this issue?
Thanks, Stefan
Hi Stefan, I think I found what was the issue, just sent a patch series for Omnia, the last patch explains my theory and fixes the issue with one ndelay(100)
Marek