lkml.org 
[lkml]   [2008]   [Jan]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [RFC v2 0/5] dmaengine: Slave DMA interface and example users
    Date
    On Tuesday 29 January 2008, Haavard Skinnemoen wrote:
    >
    > Btw, there's one issue I forgot to mention: I believe the DMA Engine
    > framework is currently misusing the DMA mapping API, and this patchset
    > makes things worse.
    >
    > Currently, the async_tx bits of the API do the required calls to
    > dma_map_single() and/or dma_map_page(), but they rely on the driver to
    > do the unmapping. This is problematic ...
    >
    > How do we solve this?

    How about: for peripheral DMA, don't let the engine see anything
    except dma_addr_t values.

    The engine needs to be able to dma_alloc_coherent() memory too,
    which is pre-mapped.

    - Dave


    \
     
     \ /
      Last update: 2008-01-30 08:35    [W:3.036 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site