Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756386AbZA3XNl (ORCPT ); Fri, 30 Jan 2009 18:13:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756425AbZA3XNP (ORCPT ); Fri, 30 Jan 2009 18:13:15 -0500 Received: from wa-out-1112.google.com ([209.85.146.179]:8770 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755684AbZA3XNN (ORCPT ); Fri, 30 Jan 2009 18:13:13 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=MEx6X6/568ebYRTBtrB8o5oxOQyHPmCKh+t/3lo+5+5ZekDjCTGjdsHiRcvvphimCN RkUAFoMIHD520kvqmULcUeayl+jXY3z1exJ4TFISJxQlCEiMjREA9CC5dxlK/EFumQdz HeCxrTL90zmMs8v7CvTY0EXSuNz3YWeo+6ths= MIME-Version: 1.0 In-Reply-To: <20090131.020300.82352947.anemo@mba.ocn.ne.jp> References: <20081114213453.32354.53002.stgit@dwillia2-linux.ch.intel.com> <20090131.020300.82352947.anemo@mba.ocn.ne.jp> Date: Fri, 30 Jan 2009 16:13:12 -0700 X-Google-Sender-Auth: a585d30bc38f890a Message-ID: Subject: Re: [PATCH 07/13] dmaengine: introduce dma_request_channel and private channels From: Dan Williams To: Atsushi Nemoto Cc: g.liakhovetski@gmx.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, maciej.sosnowski@intel.com, hskinnemoen@atmel.com, nicolas.ferre@atmel.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 949 Lines: 25 On Fri, Jan 30, 2009 at 10:03 AM, Atsushi Nemoto wrote: > I'm writing a new dma driver. My DMAC has multiple channels and only > one channel is capable for generic memcpy and other channels have > fixed role. > > Does new framework allow dma driver make only one channel public? Yes, if the driver registers a dma_device for each channel. > Or should I register two dma_device for DMA_MEMCPY and DMA_SLAVE? > Could you give me some advice? Register multiple dma_devices, the public one with a DMA_MEMCPY, and the fixed role devices with DMA_PRIVATE, DMA_MEMCPY, and DMA_SLAVE capabilities. DMA_PRIVATE ensures that a channel is never considered for public consumption. -- Dan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/