From mboxrd@z Thu Jan 1 00:00:00 1970 From: w.sang@pengutronix.de (Wolfram Sang) Date: Wed, 29 Jun 2011 14:29:42 +0200 Subject: [PATCH v7 1/3] MTD : add the common code for GPMI-NFC controller driver In-Reply-To: <4E0B0296.6060902@freescale.com> References: <1309335878-16678-1-git-send-email-b32955@freescale.com> <1309335878-16678-2-git-send-email-b32955@freescale.com> <20110629100658.GE1992@pengutronix.de> <20110629103337.GF1992@pengutronix.de> <4E0B0296.6060902@freescale.com> Message-ID: <20110629122942.GH1992@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > > Still, the problem exists: When a second channel GPMI channel is > > requested, dmaengine will return -EBUSY, because the DMAIRQ is already > > taken. > > > Yes, we should change the DMA code, it is a DMA bug. > I ever submitted a patch about the issue: > http://patchwork.ozlabs.org/patch/87145/ That approach was rejected because it would register the same handler n-times where one time would do. Your other approach puts too much mach-specific details into the driver IMO and probably won't scale very well. Maybe we should add something to the private dma_data (like flags indicating SHARED) and then do some refcounting? Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang | Industrial Linux Solutions | http://www.pengutronix.de/ | -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: