Linux uses the member to decide e.g. inside vring_map_single, whether
DMA API should be used. I think we may need it in barebox in future too,
but it can always be added later.
Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
---
drivers/virtio/virtio_ring.c | 1 -
include/linux/virtio_ring.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index 1e5431dd3ee4..b0b402834aca 100644
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_ring.c
@@ -422,7 +422,6 @@ struct virtqueue *vring_create_virtqueue(unsigned int index, unsigned int num,
vq->queue_dma_addr = dma_addr;
vq->queue_size_in_bytes = queue_size_in_bytes;
- vq->use_dma_api = vring_use_dma_api(vdev);
return vq;
}
diff --git a/include/linux/virtio_ring.h b/include/linux/virtio_ring.h
index 7bf667611938..bdef47b0fa6c 100644
--- a/include/linux/virtio_ring.h
+++ b/include/linux/virtio_ring.h
@@ -103,7 +103,6 @@ struct virtqueue {
unsigned int num_free;
struct vring vring;
bool event;
- bool use_dma_api;
unsigned int free_head;
unsigned int num_added;
u16 last_used_idx;
--
2.39.5
