[lkml]   [2008]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 07/13] dmaengine: introduce dma_request_channel and private channels
    On Tue, Dec 2, 2008 at 8:52 AM, Guennadi Liakhovetski
    <> wrote:
    > Hi Dan,
    > I think, there is a problem with your dma_request_channel() /
    > private_candidate() implementation: your current version only tries one
    > channel from a dma device list, which matched capabilities. If this
    > channel is not accepted by the client, you do not try other channels from
    > this device and just go to the next one...

    Which dma driver are you using? The dmaengine code assumes that all
    channels on a device are equal. It sounds like there are differences
    between peer-channels on the device in this case. If the driver
    registers a device per channel that should give the flexibility you

    > Another problem I encountered with my framebuffer is the initialisation
    > order. You initialise dmaengine per subsys_initcall(), whereas the only
    > way to guarantee the order:
    > dmaengine
    > dma-device driver
    > framebuffer

    hmm... can the framebuffer be moved to late_initcall?


     \ /
      Last update: 2008-12-02 18:19    [W:0.021 / U:38.272 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site