From: Alex Dubov <oakad@yahoo.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: David Brownell <david-b@pacbell.net>,
Andrew Victor <linux@maxim.org.za>, Pavel Pisa <ppisa@pikron.com>,
Carlos Aguiar <carlos.aguiar@indt.org.br>,
Anderson Briglia <briglia.anderson@gmail.com>,
"Syed Mohammed, Khasim" <x0khasim@ti.com>,
Russell King <rmk@arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] MMC multiwrite capability removal
Date: Sun, 20 Apr 2008 07:54:32 -0700 (PDT) [thread overview]
Message-ID: <671558.27051.qm@web36705.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080420103019.7c31cb9f@mjolnir.drzeus.cx>
--- Pierre Ossman <drzeus-list@drzeus.cx> wrote:
> On Sat, 19 Apr 2008 19:34:12 -0700 (PDT)
> Alex Dubov <oakad@yahoo.com> wrote:
>
> >
> > tifm_sd relies on controller to report the number of successfully
> transferred
> > blocks. Of course, I cannot be sure to what extent the controller is
> > trustworthy. It worked fine until now, though.
> >
>
> Sounds like a perfect example of when we have to report 0 upon
> failures. I suspect most controllers will be like this as all the specs
> I've glanced at lack the detail needed to implement a proper sector
> count.
>
> The problems caused by reporting incorrect values here are extremely
> rare and difficult to provoke, so normal testing is not likely to
> uncover it.
>
On the other hand, you may remember that in one of the earlier versions of the
driver I actually counted busy/ready cycles during transfer and from what I
remember, it appeared like controller does the right thing - decrements the
page counter at the "not busy" strobe.
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
next prev parent reply other threads:[~2008-04-20 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 7:51 [RFC] MMC multiwrite capability removal Pierre Ossman
2008-04-20 2:34 ` Alex Dubov
2008-04-20 8:30 ` Pierre Ossman
2008-04-20 14:54 ` Alex Dubov [this message]
2008-04-21 19:05 ` David Brownell
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=671558.27051.qm@web36705.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=briglia.anderson@gmail.com \
--cc=carlos.aguiar@indt.org.br \
--cc=david-b@pacbell.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=ppisa@pikron.com \
--cc=rmk@arm.linux.org.uk \
--cc=x0khasim@ti.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