Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755950AbbLAKPG (ORCPT ); Tue, 1 Dec 2015 05:15:06 -0500 Received: from mout.kundenserver.de ([212.227.126.187]:56774 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752314AbbLAKPC (ORCPT ); Tue, 1 Dec 2015 05:15:02 -0500 From: Arnd Bergmann To: Peter Ujfalusi Cc: vinod.koul@intel.com, andy.shevchenko@gmail.com, linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org, nsekhar@ti.com, linux-spi@vger.kernel.org Subject: Re: [RFC v02 04/15] dmaengine: edma: Add support for DMA filter mapping to slave devices Date: Tue, 01 Dec 2015 11:14:29 +0100 Message-ID: <4013235.sXCFUFy4j4@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <565D6F5D.3060603@ti.com> References: <1448891145-10766-1-git-send-email-peter.ujfalusi@ti.com> <7490116.jHcmUxB3Rf@wuerfel> <565D6F5D.3060603@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:lVm7+jzYnno8FnQ6/FTeMaJmgjJd17/EtPrxFnjo5Wk8AndA/ut QK7CP90ZIxjqjHGaqKH7NUEX8xqUvIzqWwC4nQ9qvdbxjyPFvJbcWXKe/30iEPdtQRwm5lr +HGb4uWxEsDudqzq9O+Wo2Ace8fgRgpIg0bfpFFNoEGJ3Hoq97ABULXxyTe+uydj5xZ+Oeb G8uDbY0pMWNuRM6gC31Xg== X-UI-Out-Filterresults: notjunk:1;V01:K0:jeGObN3cq3U=:Uv4lms5Qk8BqVgHMi0IO/b UOmWKGPAjqtlXN5cN5lmzs3vZjl/nvovr0HMlatsrQp5B5dS3D6L/29nl2P1HvPP2k5Y4+tA+ 493lWpBiBflVlEdUhZQfvRsnF86MkoKimSzPuI0jxDIUC88B7czZtWc0ZK+epQNs1ba4Pt8Ot ej8IHmPDssY/OMMIMrQYlrOFgzmkO5cDAvBqsbTJkeb+nVd3QWPFxE2PI8sGl3o0cG7BpQ0ih kvlhsLwRyb6epoivGR7BKFCXMW2JW8Af4rYBpjmyyTcGoEbaHLum3T5VEucHS/fK1mGHOpUUw wrLRwnpBsth92LXvjfnr6zGvlTXuazkbX9ZCjUA2h4c/rMSZtKOzTm7aSAWTSfh4SdKyp5Eqh YKt99sAvvMBdOuvojdqZOZVi/bTeu2r85VdxBcBc/IwlHsnoXjBnTyjZ+C77EzDBcWC9XWuCi CWDCR/Jh3cindPFmoJQHGunFfxji88vpZmoVAxKJtfkY0OxpyUrbRMjCHs5kRG6ACwQvy2MeX 1r+c4ldzokJVgTBF2HfF8O8ljyPCLxMTVVwfxsX4MmDARniEenmot6e52r7YLUXJSn9AzYBm9 HPQEs0VCwAjRofVMeF7MiJjvKIXY0vyIa2cac46RvELtfdj2b7NSRJ6z9GlSoR8ZYwhObe7Hq 3cbwmJdCByeUhFVN/7eeSvjImGHCLL6it8uaWEuWTrv0/iAUjHjqgvJLnBf2IR8Xe8zafjA4/ OB9pMMIZrW0FoN8H Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2104 Lines: 61 On Tuesday 01 December 2015 11:58:53 Peter Ujfalusi wrote: > On 11/30/2015 04:11 PM, Arnd Bergmann wrote: > > On Monday 30 November 2015 15:45:34 Peter Ujfalusi wrote: > >> @@ -2428,6 +2436,22 @@ bool edma_filter_fn(struct dma_chan *chan, void *param) > >> } > >> EXPORT_SYMBOL(edma_filter_fn); > >> > >> +static bool edma_filter_for_map(struct dma_chan *chan, void *param) > >> +{ > >> + bool match = false; > >> + > >> + if (chan->device->dev->driver == &edma_driver.driver) { > >> + struct edma_chan *echan = to_edma_chan(chan); > >> + unsigned ch_req = (unsigned)param; > >> + if (ch_req == echan->ch_num) { > >> + /* The channel is going to be used as HW synchronized */ > >> + echan->hw_triggered = true; > >> + match = true; > >> + } > >> + } > >> + return match; > >> +} > >> + > >> static int edma_init(void) > >> > > > > I don't see the difference between edma_filter_fn and edma_filter_for_map. > > Why do you need both? > > edma_filter_fn: > unsigned ch_req = *(unsigned *)param; > > edma_filter_for_map: > unsigned ch_req = (unsigned)param; I see. > If I want to reuse the edma_filter_fn, I would need an unsigned array for the > eDMA event numbers in the board files to be able to provide the pointer to > each of them. How about this: #define EDMA_CTLR_CHANP(ctlr, chan) ((const int[]){ [0] = ((ctlr) << 16) | (chan)}) static struct dma_filter_map da830_edma_map[] = { { "davinci-mcasp.0", "rx", EDMA_CTLR_CHANP(0, 0)}, { "davinci-mcasp.0", "tx", EDMA_CTLR_CHANP(0, 1)}, { "davinci-mcasp.1", "rx", EDMA_CTLR_CHANP(0, 2)}, ... }; That way, you create an anonymous constant integer expression and the data points to that. Arnd -- 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/