linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: olof@lixom.net, grant.likely@secretlab.ca, lrg@ti.com,
	broonie@opensource.wolfsonmicro.com, vinod.koul@linux.intel.com,
	linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org,
	spi-devel-general@lists.sourceforge.net,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/5] ARM: tegra: move all APB DMA client to dmaengine based driver
Date: Thu, 13 Sep 2012 17:35:20 -0600	[thread overview]
Message-ID: <50526DB8.3090808@wwwdotorg.org> (raw)
In-Reply-To: <1345126397-28864-1-git-send-email-ldewangan@nvidia.com>

On 08/16/2012 08:13 AM, Laxman Dewangan wrote:
> This patch series enable the dmaengine based Tegra APB DMA driver
> and remove the support code for the legacy dma driver from different
> APB DMA clients.
> Patch 1 enable the dmaengine based dma drie and disable the legacy dma driver
>         in config file.
> Patch 2 remove the legacy dma driver.
> Patch 3,4, 5 remove the support code from different APB DMA clients to support
>         legacy dma driver.
> 
> Please note that this series will depends on patch
> dma: tegra: enable/disable dma clock
> which is not in 3.6-rc1 but will be available in next RC (rc2) of 3.6 as
> part of fixes.

I have applied this series to Tegra's for-3.7/dmaengine branch. Right
now, that branch is based directly on Mark Brown's ASoC for-3.6 branch
in order to pick up the fix it depends on. However, I'll rebase on the
3.6 pull request tag he sends for that branch as soon as it's available.

      parent reply	other threads:[~2012-09-13 23:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 14:13 [PATCH 0/5] ARM: tegra: move all APB DMA client to dmaengine based driver Laxman Dewangan
2012-08-16 14:13 ` [PATCH 1/5] ARM: tegra: config: enable dmaengine based APB DMA driver Laxman Dewangan
2012-08-16 17:53   ` Stephen Warren
2012-08-17  6:38     ` Laxman Dewangan
2012-08-17 15:17       ` Stephen Warren
2012-08-17 17:34         ` Stephen Warren
2012-08-17 18:00           ` Laxman Dewangan
2012-08-16 14:13 ` [PATCH 2/5] ARM: tegra: dma: remove legacy " Laxman Dewangan
2012-08-16 14:13 ` [PATCH 3/5] ARM: tegra: apbio: remove support of legacy DMA driver based access Laxman Dewangan
2012-08-16 14:13 ` [PATCH 4/5] spi: tegra: " Laxman Dewangan
2012-09-06 23:50   ` Stephen Warren
2012-09-14 15:57     ` Mark Brown
2012-09-14 15:57     ` Stephen Warren
2012-09-14 16:02       ` Mark Brown
2012-09-13 23:36   ` Stephen Warren
2012-08-16 14:13 ` [PATCH 5/5] ASoC: " Laxman Dewangan
2012-09-06 23:50   ` Stephen Warren
2012-09-14 15:57     ` Stephen Warren
2012-09-14 16:08       ` Mark Brown
2012-09-13 23:36   ` Stephen Warren
2012-09-14 15:53     ` Mark Brown
2012-09-14 16:00       ` Stephen Warren
2012-09-14 16:33         ` Mark Brown
2012-09-13 23:35 ` Stephen Warren [this message]

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=50526DB8.3090808@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=grant.likely@secretlab.ca \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=lrg@ti.com \
    --cc=olof@lixom.net \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=vinod.koul@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).