From: Joey Oravec <joravec@drewtech.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Rob Emanuele <poorarm@shoreis.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [PATCH] New AT91 MCI Driver that supports both MCI slots used at the same time
Date: Wed, 03 Jun 2009 11:45:07 -0400 [thread overview]
Message-ID: <4A269A83.3020008@drewtech.com> (raw)
In-Reply-To: <4A269251.8090706@atmel.com>
Nicolas Ferre wrote:
> This systematic reset was remove by Haavard with this comment:
> "Also, don't reset the controller between each transfer. That was an
> attempt to work around earlier bugs, and it never really worked very
> well."
>
See:
http://lists.arm.linux.org.uk/lurker/message/20090409.120542.4f74c08d.en.html
I disagree with Haavard. Without the reset my sam9261 would exhibit DAT0
contention, early interrupts, and other problems. Adding the reset was a
major improvement. I emailed you some screenshots on April 10 2009 that
demonstrate my testing. Let me know offline if either you or Havaard did
not get the email and I can resend.
Maybe the problems are limited to this chip? We should discuss this further.
-joey
next prev parent reply other threads:[~2009-06-03 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 21:40 [PATCH] New AT91 MCI Driver that supports both MCI slots used at the same time Rob Emanuele
2009-05-29 15:27 ` Joey Oravec
2009-06-02 16:53 ` Rob Emanuele
2009-06-03 15:10 ` Nicolas Ferre
2009-06-03 15:45 ` Joey Oravec [this message]
2009-06-03 19:02 ` [PATCH][Updated] " Rob Emanuele
2009-06-08 10:47 ` Haavard Skinnemoen
2009-06-08 16:58 ` Rob Emanuele
2009-06-08 18:59 ` Rob Emanuele
2009-06-02 8:49 ` [PATCH] " Nicolas Ferre
2009-06-02 16:31 ` Rob Emanuele
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=4A269A83.3020008@drewtech.com \
--to=joravec@drewtech.com \
--cc=hskinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=poorarm@shoreis.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 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.