From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH RFC 00/26] Migrate more OMAP DMA code to DMA engine Date: Mon, 13 Jan 2014 13:21:18 -0800 Message-ID: <20140113212117.GB7993@atomide.com> References: <20140102150836.GA3826@n2100.arm.linux.org.uk> <20140108012110.GL5074@atomide.com> <20140109152437.GB27282@n2100.arm.linux.org.uk> <20140113141811.GD27282@n2100.arm.linux.org.uk> <20140113173744.GA7746@atomide.com> <20140113185503.GE27282@n2100.arm.linux.org.uk> <20140113192630.GB7746@atomide.com> <20140113203404.GF27282@n2100.arm.linux.org.uk> <20140113210242.GA7993@atomide.com> <20140113211130.GG27282@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:47382 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751584AbaAMVVY (ORCPT ); Mon, 13 Jan 2014 16:21:24 -0500 Content-Disposition: inline In-Reply-To: <20140113211130.GG27282@n2100.arm.linux.org.uk> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Russell King - ARM Linux Cc: dmaengine@vger.kernel.org, Vinod Koul , Dan Williams , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org * Russell King - ARM Linux [140113 13:13]: > On Mon, Jan 13, 2014 at 01:02:42PM -0800, Tony Lindgren wrote: > > * Russell King - ARM Linux [140113 12:36]: > > > On Mon, Jan 13, 2014 at 11:26:31AM -0800, Tony Lindgren wrote: > > > > * Russell King - ARM Linux [140113 10:= 57]: > > > > > On Mon, Jan 13, 2014 at 09:37:45AM -0800, Tony Lindgren wrote= : > > > > > > * Russell King - ARM Linux [140113= 08:48]: > > > > > > > Any news on this? > > > > > >=20 > > > > > > Sorry for the delay, now getting this: > > > > > >=20 > > > > > > arch/arm/mach-omap1/dma.c: In function =E2=80=98omap1_syste= m_dma_init=E2=80=99: > > > > > > arch/arm/mach-omap1/dma.c:368: error: =E2=80=98struct omap_= dma_dev_attr=E2=80=99 has no member named =E2=80=98chan=E2=80=99 > > > > >=20 > > > > > Gah. Next incremental patch: > > > >=20 > > > > Thanks, now getting this on omap1: > > > >=20 > > > > # dmesg | grep -i dma > > > > DMA: preallocated 256 KiB pool for atomic coherent allocations > > > > OMAP DMA hardware version 1 > > > > DMA capabilities: 0000000c:00000000:01ff:003f:007f > > > > omap-dma-engine omap-dma-engine: invalid resource > > > > omap-dma-engine: probe of omap-dma-engine failed with error -22 > > > > mmci-omap mmci-omap.1: unable to obtain TX DMA engine channel 5= 4 > > > > mmci-omap mmci-omap.1: unable to obtain RX DMA engine channel 5= 5 > > >=20 > > > Sigh... let's give it the iomem resource then: > >=20 > > OK, looks like adding that makes MMC card detection to fail with: > >=20 > > DMA timeout with device 55 >=20 > You should also see a message: >=20 > oma-dma-engine omap-dma-engine: failed to get L1 IRQ: .. >=20 > which indicates that it's falling back to the old driver for IRQ > servicing. Can you confirm that please? Yes that's correct, here are all the DMA related lines: DMA: preallocated 256 KiB pool for atomic coherent allocations OMAP DMA hardware version 1 DMA capabilities: 0000000c:00000000:01ff:003f:007f omap-dma-engine omap-dma-engine: failed to get L1 IRQ: -6 omap-dma-engine omap-dma-engine: OMAP DMA engine driver omap-dma-engine omap-dma-engine: allocating channel 0 for 54 omap-dma-engine omap-dma-engine: allocating channel 1 for 55 DMA timeout with device 55 Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Mon, 13 Jan 2014 13:21:18 -0800 Subject: [PATCH RFC 00/26] Migrate more OMAP DMA code to DMA engine In-Reply-To: <20140113211130.GG27282@n2100.arm.linux.org.uk> References: <20140102150836.GA3826@n2100.arm.linux.org.uk> <20140108012110.GL5074@atomide.com> <20140109152437.GB27282@n2100.arm.linux.org.uk> <20140113141811.GD27282@n2100.arm.linux.org.uk> <20140113173744.GA7746@atomide.com> <20140113185503.GE27282@n2100.arm.linux.org.uk> <20140113192630.GB7746@atomide.com> <20140113203404.GF27282@n2100.arm.linux.org.uk> <20140113210242.GA7993@atomide.com> <20140113211130.GG27282@n2100.arm.linux.org.uk> Message-ID: <20140113212117.GB7993@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Russell King - ARM Linux [140113 13:13]: > On Mon, Jan 13, 2014 at 01:02:42PM -0800, Tony Lindgren wrote: > > * Russell King - ARM Linux [140113 12:36]: > > > On Mon, Jan 13, 2014 at 11:26:31AM -0800, Tony Lindgren wrote: > > > > * Russell King - ARM Linux [140113 10:57]: > > > > > On Mon, Jan 13, 2014 at 09:37:45AM -0800, Tony Lindgren wrote: > > > > > > * Russell King - ARM Linux [140113 08:48]: > > > > > > > Any news on this? > > > > > > > > > > > > Sorry for the delay, now getting this: > > > > > > > > > > > > arch/arm/mach-omap1/dma.c: In function ?omap1_system_dma_init?: > > > > > > arch/arm/mach-omap1/dma.c:368: error: ?struct omap_dma_dev_attr? has no member named ?chan? > > > > > > > > > > Gah. Next incremental patch: > > > > > > > > Thanks, now getting this on omap1: > > > > > > > > # dmesg | grep -i dma > > > > DMA: preallocated 256 KiB pool for atomic coherent allocations > > > > OMAP DMA hardware version 1 > > > > DMA capabilities: 0000000c:00000000:01ff:003f:007f > > > > omap-dma-engine omap-dma-engine: invalid resource > > > > omap-dma-engine: probe of omap-dma-engine failed with error -22 > > > > mmci-omap mmci-omap.1: unable to obtain TX DMA engine channel 54 > > > > mmci-omap mmci-omap.1: unable to obtain RX DMA engine channel 55 > > > > > > Sigh... let's give it the iomem resource then: > > > > OK, looks like adding that makes MMC card detection to fail with: > > > > DMA timeout with device 55 > > You should also see a message: > > oma-dma-engine omap-dma-engine: failed to get L1 IRQ: .. > > which indicates that it's falling back to the old driver for IRQ > servicing. Can you confirm that please? Yes that's correct, here are all the DMA related lines: DMA: preallocated 256 KiB pool for atomic coherent allocations OMAP DMA hardware version 1 DMA capabilities: 0000000c:00000000:01ff:003f:007f omap-dma-engine omap-dma-engine: failed to get L1 IRQ: -6 omap-dma-engine omap-dma-engine: OMAP DMA engine driver omap-dma-engine omap-dma-engine: allocating channel 0 for 54 omap-dma-engine omap-dma-engine: allocating channel 1 for 55 DMA timeout with device 55 Regards, Tony