From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>,
'Olof Johansson' <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Grant Likely' <grant.likely@secretlab.ca>,
w.sang@pengutronix.de, 'Boojin Kim' <boojin.kim@samsung.com>,
'Kyoungil Kim' <ki0351.kim@samsung.com>,
'Vinod Koul' <vinod.koul@intel.com>,
'Dan Williams' <dan.j.williams@intel.com>,
'Ben Dooks' <ben@simtec.co.uk>
Subject: Re: [GIT PULL] Samsung devel-dma ops for v3.6
Date: Wed, 11 Jul 2012 08:18:03 +0000 [thread overview]
Message-ID: <201207110818.04091.arnd@arndb.de> (raw)
In-Reply-To: <0e1301cd5f34$008fe1e0$01afa5a0$%kim@samsung.com>
On Wednesday 11 July 2012, Kukjin Kim wrote:
> Yeah, let me explain the status for Samsung SoCs' DMA. There are 3 different
> DMA IPs, samsung specific s3c24xx dma, pl080 and pl330. As you know, pl330
> already moved in drivers/dma for using common DMA engine and Alim is
> re-working on pl080
> (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg10954.html
> ) and let me check its progress. But s3c24xx dma is not ready yet. When
> pl330 was moving, my colleague, Boojin Kim posted to use common DMA APIs for
> Samsung drivers which are using DMA such as spi and ASoC. But it was
> including too many ifdef for checking which DMA is used and it can occur
> breakage for multiplatform
> (http://www.spinics.net/lists/arm-kernel/msg131137.html). So we implemented
> to use some dma_ops after discussing with Grant Likely
> (http://lists.infradead.org/pipermail/linux-arm-kernel/2011-July/058171.html
> ).
>
> Anyway, we will try to use common DMA APIs for all Samsung SoCs. But need
> more time ;)
Ok, sounds good. Thanks for the background information!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel-dma ops for v3.6
Date: Wed, 11 Jul 2012 08:18:03 +0000 [thread overview]
Message-ID: <201207110818.04091.arnd@arndb.de> (raw)
In-Reply-To: <0e1301cd5f34$008fe1e0$01afa5a0$%kim@samsung.com>
On Wednesday 11 July 2012, Kukjin Kim wrote:
> Yeah, let me explain the status for Samsung SoCs' DMA. There are 3 different
> DMA IPs, samsung specific s3c24xx dma, pl080 and pl330. As you know, pl330
> already moved in drivers/dma for using common DMA engine and Alim is
> re-working on pl080
> (http://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg10954.html
> ) and let me check its progress. But s3c24xx dma is not ready yet. When
> pl330 was moving, my colleague, Boojin Kim posted to use common DMA APIs for
> Samsung drivers which are using DMA such as spi and ASoC. But it was
> including too many ifdef for checking which DMA is used and it can occur
> breakage for multiplatform
> (http://www.spinics.net/lists/arm-kernel/msg131137.html). So we implemented
> to use some dma_ops after discussing with Grant Likely
> (http://lists.infradead.org/pipermail/linux-arm-kernel/2011-July/058171.html
> ).
>
> Anyway, we will try to use common DMA APIs for all Samsung SoCs. But need
> more time ;)
Ok, sounds good. Thanks for the background information!
Arnd
next prev parent reply other threads:[~2012-07-11 8:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 2:13 [GIT PULL] Samsung devel-dma ops for v3.6 Kukjin Kim
2012-07-10 2:13 ` Kukjin Kim
2012-07-10 12:42 ` Arnd Bergmann
2012-07-10 12:42 ` Arnd Bergmann
2012-07-11 7:08 ` Kukjin Kim
2012-07-11 7:08 ` Kukjin Kim
2012-07-11 8:18 ` Arnd Bergmann [this message]
2012-07-11 8:18 ` Arnd Bergmann
2012-07-23 14:36 ` Linus Walleij
2012-07-23 14:36 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201207110818.04091.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ben@simtec.co.uk \
--cc=boojin.kim@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dan.j.williams@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=ki0351.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=vinod.koul@intel.com \
--cc=w.sang@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.