From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/03] dmaengine: shdma: sh73a0 and SH_DMAC_MAX_CHANNELS
Date: Tue, 24 May 2011 15:43:49 +0000 [thread overview]
Message-ID: <20110524154349.GB14329@linux-sh.org> (raw)
In-Reply-To: <20110524103104.10334.42987.sendpatchset@t400s>
On Tue, May 24, 2011 at 07:31:04PM +0900, Magnus Damm wrote:
> dmaengine: shdma: sh73a0 and SH_DMAC_MAX_CHANNELS
>
> [PATCH 01/03] dmaengine: shdma: Make second memory window optional
> [PATCH 02/03] dmaengine: shdma: Fix SH_DMAC_MAX_CHANNELS handling
> [PATCH 03/03] dmaengine: shdma: Update SH_DMAC_MAX_CHANNELS to 20
>
> These patches update the shdma dmaengine driver to support DMA
> controllers with more than 6 slave-id capable channels mapped
> into a single I/O-memory window. While at it fix the handling
> of SH_DMAC_MAX_CHANNELS that without [PATCH 02/03] may overflow
> some arrays at probe() time depending on platform data.
>
> Needed to support the 20-channel SY-DMAC block included in sh73a0.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> Since these patches are only touching the shdma driver perhaps
> merging through the sh-2.6 tree is the easiest?
>
Easiest perhaps, but as the merge window is closing on Sunday and I've
already sent the sh bits off, none of this is likely to make it for -rc1.
I'm also not very thrilled about the amount of churn that the rmobile
bits add on top of this with regards to -rc2 timing, and with -rc1 timing
there's basically zero time for -next coverage should I slam all of it in
to the rmobile tree -- none of these options are terribly appealing. This
all should have been posted weeks ago.
next prev parent reply other threads:[~2011-05-24 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 10:31 [PATCH 00/03] dmaengine: shdma: sh73a0 and SH_DMAC_MAX_CHANNELS Magnus Damm
2011-05-24 15:43 ` Paul Mundt [this message]
2011-05-24 16:26 ` Magnus Damm
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=20110524154349.GB14329@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