Drivers as documentation
Drivers as documentation
Posted Nov 25, 2011 14:44 UTC (Fri) by juliank (guest, #45896)In reply to: Drivers as documentation by jzbiciak
Parent article: Drivers as documentation
> Memory ordering issue, and a barrier of some sort is required?
> Does the lockup happen on the same chip as the original
> usleep-less Android implementation?
> Does the lockup happen on the same chip as the original
> usleep-less Android implementation?
Seems I misremembered. It does not lock up, it just sends
incomplete messages. I added an udelay(100) in commit
de839b8f06bc5dd3f5037c4409a720cbb9bf21c3 [1] which seems to
prevent that.
[1] https://git.kernel.org/?p=linux/kernel/git/torvalds/linux...