[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Oct 2011 16:46:08 +0530
From: Jassi Brar <jaswinder.singh@...aro.org>
To: Vinod Koul <vinod.koul@...el.com>
Cc: "Williams, Dan J" <dan.j.williams@...el.com>,
Russell King <rmk@....linux.org.uk>,
Barry Song <21cnbao@...il.com>, linux-kernel@...r.kernel.org,
DL-SHA-WorkGroupLinux <workgroup.linux@....com>,
Dave Jiang <dave.jiang@...el.com>
Subject: Re: [PATCHv4] DMAEngine: Define interleaved transfer request api
On 10 October 2011 16:15, Vinod Koul <vinod.koul@...el.com> wrote:
>
> But I am fine if we find a common ground and merge the two where dmac
> can cleanly identify direction and mode it is operating.
>
The client would set the xfer_direction and dmac would interpret as
enum xfer_direction {
MEM_TO_MEM, -> Async/Memcpy mode
MEM_TO_DEV, -> Slave mode & From Memory to Device
DEV_TO_MEM, -> Slave mode & From Device to Memory
DEV_TO_DEV, -> Slave mode & From Device to Device
}
How could it get any cleaner?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists