From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5 v2] sh: dmaengine driver improvements
Date: Tue, 02 Mar 2010 03:08:09 +0000 [thread overview]
Message-ID: <20100302030809.GA20256@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1002111647350.4484@axis700.grange>
On Fri, Feb 12, 2010 at 12:54:58PM +0900, Paul Mundt wrote:
> On Thu, Feb 11, 2010 at 05:50:00PM +0100, Guennadi Liakhovetski wrote:
> > V2 of this patchset addresses comments to v1 - as is easy to guess;)
> > Specific chenges are described in respective patches. One more patch is
> > added, described in (4) below. Here again the description from v1:
> >
> > This patch series introduces several improvements to the shdma SH
> > dmaengine driver:
> >
> > 1. (v2) fix handling of DMA error interrupts
> >
> > 2. better use platform-dvice infrastructures, resources to describe DMAC
> > implementation details, ioremap address ranges, instead of poking at
> > physical addresses directly.
> >
> > 3. separate SH headers for the legacy arch/sh/drivers/dma and the
> > dmaengine driver
> >
> > 4. add runtime PM support to shdma dmaengine driver
> >
> > This series applies on top of my previous ASoC (SIU) and SH / dmaengine
> > patches.
> >
> This definitely looks much better than v1, and should give us a pretty
> good foundation for killing off the legacy DMA support incrementally.
>
> Given the dependencies on the SIU patches, I'll roll these in for the
> second round of updates during the merge window once the ASoC tree has
> merged. This leaves plenty of time for Dan or Iwamatsu-san to voice any
> objections in the interim.
I've applied these now that the ASoC tree has merged.
prev parent reply other threads:[~2010-03-02 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 16:50 [PATCH 0/5 v2] sh: dmaengine driver improvements Guennadi Liakhovetski
2010-02-12 3:54 ` Paul Mundt
2010-03-02 3:08 ` Paul Mundt [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=20100302030809.GA20256@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
/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).