From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
kernel@avr32linux.org, shannon.nelson@intel.com,
David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH v4 6/6] Atmel MCI: Driver for Atmel on-chip MMC controllers
Date: Sat, 28 Jun 2008 15:45:15 +0200 [thread overview]
Message-ID: <20080628154515.0eb002f6@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080628144313.353bbf18@hskinnemo-gx745.norway.atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Sat, 28 Jun 2008 14:43:13 +0200
Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
> Tests 15 and 17 return -EILSEQ instead of -ETIMEDOUT. The at91_mci
> driver has the same problem, and I think it's a hardware issue -- the
> controller wrongly flags a CRC error instead of a data timeout error
> if the card doesn't respond with any CRC status after a write. I don't
> know how to work around that problem.
If that's how the hardware behaves, then EILSEQ will have to do. The
test is more about forcing people to do proper error management in the
driver than anything else. Have a check that you don't report a bad
bytes_xfered though.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-28 13:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 13:23 [PATCH v4 0/6] dmaengine/mmc: DMA slave interface and two new drivers Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 1/6] dmaengine: Add dma_client parameter to device_alloc_chan_resources Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 2/6] dmaengine: Add dma_chan_is_in_use() function Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 3/6] dmaengine: Add slave DMA interface Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 4/6] dmaengine: Make DMA Engine menu visible for AVR32 users Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 5/6] dmaengine: Driver for the Synopsys DesignWare DMA controller Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 6/6] Atmel MCI: Driver for Atmel on-chip MMC controllers Haavard Skinnemoen
2008-06-27 19:10 ` Haavard Skinnemoen
2008-06-27 19:56 ` Pierre Ossman
2008-06-28 12:43 ` Haavard Skinnemoen
2008-06-28 13:31 ` Haavard Skinnemoen
2008-06-29 16:49 ` Pierre Ossman
2008-06-28 13:45 ` Pierre Ossman [this message]
2008-06-28 14:01 ` Haavard Skinnemoen
2008-06-28 14:11 ` Pierre Ossman
2008-06-27 21:31 ` Dan Williams
2008-06-28 12:47 ` Haavard Skinnemoen
2008-07-04 0:40 ` dmaengine skip unmap (was: Re: [PATCH v4 5/6] dmaengine: Driver for the Synopsys DesignWare DMA controller) Dan Williams
2008-07-04 14:47 ` Haavard Skinnemoen
2008-06-26 14:15 ` [PATCH v4 4/6] dmaengine: Make DMA Engine menu visible for AVR32 users Adrian Bunk
2008-06-26 14:46 ` Haavard Skinnemoen
2008-06-27 0:59 ` Dan Williams
2008-06-27 16:37 ` David Brownell
2008-06-27 17:44 ` Adrian Bunk
2008-06-27 18:24 ` David Brownell
2008-06-27 18:29 ` Adrian Bunk
2008-06-27 18:31 ` Dan Williams
2008-06-27 18:13 ` Haavard Skinnemoen
2008-06-26 20:04 ` David Brownell
2008-06-26 13:32 ` [PATCH v4 3/6] dmaengine: Add slave DMA interface Haavard Skinnemoen
2008-06-28 12:29 ` Haavard Skinnemoen
2008-07-02 1:31 ` [PATCH v4 2/6] dmaengine: Add dma_chan_is_in_use() function Dan Williams
2008-07-02 2:00 ` Dan Williams
2008-07-02 7:59 ` Haavard Skinnemoen
2008-07-02 7:56 ` Haavard Skinnemoen
2008-07-04 1:06 ` [PATCH v4 0/6] dmaengine/mmc: DMA slave interface and two new drivers Dan Williams
2008-07-04 15:13 ` Haavard Skinnemoen
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=20080628154515.0eb002f6@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=dan.j.williams@intel.com \
--cc=david-b@pacbell.net \
--cc=haavard.skinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon.nelson@intel.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.