From: Andrew Morton <akpm@linux-foundation.org>
To: Hein Tibosch <hein_tibosch@yahoo.es>
Cc: viresh kumar <viresh.kumar@linaro.org>,
spear-devel <spear-devel@list.st.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"ludovic.desroches" <ludovic.desroches@atmel.com>,
Havard Skinnemoen <havard@skinnemoen.net>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
egtvedt@samfundet.no, Arnd Bergmann <arnd.bergmann@linaro.org>
Subject: Re: [PATCH 2/2] dw_dmac: max_mem_width limits value for SRC/DST_TR_WID register
Date: Fri, 31 Aug 2012 16:49:43 -0700 [thread overview]
Message-ID: <20120831164943.f4b4531c.akpm@linux-foundation.org> (raw)
In-Reply-To: <503A89E0.40602@yahoo.es>
On Mon, 27 Aug 2012 04:41:04 +0800
Hein Tibosch <hein_tibosch@yahoo.es> wrote:
> The dw_dmac driver was earlier adapted to do 64-bit transfers
> on the memory side (https://lkml.org/lkml/2012/1/18/52)
> This works on ARM platforms but for AVR32 (AP700x) the maximum
> allowed transfer size is 32-bits.
> This patch allows the arch to set a new slave property
> max_mem_width to limit the size.
> Allowable values for dw_dma_slave::max_mem_width are:
>
This patch fails to apply to mainline and to linux-next and I can't
work out how to make it to apply to either. And "avr32-linux:
at32ap700x: set DMA slave properties for MCI dw_dmac" is said to depend
on this patch.
All confused, giving up.
prev parent reply other threads:[~2012-08-31 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 20:41 [PATCH 2/2] dw_dmac: max_mem_width limits value for SRC/DST_TR_WID register Hein Tibosch
[not found] ` <CAKohpontcFpMiju1LwO3fL43Oud0jAixYf8ZNN+6-hTj35ownA@mail.gmail.com>
2012-08-27 7:48 ` Hein Tibosch
2012-08-27 8:26 ` Viresh Kumar
2012-08-31 23:49 ` Andrew Morton [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=20120831164943.f4b4531c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd.bergmann@linaro.org \
--cc=egtvedt@samfundet.no \
--cc=havard@skinnemoen.net \
--cc=hein_tibosch@yahoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=spear-devel@list.st.com \
--cc=viresh.kumar@linaro.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