diff options
author | Stefan Richter <stefanr@s5r6.in-berlin.de> | 2007-08-25 14:08:19 +0200 |
---|---|---|
committer | Stefan Richter <stefanr@s5r6.in-berlin.de> | 2007-10-17 00:00:05 +0200 |
commit | ee71c2f9ee85117e41ef87357ed8f75d29369b98 (patch) | |
tree | 9bb749909370ec732ed730ca80553908913156af /drivers/bluetooth | |
parent | df8ec2490fed5dd23316bbb2c2e90e59e7d37126 (diff) |
firewire: fw-ohci: enforce read order for selfID generation
It seems unlikely, but access to self_id_cpu[0] could at least in theory
be deferred until after the loop over self_id_cpu[1..n] or even after
the subsequent reg_read. Enforce the desired order by a read barrier.
Also prevent the reg_read from being reordered relative to the for loop.
This isn't necessary if the loop's conditional printk counts as an
implicit barrier, but better make it explicit.
(self_id_cpu[] is a coherent DMA buffer.)
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions