linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: Hein Tibosch <hein_tibosch@yahoo.es>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	"ludovic.desroches" <ludovic.desroches@atmel.com>,
	Havard Skinnemoen <havard@skinnemoen.net>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH v2] avr32: at32ap700x: set DMA slave properties for MCI dw_dmac
Date: Thu, 30 Aug 2012 21:22:53 +0200	[thread overview]
Message-ID: <20120830192253.GA10588@samfundet.no> (raw)
In-Reply-To: <503F9DC1.9030601@yahoo.es>

Around Fri 31 Aug 2012 01:07:13 +0800 or thereabout, Hein Tibosch wrote:
> The MCI makes use of the dw_dmac driver when DMA is being used.
> Due to recent changes the driver was broken because:
> - the SMS field in the CTLL register received the wrong value 0
> - a patch in dw_dmac (http://lkml.org/lkml/2012/1/18/52)
> allowed for 64-bit transfers on the memory side, giving an illegal
> value of 3 in the SRC/DST_TR_WIDTH register.
> 
> This patch sets the SMS (Source Master Select) to 1 and limits
> the maximum transfer width to 32 bits.
> 
> Note: this can only be applied after my patch:
> [PATCH v2 2/2] dw_dmac: max_mem_width limits value for
> SRC/DST_TR_WID register
> 
> Signed-off-by: Hein Tibosch <hein_tibosch@yahoo.es>

Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>

<snipp diff>

-- 
mvh
Hans-Christian Egtvedt

      reply	other threads:[~2012-08-30 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 17:07 [PATCH v2] avr32: at32ap700x: set DMA slave properties for MCI dw_dmac Hein Tibosch
2012-08-30 19:22 ` Hans-Christian Egtvedt [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=20120830192253.GA10588@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=akpm@linux-foundation.org \
    --cc=cjb@laptop.org \
    --cc=havard@skinnemoen.net \
    --cc=hein_tibosch@yahoo.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    /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).