[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130812233641.GL6427@sirena.org.uk>
Date: Tue, 13 Aug 2013 00:36:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Tomasz Figa <tomasz.figa@...il.com>
Cc: linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
Dan Williams <djbw@...com>, Jaroslav Kysela <perex@...ex.cz>,
Kukjin Kim <kgene.kim@...sung.com>,
Liam Girdwood <lgirdwood@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
Mike Turquette <mturquette@...aro.org>,
Padmavathi Venna <padma.v@...sung.com>,
Russell King <linux@....linux.org.uk>,
Sangbeom Kim <sbkim73@...sung.com>,
Takashi Iwai <tiwai@...e.de>, Vinod Koul <vinod.koul@...el.com>
Subject: Re: [PATCH 10/18] spi: s3c64xx: Do not require legacy DMA API in
case of S3C64XX
On Sun, Aug 11, 2013 at 07:59:22PM +0200, Tomasz Figa wrote:
> With support for amba-pl08x driver, on S3C64xx the generic DMA engine
> API can be used instead of the private s3c-dma interface.
I'm still getting issues for SPI with this:
[ 50.952845] s3c64xx-spi s3c6410-spi.0: Failed to get RX DMA channel
[ 50.953520] spi_master spi0: failed to prepare transfer hardware
when I test (with -next with this series applied on top), this is from
the first transfer that tries to DMA - there's actually no RX data. No
errors are reported by the DMA controller itself. I'm also getting
crashes setting up the audio DMA while derferencecing the channel.
This is without DT - are there any hookups missing because of that?
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists