Converting m68k WD33C93 drivers to DMA API
Status from this message: Applied to 5.20/scsi-staging, thanks!
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 3 repliesApplied
- v13 patches 15 repliesSuperseded
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | scsi - a3000.c: convert m68k WD33C93 drivers to DMA APIdrivers/ | +44 | 0 replies | |
| 2/3 | scsi - a2091.c: convert m68k WD33C93 drivers to DMA APIdrivers/ | +48 | 0 replies | |
| 3/3 | scsi - gvp11.c: convert m68k WD33C93 drivers to DMA APIdrivers/ | +77 | 0 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Arnd Bergmann |
|---|---|
| 1/3 | R-b |
| 2/3 | R-b |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/3] Converting m68k WD33C93 drivers to DMA API
This series was precipitated by Arnd removing CONFIG_VIRT_TO_BUS. The m68k WD33C93 still used virt_to_bus to convert virtual addresses to physical addresses suitable for the DMA engines (note m68k does not have an IOMMU and uses a direct mapping for DMA addresses).
Arnd suggested to use dma_map_single() to set up dma mappings instead of open-coding much the same in every driver dma_setup() function.
DMA setup on a3000 host adapters can be kept as-is (bounce buffers are used only where the input buffer isn't cache line aligned). Cache management is now taken care of by dma_map_single(). Note that I've restored bounce buffer allocation (dropped in v1) in order to make minimal changes to the core logic.
On gvp11 and a2091 host adapters, only the lowest 16 MB of physical memory can be directy addressed by DMA, and bounce buffers from that space must be used (possibly allocated from chip RAM using the custom allocator) if buffers are located in the higher memory regions. No cache management is required for chip RAM bounce buffers.
The m68k VME mvme147 driver has no DMA addressing or alignment restrictions and can be converted in the same way as the Amiga a3000 one, but will require conversion to a platform device driver first.
Only compile tested so far, and hardware testing might be hard to do.
Cheers,
Michael