Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756362AbbLBKwT (ORCPT ); Wed, 2 Dec 2015 05:52:19 -0500 Received: from devils.ext.ti.com ([198.47.26.153]:56332 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752466AbbLBKwQ (ORCPT ); Wed, 2 Dec 2015 05:52:16 -0500 Subject: Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel To: Arnd Bergmann References: <1448891145-10766-1-git-send-email-peter.ujfalusi@ti.com> <565DA47C.4000308@ti.com> <103520159.g0xhtFsXUi@wuerfel> CC: Andy Shevchenko , Vinod Koul , "linux-kernel@vger.kernel.org" , dmaengine , Linux OMAP Mailing List , linux-arm Mailing List , "linux-mmc@vger.kernel.org" , Sekhar Nori , linux-spi From: Peter Ujfalusi X-Enigmail-Draft-Status: N1110 Message-ID: <565ECD3F.3070500@ti.com> Date: Wed, 2 Dec 2015 12:51:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <103520159.g0xhtFsXUi@wuerfel> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2565 Lines: 48 On 12/01/2015 04:24 PM, Arnd Bergmann wrote: > On Tuesday 01 December 2015 15:45:32 Peter Ujfalusi wrote: >>>> static struct dma_filter_map da830_edma_map[] = { >>>> DMA_FILTER_ENTRY("davinci-mcasp.0", "rx", EDMA_CTLR_CHAN(0, 0)), >>>> DMA_FILTER_ENTRY("davinci-mcasp.0", "tx", EDMA_CTLR_CHAN(0, 1)), >>>> DMA_FILTER_ENTRY("davinci-mcasp.1", "rx", EDMA_CTLR_CHAN(0, 2)), >>>> DMA_FILTER_ENTRY("davinci-mcasp.1", "tx", EDMA_CTLR_CHAN(0, 3)), >>>> DMA_FILTER_ENTRY("davinci-mcasp.2", "rx", EDMA_CTLR_CHAN(0, 4)), >>>> DMA_FILTER_ENTRY("davinci-mcasp.2", "tx", EDMA_CTLR_CHAN(0, 5)), >>>> DMA_FILTER_ENTRY("spi_davinci.0", "rx", EDMA_CTLR_CHAN(0, 14)), >>>> DMA_FILTER_ENTRY("spi_davinci.0", "tx", EDMA_CTLR_CHAN(0, 15)), >>>> DMA_FILTER_ENTRY("da830-mmc.0", "rx", EDMA_CTLR_CHAN(0, 16)), >>>> DMA_FILTER_ENTRY("da830-mmc.0", "tx", EDMA_CTLR_CHAN(0, 17)), >>>> DMA_FILTER_ENTRY("spi_davinci.1", "rx", EDMA_CTLR_CHAN(0, 18)), >>>> DMA_FILTER_ENTRY("spi_davinci.1", "tx", EDMA_CTLR_CHAN(0, 19)), >>> >>> Does this ".2" and so prevent driver to use auto ID for platform devices? >> >> Yes, as all the infra around the traditional board files with platform_device >> creation does. Ideally we could have 'phandle' pointing from this table to the >> device in question (or other way around), but I'm not aware of anything we can >> use. > > I was thinking that we could use a pointer to the device structure, but > if you have that, you can also just read the name from it. Hrm to have pdev pointer instead of the devname string? In the core we could get the pdev from the caller's device with to_platform_device(dev) and simply compare the pointers... One of the issue I see (in mach-davinci and mach-omap1/2) is that the pdevs are scattered around in the c files so gathering the pointers to a place where we can see them to be able to use it in the dma_filter_map is not going to be light weight task. Furthermore we have the omap_hwmod for OMAP2+ which creates the actual pdevs and resources from the omap_hwmod data structures so getting out the DMA event numbers there is not going to be easy either... I'll hold back the RFC v3 to see if we should switch to pdev pointer or stay with the devname strings here. -- P?ter -- 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/