From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 4337EDDE19 for ; Tue, 25 Nov 2008 08:28:26 +1100 (EST) Message-ID: <492B1C74.9070700@freescale.com> Date: Mon, 24 Nov 2008 15:28:20 -0600 From: Scott Wood MIME-Version: 1.0 To: Bruce_Leonard@selinc.com Subject: Re: Async DMA question regarding dma_async_memcpy_buf_to_buf References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Bruce_Leonard@selinc.com wrote: > Maybe (with you clarification) this is starting to make sense. It doesn't > matter if the "src" is host memory or PCI space. What the "src" and it's > DMA_TO_DEVICE mapping is saying to the kernel is "this data needs to be > moved into the DMA engine", while the "dest" and it's DMA_FROM_DEIVCE > mapping is telling the kernel "this data needs to be moved from the DMA > engine". Right. -Scott