From: Ralf Baechle <ralf@linux-mips.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-mips@linux-mips.org, alsa-devel@alsa-project.org,
Vinod Koul <vinod.koul@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Maarten ter Huurne <maarten@treewalker.org>
Subject: Re: [PATCH 0/6] Convert JZ4740 to dmaengine
Date: Wed, 29 May 2013 11:31:03 +0200 [thread overview]
Message-ID: <20130529093103.GA6426@linux-mips.org> (raw)
In-Reply-To: <1369341387-19147-1-git-send-email-lars@metafoo.de>
On Thu, May 23, 2013 at 10:36:21PM +0200, Lars-Peter Clausen wrote:
> done in 3 steps:
> 1) Add a dmaengine driver which wraps the custom JZ4740 DMA API
> 2) Update all users of the JZ4740 DMA API to use dmaengine instead
> 3) Remove the custom API and move all direct hardware access to the
> dmaengine driver.
>
> The first two patches in the series also make sure that the clock of the DMA
> core is enabled.
>
> Since the patches in this series depend on each other I'd prefer if they could
> all go through the DMA tree.
No problem - though my experience is that code for MIPS systems, including
drivers receives most testing if it lives in the MIPS git tree, less in
linux-next and barely any in in other subsystem-specific trees.
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@linux-mips.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Maarten ter Huurne <maarten@treewalker.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/6] Convert JZ4740 to dmaengine
Date: Wed, 29 May 2013 11:31:03 +0200 [thread overview]
Message-ID: <20130529093103.GA6426@linux-mips.org> (raw)
In-Reply-To: <1369341387-19147-1-git-send-email-lars@metafoo.de>
On Thu, May 23, 2013 at 10:36:21PM +0200, Lars-Peter Clausen wrote:
> done in 3 steps:
> 1) Add a dmaengine driver which wraps the custom JZ4740 DMA API
> 2) Update all users of the JZ4740 DMA API to use dmaengine instead
> 3) Remove the custom API and move all direct hardware access to the
> dmaengine driver.
>
> The first two patches in the series also make sure that the clock of the DMA
> core is enabled.
>
> Since the patches in this series depend on each other I'd prefer if they could
> all go through the DMA tree.
No problem - though my experience is that code for MIPS systems, including
drivers receives most testing if it lives in the MIPS git tree, less in
linux-next and barely any in in other subsystem-specific trees.
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Ralf
next prev parent reply other threads:[~2013-05-29 9:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 20:36 [PATCH 0/6] Convert JZ4740 to dmaengine Lars-Peter Clausen
2013-05-23 20:36 ` Lars-Peter Clausen
2013-05-23 20:36 ` [PATCH 1/6] MIPS: jz4740: Correct clock gate bit for DMA controller Lars-Peter Clausen
2013-05-23 20:36 ` [PATCH 2/6] MIPS: jz4740: Acquire and enable DMA controller clock Lars-Peter Clausen
2013-05-23 20:36 ` [PATCH 3/6] dma: Add a jz4740 dmaengine driver Lars-Peter Clausen
2013-05-24 4:59 ` Vinod Koul
2013-05-24 5:58 ` Lars-Peter Clausen
2013-05-24 5:58 ` Lars-Peter Clausen
2013-05-24 5:54 ` Vinod Koul
2013-05-24 6:41 ` Lars-Peter Clausen
2013-05-24 7:54 ` Vinod Koul
2013-05-24 7:54 ` Vinod Koul
2013-05-24 8:39 ` [alsa-devel] " Lars-Peter Clausen
2013-05-23 20:36 ` [PATCH 4/6] MIPS: jz4740: Register jz4740 DMA device Lars-Peter Clausen
2013-05-23 20:36 ` Lars-Peter Clausen
2013-05-23 20:36 ` [PATCH 5/6] ASoC: jz4740: Use the generic dmaengine PCM driver Lars-Peter Clausen
2013-05-25 15:16 ` Mark Brown
2013-05-23 20:36 ` [PATCH 6/6] MIPS: jz4740: Remove custom DMA API Lars-Peter Clausen
2013-05-29 9:31 ` Ralf Baechle [this message]
2013-05-29 9:31 ` [PATCH 0/6] Convert JZ4740 to dmaengine Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2013-05-30 16:24 Lars-Peter Clausen
2013-05-30 16:24 ` Lars-Peter Clausen
2013-06-21 14:13 ` Vinod Koul
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=20130529093103.GA6426@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=maarten@treewalker.org \
--cc=vinod.koul@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 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.