All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hein Tibosch <hein_tibosch@yahoo.es>
To: Andrew Morton <akpm@linux-foundation.org>,
	viresh kumar <viresh.kumar@linaro.org>,
	Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: 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>,
	spear-devel <spear-devel@list.st.com>
Subject: [PATCH v3 0/3] dw_dmac: repair driver for use with AVR32 (AP7000)
Date: Sat, 01 Sep 2012 10:58:03 +0800	[thread overview]
Message-ID: <504179BB.2090007@yahoo.es> (raw)

@Andrew: This is the third and hopefully final version of the dw_dmac patches.
Now the small Atmel patch is included because of its dependency on
the second dw_dmac patch. Sorry for the earlier confusion.


After some recent changes to dw_dmac, the driver got broken for the
AVR32 platform for several reasons:

The accessors to i/o memory had become little-endian.
The maximum transfer width on the memory side was increased from 32 to 64 bits.
This led to undefined behavior on the avr32 platform.

These patches will repair the driver so it can be used again on avr32. For
other users of dw_dmac (ARM platform), nothing will change and no code has
to be adapted.

The small patch for Atmel (at32ap700x.c) is included here because of its
dependency on the second dw_dmac patch.

Thanks to all for reviewing, both people from Atmel and Linaro

Hein Tibosch (3):
  dw_dmac: make driver endianness configurable
  dw_dmac: max_mem_width limits value for SRC/DST_TR_WID register
  avr32: at32ap700x: set DMA slave properties for MCI dw_dmac

 arch/avr32/mach-at32ap/at32ap700x.c |    5 +++++
 drivers/dma/Kconfig                 |   11 +++++++++++
 drivers/dma/dw_dmac.c               |   10 +++++++---
 drivers/dma/dw_dmac_regs.h          |   14 ++++++++++++++
 include/linux/dw_dmac.h             |    3 +++
 5 files changed, 40 insertions(+), 3 deletions(-)

-- 


                 reply	other threads:[~2012-09-01  3:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=504179BB.2090007@yahoo.es \
    --to=hein_tibosch@yahoo.es \
    --cc=akpm@linux-foundation.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=egtvedt@samfundet.no \
    --cc=havard@skinnemoen.net \
    --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 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.