Commit 2d7f1d1c authored by Eli Billauer's avatar Eli Billauer Committed by Greg Kroah-Hartman

staging: xillybus: Removed read barrier at beginning of ISR

The comment (also removed) explains why it was there in the first place, but
that doesn't make much sense.
Signed-off-by: default avatarEli Billauer <eli.billauer@gmail.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 9959078c
...@@ -133,17 +133,9 @@ irqreturn_t xillybus_isr(int irq, void *data) ...@@ -133,17 +133,9 @@ irqreturn_t xillybus_isr(int irq, void *data)
unsigned int msg_channel, msg_bufno, msg_data, msg_dir; unsigned int msg_channel, msg_bufno, msg_data, msg_dir;
struct xilly_channel *channel; struct xilly_channel *channel;
/*
* The endpoint structure is altered during periods when it's
* guaranteed no interrupt will occur, but in theory, the cache
* lines may not be updated. So a memory barrier is issued.
*/
smp_rmb();
buf = ep->msgbuf_addr; buf = ep->msgbuf_addr;
buf_size = ep->msg_buf_size/sizeof(u32); buf_size = ep->msg_buf_size/sizeof(u32);
ep->ephw->hw_sync_sgl_for_cpu(ep, ep->ephw->hw_sync_sgl_for_cpu(ep,
ep->msgbuf_dma_addr, ep->msgbuf_dma_addr,
ep->msg_buf_size, ep->msg_buf_size,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment