From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmci: fixup broken_blockend variant patch v2
Date: Thu, 20 Jan 2011 00:52:33 +0100 [thread overview]
Message-ID: <AANLkTimGmGStr8wHbJhkOsPcrWQmLFFQQCpgizE8+joj@mail.gmail.com> (raw)
In-Reply-To: <20110119205158.GC6335@n2100.arm.linux.org.uk>
2011/1/19 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> On Wed, Jan 19, 2011 at 09:34:49PM +0100, Linus Walleij wrote:
>> 2011/1/18 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>>
>> > How reliable is the FIFOCNT register ?
>>
>> Hmm... the FIFOCNT is just the FIFO.
>
> No, FIFOCNT.
>
> ?The MCIFifoCnt register contains the remaining number of words to be
> ?written to or read from the FIFO.
Yeah I B damned that's right. Sorry for the confusion. I'll respin
the latest patch on the FIFOCNT register instead and test
tomorrow.
But if the transfer is complete, MCIDataCnt should be valid
as well. I'll read the datasheet(s) closer and see if I get some
useful clues about which one is more reliable in the error
case.
Sorry for late night confusion...
Linus Walleij
next prev parent reply other threads:[~2011-01-19 23:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 14:37 [PATCH] mmci: fixup broken_blockend variant patch v2 Linus Walleij
2011-01-17 15:12 ` Rabin Vincent
2011-01-17 16:02 ` Linus Walleij
2011-01-18 12:14 ` Russell King - ARM Linux
2011-01-19 20:34 ` Linus Walleij
2011-01-19 20:51 ` Russell King - ARM Linux
2011-01-19 23:52 ` Linus Walleij [this message]
2011-01-21 12:53 ` Linus Walleij
2011-01-23 18:01 ` Russell King - ARM Linux
2011-01-23 21:40 ` Linus Walleij
2011-01-23 23:09 ` Russell King - ARM Linux
2011-01-24 8:18 ` Linus Walleij
2011-01-24 11:21 ` Russell King - ARM Linux
2011-01-24 14:29 ` Linus Walleij
2011-01-27 11:06 ` Russell King - ARM Linux
2011-01-27 14:16 ` Linus Walleij
2011-01-17 15:36 ` Rabin Vincent
2011-01-17 15:56 ` Linus Walleij
2011-01-17 16:56 ` Rabin Vincent
2011-01-18 15:01 ` Linus Walleij
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=AANLkTimGmGStr8wHbJhkOsPcrWQmLFFQQCpgizE8+joj@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).