From: Pierre Ossman <drzeus@drzeus.cx>
To: "raki john" <raki4652@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: relation between mmc_request, mmc_data and mmc_command
Date: Tue, 25 Dec 2007 14:35:40 +0100 [thread overview]
Message-ID: <20071225143540.1dd5aca4@poseidon.drzeus.cx> (raw)
In-Reply-To: <d2a348dd0712232325s7da2bfdfk92b0fd049adcb3df@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Sun, 23 Dec 2007 23:25:26 -0800
"raki john" <raki4652@gmail.com> wrote:
>
> Does mmc_requeest->stop is equal to mmc_request->data->stop ?
>
> Does mmc_request is equal to mmc_request->data->mrq ?
>
> Does mmc_request->data is equal to mmc_request->cmd->data ?
>
> Does mmc_request is equal to mmc_request->cmd->mrq ?
>
Yes on all accounts. I don't know the reason for this extreme redundancy. It was there long before I got involved.
>
> I think Stop command which is part of mmc_request is used for sending stop
> command after Multi Block write. is this correct. If stop command fails(CRC
> fail, timeout), does this mean card write failed.
>
It is correct that it is used for multi block writes. But also other open ended transfers.
If the stop command fails, then the card will be in an unknown state. The write should have been completed though.
Rgds
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next parent reply other threads:[~2007-12-25 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d2a348dd0712232325s7da2bfdfk92b0fd049adcb3df@mail.gmail.com>
2007-12-25 13:35 ` Pierre Ossman [this message]
2007-12-24 8:05 raki john
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=20071225143540.1dd5aca4@poseidon.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=raki4652@gmail.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
all inboxes | Powered by JetHome®