tree 582181edf96f6389672c90b94654dd6acbaa9aaf
parent d4da0e97baea8768b3d66ccef3967bebd50dfc3b
author Christoph Hellwig <hch@lst.de> 1532712366 +0200
committer Paul Burton <paul.burton@mips.com> 1532729999 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iIsEABYIADMWIQRgLjeFAZEXQzy86/s+p5+stXUA3QUCW1uavhUccGF1bC5idXJ0
 b25AbWlwcy5jb20ACgkQPqefrLV1AN2SXAEAmQAPyrqCgv8zSsBh1yKPc3nN5C5H
 jq5wTSAHLKQJ8WMA/2eIlb6+dVbX6f+MHNziCJ0IDG3EKld6tOxQVCO7qN8F
 =lKqh
 -----END PGP SIGNATURE-----

MIPS: remove mips_swiotlb_ops

mips_swiotlb_ops differs from the generic swiotlb_dma_ops only in that
it contains a mb() barrier after each operations that maps or syncs
dma memory to the device.

The dma operations are defined to not be memory barriers, but instead
the write* operations to kick the DMA off are supposed to contain them.

For mips this handled by war_io_reorder_wmb(), which evaluates to the
stronger wmb() instead of the pure compiler barrier barrier() for
just those platforms that use swiotlb, so I think we are covered
properly.

[paul.burton@mips.com:
  - Include linux/swiotlb.h to fix build failures for configs with
    CONFIG_SWIOTLB=y.]

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Paul Burton <paul.burton@mips.com>
Patchwork: https://patchwork.linux-mips.org/patch/20038/
Cc: David Daney <ddaney@caviumnetworks.com>
Cc: Huacai Chen <chenhc@lemote.com>
Cc: linux-mips@linux-mips.org
Cc: iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org