From: Andrew Morton <akpm@linux-foundation.org>
To: Hein Tibosch <hein_tibosch@yahoo.es>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
viresh kumar <viresh.kumar@linaro.org>,
spear-devel <spear-devel@list.st.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
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>
Subject: Re: [PATCH REGRESSION FIX] dw_dmac: make driver's endianness configurable
Date: Tue, 23 Oct 2012 16:12:18 -0700 [thread overview]
Message-ID: <20121023161218.45a7ae4e.akpm@linux-foundation.org> (raw)
In-Reply-To: <507A6FA5.1000800@yahoo.es>
On Sun, 14 Oct 2012 15:54:13 +0800
Hein Tibosch <hein_tibosch@yahoo.es> wrote:
> The dw_dmac was originally developed for avr32 to be used with the Synopsys
> DesignWare AHB DMA controller. Starting from 2.6.38, access to the device's i/o
> memory was done with the little-endian readl/writel functions(1)
>
> This broke the driver for the avr32 platform, because it needs big (native)
> endian accessors.
> This patch makes the endianness configurable using 'DW_DMAC_BIG_ENDIAN_IO',
> which will default be true for AVR32
Do we think this bug should be fixed in earlier kernel versions?
If so, the patch might need to be tweaked for 3.6 and earlier, which
don't have the dma_read_byaddr() definition.
next prev parent reply other threads:[~2012-10-23 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 7:54 [PATCH REGRESSION FIX] dw_dmac: make driver's endianness configurable Hein Tibosch
2012-10-14 19:09 ` Arnd Bergmann
2012-10-14 20:08 ` Andy Shevchenko
2012-10-15 0:39 ` Hein Tibosch
2012-10-15 7:31 ` Andy Shevchenko
2012-10-15 3:19 ` viresh kumar
2012-10-23 23:12 ` Andrew Morton [this message]
2012-10-24 0:53 ` Hein Tibosch
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=20121023161218.45a7ae4e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--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