Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756633AbbLARUE (ORCPT ); Tue, 1 Dec 2015 12:20:04 -0500 Received: from mga09.intel.com ([134.134.136.24]:60556 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756073AbbLARUB (ORCPT ); Tue, 1 Dec 2015 12:20:01 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,369,1444719600"; d="scan'208";a="831982509" Date: Tue, 1 Dec 2015 22:52:12 +0530 From: Vinod Koul To: Peter Ujfalusi Cc: arnd@arndb.de, 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 Message-ID: <20151201172212.GC1696@localhost> References: <1448891145-10766-1-git-send-email-peter.ujfalusi@ti.com> <1448891145-10766-5-git-send-email-peter.ujfalusi@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1448891145-10766-5-git-send-email-peter.ujfalusi@ti.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2926 Lines: 96 On Mon, Nov 30, 2015 at 03:45:34PM +0200, Peter Ujfalusi wrote: > Add support for providing device to filter_fn mapping so client drivers > can switch to use the dma_request_chan() API. Any reason why we dont want to go with DT based only for edma here? > > Signed-off-by: Peter Ujfalusi > --- > drivers/dma/edma.c | 24 ++++++++++++++++++++++++ > include/linux/platform_data/edma.h | 5 +++++ > 2 files changed, 29 insertions(+) > > diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c > index 0675e268d577..386f8c9bd606 100644 > --- a/drivers/dma/edma.c > +++ b/drivers/dma/edma.c > @@ -2098,6 +2098,8 @@ static struct dma_chan *of_edma_xlate(struct of_phandle_args *dma_spec, > } > #endif > > +static bool edma_filter_for_map(struct dma_chan *chan, void *param); > + > static int edma_probe(struct platform_device *pdev) > { > struct edma_soc_info *info = pdev->dev.platform_data; > @@ -2297,6 +2299,12 @@ static int edma_probe(struct platform_device *pdev) > edma_set_chmap(&ecc->slave_chans[i], ecc->dummy_slot); > } > > + if (info->filter_map) { > + ecc->dma_slave.filter_map.map = info->filter_map; > + ecc->dma_slave.filter_map.mapcnt = info->filtercnt; > + ecc->dma_slave.filter_map.filter_fn = edma_filter_for_map; > + } > + > ret = dma_async_device_register(&ecc->dma_slave); > if (ret) { > dev_err(dev, "slave ddev registration failed (%d)\n", ret); > @@ -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) > { > int ret; > diff --git a/include/linux/platform_data/edma.h b/include/linux/platform_data/edma.h > index e2878baeb90e..117a36d63840 100644 > --- a/include/linux/platform_data/edma.h > +++ b/include/linux/platform_data/edma.h > @@ -59,6 +59,8 @@ struct edma_rsv_info { > const s16 (*rsv_slots)[2]; > }; > > +struct dma_filter_map; > + > /* platform_data for EDMA driver */ > struct edma_soc_info { > /* > @@ -76,6 +78,9 @@ struct edma_soc_info { > > s8 (*queue_priority_mapping)[2]; > const s16 (*xbar_chans)[2]; > + > + struct dma_filter_map *filter_map; > + int filtercnt; > }; > > #endif > -- > 2.6.3 > -- ~Vinod -- 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/